Hello Filipus, On Tue, Jul 23, 2013 at 09:20:26AM -0400, Filipus Klutiero wrote: > The system where this originally happened no longer exists. But I > still experience the same symptom on my current PC. If the cause is > the same, I now have a good clue about what's wrong; the error console > gets this when I test the sound: > >Error: uncaught exception: [Exception... "Component returned failure code: > >0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsISound.play]" nsresult: "0x80040111 > >(NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: > >chrome://messenger/content/preferences/general.js :: <TOP_LEVEL> :: line 94" > > data: no] > > This must be related to several upstream reports: > https://bugzilla.mozilla.org/show_bug.cgi?id=635918 > https://bugzilla.mozilla.org/show_bug.cgi?id=537195 > https://bugzilla.mozilla.org/show_bug.cgi?id=629081 > > These suggest the issue would be fixed in Thunderbird 12. I am still > on Icedove 10, so I will re-test when I upgrade.
thanks for your quick feedback! That sounds very interesting. I will try in the next free time to merge this changes that made to TB 12. Mozilla will no longer support the current Icedove version 10.0 in stable because the new ESR version after the version 10 is 17. That's the reason why 17.0.7 is currently in stable-security. But if this back merging works we can build a newer version with that sound fixing for the 10.0.12. > Note: icedove may be missing a dependency on libcanberra, The current version 17 of Icedove has a dependencie to libasound2-dev and don't use libcanberra-dev. We have to investigate this. But thanks for your collections of this infos! Regards Carsten -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
