Closed Bug 228024 Opened 21 years ago Closed 21 years ago

mail notification custom .wav doesn't work [preview button doesn't work either]

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 186954

People

(Reporter: x, Assigned: sspitzer)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

I've tried a whole bunch of things to get custom .wav files to play when I hit
the 'preview' button under the mail notification setup preference.  I've tried
running under no sound mixer ( no esd or artsd ), I've tried under esd, and I've
tried under artsd.  I get no sound whatsoever either way.

I've made sure that I can play sound [not using mozilla] under all three
configurations above.

I've reduced the filename to a very short one, and put it in the root with full
permisions.  I then tried paths like /a.wav, file:///a.wav, file:\\\a.wav, etc,
all with no luck.

I'm using the .wav that comes with mozilla under res/samples/test.wav

I get no error messages or other hints.  It just doesn't play.  The 'system
beep' does work as a notification.

Reproducible: Always

Steps to Reproduce:
1.Edit -> Preferences -> Mail & Newsgroups -> Notifications
2.Play a sound -> Custom Wav file
3.Type in Wav name like /a.wav or file:///a.wav
4.Press Preview.

Actual Results:  
Nothing happened

Expected Results:  
Sound should play

I get the feeling reading through similar bugzilla cases that this will be hard
for you to reproduce.  Any pointers you guys can give me on things to try or
ways to get more information would be great.
Please check bug 177280 (which is supposed to be fixed in 1.5) and bug 214937.

Also, do you have artsd or esd or any other application or daemon running that
might be blocking the sound device? To get sounds working (Linux, KDE) I have to
use 'artsdsp ./mozilla' to start Mozilla, otherwise artsd will block the sound
device, and mozilla natively doesn't know about arts. 

To test, just kill anything that might be accessing the sound device (artsd,
esd, any type of sound player, games, etc.) and try again.
I've tried it with no sound servers, with esd, with just artsd, and none worked.
 I tried your artdsp approach too, with no success.  I have looked at the bugs
you mentioned, which is why I tried file:///a.wav, file:\\\a.wav, etc. Thanks
for the response. Any debugging info I can turn on that relates? 

*** This bug has been marked as a duplicate of 186954 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Verified dup.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
Component: MailNews: Notification → MailNews: Message Display
QA Contact: stephend → search
You need to log in before you can comment on or make changes to this bug.