I have set up "new email notification" in my Thunderbird, both "Show an alert" and "Play a sound", as shown below. But now I am experiencing strange problems.
The sound only works sometimes. Then, I close Thunderbird and start again, and there is 50% chance that the sound will not work. If I keep restarting Thunderbird, eventually the sound will start to work again.
The wav
file exists, when I click on Play I can hear the sound.
I have a suspicion, this problem might be connected to the fact, that I have two Thunderbird Profiles which I am using simultaneously. Sometimes the Notification works in both, sometimes in one only. The problem is with both the sound notification and the "Show an Alert" notification.
I use following commands to start the two profiles, respectively:
icedove -P "default"
icedove -P "second" -no-remote
The problem with the notification happens in a non-deterministic way. Even when only one profile is running, the notifications might not work (thus, the problem is not caused by one instance "blocking" the device/resource).
How could I fix this problem? New mail notifications are crucial for my workflow. This problem is critical for me.
I am using Thunderbird (Icedove) 24.6.0
UPDATE:
I did some further troubleshooting: When I am monitoring access to the wav
file using inotify
, I see that upon new message, no process is attempting to open new_mail.wav
:
while inotifywait new_mail.wav ; do echo "$(date +%T) inotify event" ; done
When I click on the Play button however, the sound actually plays, I and get the inotify events as well.
This looks like some bug in Thunderbird, where an event (new email) is not properly recognized and acted upon.