554505 - OGG audio does not play using 32-bit Firefox build on a 64-bit Linux OS

Status: RESOLVED INVALID

(Core :: Audio/Video, defect)

Description

[Bill Gianopoulos [:WG9s]]

OGG audio content does not seem to play using the Official Firefox 32-bit builds under a Fedora 12 64-bit Operating system.

The same files seem to play just find on a 64-bit Windows 7 OS using an Official Firefox 32-bit windows build on the exact same hardware, so this would appear to be Linux only.

Also on the same hardware a Linux 64-bit build seems to play the audio just fine.

Comment 1

[Bill Gianopoulos [:WG9s]]

The video on the URL seems to exhibit this issue.

Comment 3

[Matthew Gregan [:kinetik]]

What version are you testing with?  Does that happen using a nightly build of the trunk?

Comment 4

[Bill Gianopoulos [:WG9s]]

Well yes. That is why I set the Version to Trunk.

Comment 5

[Matthew Gregan [:kinetik]]

I tend not to pay attention to the version field as people often file with their regular browser.  Anyway, thanks for confirming.  I've got a 64-bit F12 VM at home, so I'll see if I can debug this tonight.

Comment 6

[Bill Gianopoulos [:WG9s]]

Oh and this has nothing to do with library versions etc.  This also fails with
my own 32-bit builds crated on the same machine that I see the failure on.  I
see this on 3 different systems.  They are all running Fedora 12 on AMD 64-bit
processors, however, so in a lot of ways similar.

Comment 7

[Matthew Gregan [:kinetik]]

snd_pcm_open fails returning -2.  If I disable the silent error handler, the error reported is "ALSA lib pcm.c:2171:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_module_pcm_pulse.so".

Solution is pretty obvious once you have that error text: yum install alsa-plugins-pulseaudio.

Comment 8

[Bill Gianopoulos [:WG9s]]

Thanks.

Actually what is required is:

yum install alsa-plugins-pulseaudio.i686

Not including the .i686 part just returns a message saying it is already installed since the 64-bit version is installed.

However, how does one disable this silent error handler and exactly under what circumstances is it desirable to hide this error from the user?

Comment 9

[Bill Gianopoulos [:WG9s]]

Nevermind.  I found that bug 461281 introduced the quiet error handler, so the explanation is there.