Linux trunk build 2002111311 Whenever you have specified a custom WAV file to play for new mail notification on Linux, instead of hearing the sound, you hear nothing, and the following error appears in the Javascript console: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsISound.play]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/pref-notifications.js :: PreviewSound :: line 63" data: no] see also, bug 64462 comment 155

Linux release 1.2.1 I'm sorry to dig this up again after some of us might have thought this safely buried :-} I am still getting no sound output (via the soundcard) on mail notification. I realise there have been "worksforme" posts, so I am working from a fresh profile created from scratch. The entries in prefs.js as inserted by the dialogue routine (i.e. without any file:// ) result in nothing but the system beep. The "preview" button in the dialogue only plays the system beep, regardless of what WAV file is selected. If I manually enter file:// in the sound-URL in prefs.js, I get absolute silence on mail notification. Here are the appropriate lines in my prefs.js as they are at the moment: user_pref("mail.biff.play_sound.type", 1); user_pref("mail.biff.play_sound.url", "file:///home/James/misc/quack.wav"); Can anyone see anything wrong with this? Needless to say, I have tried this with other WAV files. Running "play quack.wav" from the command-line works OK.

Confirming based on comment #1

From http://bugzilla.mozilla.org/show_bug.cgi?id=64462#c148: ------- Additional Comment #149 From Seth Spitzer 2002-09-19 16:41 ------- I need to fix the path handling code. see bug 169414 I need to make it work for both file:// and native paths the side effect of this bug is that on linux, any native path will be the system beep. Guys, I think this might be a dup of bug 169414, based on the above comment.

Stephen: No, I do not believe this is a dup. I was already aware before filing this bug that a native path such as "/home/username/beep.wav" would not work. Until bug 169414 is fixed, yes, you must use a file:// path to specify your wav file on linux. But this bug is about the fact that when I do _correctly_ specify a path that should work (and does work for some other people, according to comments on bug 64462) I get no sound at all, no speaker-beep, and a javascript error.

onfirming based on comment #1 Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.2.1) Gecko/20021130

*** This bug has been marked as a duplicate of 177280 ***

Verified dup