Description of problem: All videos opened by firefox play with no sound since the upgrade to firefox 60. This is confirmed on 2 different machines. I am not running pulseaudio, but even with pulseaudio I cannot get sound, for instance for any youtube videos. No issue with the sound card whatsoever, all this videos play fine with chrome-browser. Tried --safe-mode, no change. Tried to disable hardware acceleration, no change. The console however reports a lot of issues: JavaScript error: jar:file:///usr/lib64/firefox/omni.ja!/components/nsUrlClassifierListManager.js, line 65: NS_ERROR_XPC_GS_RETURNED_FAILURE: Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService] JavaScript error: jar:file:///usr/lib64/firefox/omni.ja!/components/nsUrlClassifierListManager.js, line 65: NS_ERROR_XPC_GS_RETURNED_FAILURE: Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService] [Child 26439, MediaPlayback #1] WARNING: 7f1208f6d940 OpenCubeb() failed to init cubeb: file /home/iurt/rpmbuild/BUILD/firefox-60.3.0/dom/media/AudioStream.cpp, line 388 [Child 26439, MediaPlayback #1] WARNING: Decoder=7f120adab5c0 [OnMediaSinkAudioError]: file /home/iurt/rpmbuild/BUILD/firefox-60.3.0/dom/media/MediaDecoderStateMachine.cpp, line 3750 console.log: Accessibility service init or shutdown observer does not exist. ###!!! [Parent][MessageChannel] Error: (msgtype=0x160080,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost [Child 26439, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /home/iurt/rpmbuild/BUILD/firefox-60.3.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ###!!! [Child][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost *** UTM:SVC TimerManager:registerTimer called after profile-before-change notification. Ignoring timer registration for id: telemetry_modules_ping PS: As other users, I don't understand why we have upgraded firefox on the stable mageia 6, got many other troubles as well, which are currently opened bugs (PDF opening, themes broken etc...) :(
Sorry but works for me, videos in youtube and some anime pages that i visit also works the pdf viewer. What sites do you test? From what mirror do you download the packages? - if you use mirrorlist check if the system give you a full updated mirror - Do you install the codecs? Firefox 52 have reached end of support so is not good idea keep it. This is my output seeing a youtube video (xfce i586) alloc factor 0.900000 0. (x6) [Child 4737, MediaPlayback #4] WARNING: Decoder=9f8a4700 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<mozilla::MozPromise<RefPtr<mozilla::MediaTrackDemuxer::SamplesHolder>, mozilla::MediaResult, true> > mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /home/iurt/rpmbuild/BUILD/firefox-60.3.0/dom/media/MediaDecoderStateMachine.cpp, line 3445 (x3)
It works for me also. I'm running, FF 60.3.0esr (64-bit), with Pulseaudio.
@ Chris, Does it still not work if you move ~/.firefox temporarily out of the way and start firefox again? If so, did you try the suggestions here https://support.mozilla.org/en-US/kb/fix-common-audio-and-video-issues. If that didn't help: do you have the same problem with Firefox from upstream (instead of the Mageia package)? http://ftp.mozilla.org/pub/firefox/releases/60.3.0esr/
Assignee: bugsquad => pkg-bugsKeywords: (none) => NEEDINFOCC: (none) => lists.jjorge, marja11, mramboSummary: no sound in firefox => no sound in firefox-60.3.0-1.mga6
All right, thanks for the feedback and suggestions guys. I've managed to make it works, but only with pulseaudio! In my previous tries, I did not notice that starting pulseaudio was muting the audio (great idea by the way...). So yes, no issue whatsoever with pulseaudio. But, I am not using pulseaudio usually, and without pulseaudio, no way to make it works. But maybe alsa support is just a compilation switch? PS: I've renamed the title accordingly!
Summary: no sound in firefox-60.3.0-1.mga6 => no sound in firefox-60.3.0-1.mga6 without pulseaudio
How to say... Firefox requires pulseaudio since some versions... https://www.omgubuntu.co.uk/2017/03/firefox-52-no-sound-pulseaudio-alsa-linux
Keywords: NEEDINFO => (none)Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Another very good reason to not have upgraded firefox for mga6.... That was a *mistake*. We should never break a working distro configuration and mga6 allowed users to not have pulseaudio. drakconf -> hardware -> sound. See the box "Enable PulseAudio"? :) So, it is not RESOLVED FIXED, it is RESOLVED WONTFIX. At most firefox 60 should have been proposed as a backport package, clearly not an upgrade :( PS: on some slow machines, pulseaudio is not welcome...
Resolution: FIXED => WONTFIX
(In reply to Chris Denice from comment #6) > Another very good reason to not have upgraded firefox for mga6.... That was > a *mistake*. We should never break a working distro configuration and mga6 > allowed users to not have pulseaudio. > > drakconf -> hardware -> sound. See the box "Enable PulseAudio"? :) > > So, it is not RESOLVED FIXED, it is RESOLVED WONTFIX. > > At most firefox 60 should have been proposed as a backport package, clearly > not an upgrade :( You can stay in 52 if you like, uninstall the 60 version add firefox to /etc/urpmi/skip.list Install the last 52 packages you need, dowloading them from repositories > PS: on some slow machines, pulseaudio is not welcome... By curiosity how as slow ? I keep pulseaudio and for vlc and smplayer use the alsa output that mitigate the audio/video desynchronization, and my machine is old and slow for the modern standards
(In reply to Chris Denice from comment #6) > Another very good reason to not have upgraded firefox for mga6.... That was > a *mistake*. We should never break a working distro configuration and mga6 > allowed users to not have pulseaudio. It is always hard to decide, but for a web browser, security fix are more important than lightweight use. I *use* firefox with pulseaudio disabled in a 2003 laptop, but I accept to have nosound. You can also just get sound launching pulseaudio before restarting firefox... A distro should never go against upstream design, else it gives unexpected behaviour...
Guys, you are confusing distro upgrade and distro update. Mga6 provided firefox 50, going with upstream just means mga7 will have firefox 60. Maintainer job is to maintain firefox 50 for mga6, and security fixes are just patches that can be applied on source files. Security fixes in that respect indeed require more job than only syncing with upstream, but that's precisely why we have releases, to maintain stability for a while. Rolling packages following upstream is called a rolling release, and that's Cauldron, not mga6, neither mga7. Sorry to disagree, but that's what we had till now and we should keep that on. Mistake has been made, no offence, this is happening to everyone. I'll switch to chrome or pulseaudio, but this situation is a killer for the users not using pulseaudio, not too many fortunately I suspect. Anyway, that's a WONTFIX, and people will land here searching on bugzilla, but we should try to not have many of these updates :) cheers.
There's no mistake here, and as a fellow developer, you should know better than that. We don't use the milestone (development) releases, so your point about 50 to 60 is just wrong. We use the ESR version, the long-term stable release. That's all that's maintained upstream and it's all we can do. There aren't backportable patches available and it's not our job to keep the previous stable version maintained when upstream no longer does (and indeed, many websites don't work with it anymore). The dropping audio support (along with many other things) in 60 is very unfortunate, but it's upstream's mistake, not ours. There's nothing we can reasonably do about it.