534033 - Custom Message Alert Sound wont play

Status: RESOLVED DUPLICATE of bug 579877

(Thunderbird :: Preferences, defect)

Description

[flytrap]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091105 Fedora/3.5.5-1.fc12 Firefox/3.5.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4pre) 

When I receive an email, and have the preferences set to play a custom sound- it does not play. It instead plays the default popping sound.

This has only been tested with .wav files.


Reproducible: Always

Steps to Reproduce:
1. set the alert preferences to a custom .wav sound.
2. send yourself an email to an account that's synced to thunderbird, or wait for an email. whichever.
3. notice that the email alert didn't play the sound you chose.
Actual Results:  
It doesn't play. Instead, the default popping sound plays.

Expected Results:  
I expect the file I chose to play.

Fedora Core 12, kernel 2.6.31.6-162.fc12.i686
Thunderbird 3.0b4
Tested with the "speech on.wav" retrieved from Windows Vista's system files and the windows95 boot sound, retrieved from http://www.angelfire.com/games5/clockmaster/themicrosoftsound.wav

Comment 1

[flytrap]

The issue is also occuring with the Lightning extension (1.01bpre), only it won't even play its default sound.

Comment 2

[cantalou]

Tested with:
- Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b1pre Thunderbird/3.0 ID:20091204171430
- Windowd XP

I had no problem: *.wav files was played OK

FlyTrap,

Could you please try to start TB in safe mode.
Please also check if you have any  extension (Tools => Nightly Tester Tools =>
Copy List of Extensions to Clipboard)

Do you have any message in your error console (Tools => Error Console)?

Could you please try to upgrade to final release of TB v3:
http://www.mozillamessaging.com/en-US/

Comment 3

[cantalou]

To start TB in Safe Mode see:
http://kb.mozillazine.org/Safe_mode

Comment 4

[flytrap]

updated to the latest version, still wouldn't play.
Due to several issues I was having with fedora12, I downgraded to fedora11. The sound plays just fine there.

I suspect this might be something related more to the distrobution than thunderbird itself.

I'm going to poke around a bit more and probably throw this at the Fedora Bugzilla.

Comment 5

[cantalou]

If you're convinced that this bug is Fedora 12 specific, could you please close this bug in Thunderbird bugzilla.
If you open a bug in Fedora bugzilla maybe you could make a link to Fedora BugZilla in case another user face the same issue.

Thanks for your support and time you took to report this bug

Comment 6

[flytrap]

heh, not really sure how to close it :\

Comment 8

[Grégoire Paris]

Hi
I'm also using Fedora 12, I filed the duplicate bug.
Copied from bug 543842 :
I get a message when I press the play button : 
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/preferences/general.js :: anonymous :: line 94" 
data: no]

Comment 9

[flytrap]

that never happened for me.

Comment 10

[Grégoire Paris]

I filed a bug here : https://bugzilla.redhat.com/show_bug.cgi?id=561551

Comment 11

[Grégoire Paris]

(In reply to comment #9)
> that never happened for me.
The message appears in the error console, you must open it if you want to notice it.

Comment 14

[S.W.B.]

Hi, this bug apparently isn't Fedora-specific.  I have it with Kubuntu 10.04, but I am running the official Thunderbird RC2 from the official tarball that Mozilla released.  And mine won't play custom .wav files either.  It always worked with 2.x and 3.0 releases of Thunderbird.

Comment 15

[tbird]

Hi, got the same problem and error-message here while upgrading to release 3.1 from official-source-tarball. Using Debian Sid (Sidux), KDE4.4.4 and pulse-audio-system on a x86_64-machine. No problems with TBird 3.0.4 and/or 3.0.5 .

Comment 16

[Sasafrass]

Same problem here, using PCLOS. Apparently, this is a Linux-wide issue....