Bug 1631 - Thunderbird - No new mail sound, only default plop
Summary: Thunderbird - No new mail sound, only default plop
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Florian Hubold
QA Contact:
URL: https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Keywords: PATCH, UPSTREAM
Depends on:
Blocks:
 
Reported: 2011-06-06 10:28 CEST by claire robinson
Modified: 2012-03-10 22:59 CET (History)
6 users (show)

See Also:
Source RPM: mozilla-thunderbird
CVE:
Status comment:


Attachments

Description claire robinson 2011-06-06 10:28:28 CEST
Description of problem:

When Thunderbird is set to play a wav file as new mail arrives, it doesn't. Also clicking the Play button in the preferences plays nothing.

I've posted an ubuntu launchpad link which seems to show it is a common bug to natty and also fedora 15 so it might be an upstream bug but I couldn't find anything on the bugzilla.

Version-Release number of selected component (if applicable):

Thunderbird 3.1.10


How reproducible:

Set thunderbird to play a wav file when new mail arrives. It only plays the default plop sound and won't play wav files when clicking the Play button in preferences either.


I found this in the thunderbird error 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/preferences/general.js :: anonymous :: line 94"  data: no]
Comment 1 Carroll Lashlee 2011-06-06 23:17:28 CEST
I have same problem and reported in forums.

https://forums.mageia.org/en/viewtopic.php?f=7&t=434

CC: (none) => lashleec

Comment 2 Stuart Rogers 2011-06-07 00:09:02 CEST
I have this problem as well and started the tread mentioned. The only difference for me is that I cannot get the default system sound either, no sound at all from Thunderbird 3.1.10, both using the Mageia package and a copy of Thnuderbird installed in my home directory.

CC: (none) => stuart

Remco Rijnders 2011-09-13 07:49:49 CEST

CC: (none) => fundawang

Manuel Hiebel 2011-09-15 00:34:25 CEST

Keywords: (none) => UPSTREAM

Comment 3 Samuel Verschelde 2011-10-01 03:54:47 CEST
Assigning to maintainer now that our maintainers database has an entry for
this package. Please assign back to bugsquad@mageia.org in case of a mistake
from me.

CC: (none) => stormi
Assignee: bugsquad => anssi.hannula

Olivier Placais 2011-10-01 09:35:48 CEST

CC: (none) => olivier.placais

Florian Hubold 2011-10-01 23:46:12 CEST

Status: NEW => ASSIGNED
CC: (none) => doktor5000
Assignee: anssi.hannula => doktor5000

Comment 4 Florian Hubold 2011-10-01 23:50:11 CEST
(In reply to comment #0)
> Description of problem:

> 
> I've posted an ubuntu launchpad link which seems to show it is a common bug to
> natty and also fedora 15 so it might be an upstream bug but I couldn't find
> anything on the bugzilla.

FWIW, the whole launchpad bugs consists of comments of the upstream bug.
Check the link "In Mozilla Bugzilla #635918" which is in the header of all the comments.

The upstream bug is still not fixed so far, until that, no fix, sorry.
Comment 5 Manuel Hiebel 2012-01-31 13:17:43 CET
Upstream bug resolved

Keywords: (none) => PATCH

Comment 6 Florian Hubold 2012-01-31 15:38:02 CET
Thanks for noticing, will take a look whether we can include this in an mga1 update.
Comment 7 Florian Hubold 2012-02-15 00:43:00 CET
This will be solved with next Mageia 1 update of thunderbird, where we'll switch to thunderbird ESR release 10.0.1. Would not be possible for thunderbird 3.1 branch, so i'm lucky :)
Comment 8 claire robinson 2012-02-15 09:48:03 CET
Thanks for looking into this Florian.
Comment 9 Florian Hubold 2012-03-10 22:59:18 CET
As Thunderbird 10.0.2 will be validated soon, and the problem was reported to be solved, closing this one.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.