Open Bug 751047 Opened 12 years ago Updated 2 years ago

New Mail notification sound not playing if the sound sample rate >16kHz.

Categories

(Core :: Widget: Gtk, defect, P5)

12 Branch
x86
FreeBSD
defect

Tracking

()

UNCONFIRMED

People

(Reporter: hm, Unassigned)

Details

(Keywords: qawanted, Whiteboard: [testday-20120713][Workaround see Comment 26])

User Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:12.0) Gecko/20120428 Firefox/12.0 SeaMonkey/2.9
Build ID: 20120428075329

Steps to reproduce:

I saw 635918, but I am not sure if it is the same issue

Seamonkey only plays the new mail notification sound so long as it is the default kde4 Kmail notification sound

If kmail (kdepim) is not installed it does not play any sound, whatever you select as custom in seamonkey

if kmail is installed it does not play any sound what not is the default kde .wav, what then, should be the new system notification sound


it does not play _any_ custom sound selected in seamonkey

if kde notification is at its default, it does not play the sound when another player is selected as kde4 default (example mplayer)

it also and only plays the kde4 default sound if pulseaudio is the backend
Do you have libcanberra installed?
yes
libcanberra-0.28_1
I compared with my fedora 16 setup and there the sound is playing, also, I thought it plays only .wav but the file type selection box is kind of invisible in FreeBSD's Interface, so it might be not a Seamonkey problem

it still do not play any sound as long as the system default is selected AND the system default song is not the standard pop.wav

selecting custom sound, it plays certain files but not any, I guess that is an encoding problem? However, same sound is/can being played by KDE applications, can you tell what Seamonkey is looking for?
Sorry I have no idea, I'm not using FreeBSD but perhaps you are running into a variant of Bug 717906:

So, the problem is that fedora system libraries are depending on libfreebl3.so, and more than that, expect the NSSRAWHASH_3.12.3 symbol version to be there. This is completely unrelated to the requirement of freebl to be using nspr stubs or not, but nss mixes both: disabling one disables both.
------------------------------------

But is is supposedly fixed in SeaMonkey 2.8/Firefox 11
It might also be:
Bug 749739 - New email sound notification file cannot contain spaces (Linux - Thunderbird 12)
thanks for this info

 I checked again and found that the crucial point is that seamonkey apparently can not play any sound file with sample rate >16kHz, even if the KDE system can 

this is common for FreeBSD and Fedora, as result any typical mp3 file is not playing
Thanks this looks like a library problem. I'll move this to somewhere more likely to get fixed.
Component: General → Widget: Gtk
Product: SeaMonkey → Core
QA Contact: general → gtk
Summary: New Mail notification sound not playing → New Mail notification sound not playing if the sound sample rate >16kHz.
Version: SeaMonkey 2.9 Branch → 12 Branch
I asked in mozilla.dev.platform and got a reply:
> If it really is FreeBSD only I doubt it's a priority for the widget-gtk2
> maintainers.

Can someone reproduce with Linux?
Keywords: qawanted
Whiteboard: [Fedora and FreeBSD affected]
Did this used to work in Firefox 11?
I can not say about firefox, I started using Seamonkey with first v2.8, it never played according to the condition of this this report
FYI SeaMonkey 2.8 == Gecko 11
Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1  20120713003005

plays this file:

$ file /usr/share/sounds/alsa/Front_Center.wav 
/usr/share/sounds/alsa/Front_Center.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, mono 48000 Hz
(Debian wheezy/sid)
Whiteboard: [Fedora and FreeBSD affected] → [Fedora and FreeBSD affected][testday-20120713]
hm, can you please try to reproduce with the latest Seamonkey Nightly?
>  Comment 14     Anthony Hughes, Mozilla QA (irc: ashughes)      2012-07-13 17:12:45 PDT
> hm, can you please try to reproduce with the latest Seamonkey Nightly?
> 20120713003005
That's pretty recent.
the nightlies I guess will not run on FreeBSD ...

I will try to compile the latest v from source, I f I can make it work I post the outcome

thanks all
Hans
I got the 2.10 version to compile on my system

but seems this issue is still there, seems it does not play any sound at all, not even the system sound

Build identifier: Mozilla/5.0 (X11; FreeBSD i386; rv:13.0) Gecko/20120718 Firefox/13.0.1 SeaMonkey/2.10.1
Which sound libraries and versions are in use on your system?
Whiteboard: [Fedora and FreeBSD affected][testday-20120713] → [testday-20120713]
gstreamer, xine and vlc, as well as mplayer, all work under kde-4.8 soundsystem as base system
they are all from freebsd ports, up to date

this versions you want to see?
phonon-gstreamer-4.6.1
phonon-vlc-0.5.0_1
phonon-xine-4.4.4_5

but there is no underlaying activity, I have the impression that nothing is send to kde
Do you have any alsa/pulseaudio libraries installed? gstreamer, xine, and vlc are generally used for decoding different encoded formats and have little to do with driving the physical sound card.
of course, I was not thinking

pulseaudio-0.9.23_1
Just speculating, but on Ubuntu I have pulseaudio v1.1. Might be worth investigating if updating pulseaudio on FreeBSD "fixes" this problem on your end.
it is actually the latest version available at this time from freebsd ports

just a comment, sometimes easy things work easier :)
I am saying, do you know how claws-mail solve this? You can configure the cmd line as "mplayer path_to_snd/file.mp3" 
so it is calling any player on any system directly and goes around all of particular OS difficulties
now with the latest official release 2.11 from Freebsd ports, no sound at all, either with the new sound option oss or pulse
may be it helps someone with the same problem, on mozillas add-aonns rep is a plugin "Mailbox Alert" which works. So I can replace seamonkey's new message alert with it and have sound alerts.
another upgrade right away, unfortunately FreeBSD-KDE is so poor documented, but may be this help other people 

pulsaudio was installed, probably pulled inby some gnome ports from metacity, whatever ... 
by some error messages from another program I went deeper into this pulseaudio thing and I deinstalled it, solved the dependencies from other ports, or better I recompiled vlc, mplayer and xine without pulseaudio support, then also phonon without it, because funny or not, KDE does not start without phonon dependencies not solved

now guess what, seamonkey plays the notification sound!

still within this restrictions from above, only wave files, but may be I will find it out also.
> I saw Bug 635918, but I am not sure if it is the same issue
Interesting. Also see Bug 589732 - Selecting custom sound for incoming mail does not work.

Looks like a platform configuration problem involving one or more of pulseaudio or libcanberra or esound.
Whiteboard: [testday-20120713] → [testday-20120713][Workaround see Comment 26]
well, probably it's FreeBSD related because on my FC16 it is working, so either the Fedora guys are better or something in SM is not so much compatible with FreeBSD 

I guess 58973 is some other kind of problem, 635918 sounds similar

in any case, my simple thinking says that when my system can play any soundfiles, then any program able to run on my desktop should be able to play sound independent of the library used. As example play command from sox, as long as it is correctly compiled "play sound.mp3" plays, so I do not understand why SM can not do it as simple as it seems to be

since the actual FreeBSD port has an option to chose between Alsa,Pulseaudio and OSS before installing or upgrading, either one should work, but only OSS does and only with the already discussed restrictions

the funny part is, compiled SM with OSS support _and_ having pulseaudio installed (but system default is OSS and works), it does not make a sound, but without pulseaudio installed it plays, still with the same restrictions but it plays standard wav. Since I see the problem on a lot of computers, I do not think that it is an isolated problem related to my machine.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.