For 129 & the previous version, I've been getting no sound from YouTube in chromium. Searching for this issue does this give many old similar issues, but no current ones. Firefox playing YouTube does give sounds, and KDE test sounds work okay too. I could upgrade to 131, it's just that chromium takes ages to build, I don't want to do it unless that will fix the issue.
Created attachment 907827 [details] emerge --info
> I could upgrade to 131, it's just that chromium takes ages to build, I don't want to do it unless that will fix the issue. There's no way we could give such a guarantee. It's likely an upstream bug of course too.
I delayed several days on this. It's only because such a severe issue would be reported widely, and I could not find it on the chromium fault tracker either. Which makes me think it might only be affecting me.
Hi, I thought I replied to this earlier. +1 what Sam said. Running an outdated, vulnerable Chromium cannot be recommended, 129 is only in-tree because ppc64 got held back which has since been fixed. Even if there was an issue with 129 we're not fixing it. Please update to the latest stable slot for Chromium let me know how it goes either way - if you're still seeing it on 130 show me `emerge -pv chromium` and we'll do some troubleshooting.
130 was still masked yesterday. Since I run a sync overnight I checked it in the morning [I] www-client/chromium Available versions: 129.0.6668.100(0/stable)^d (~)130.0.6723.91(0/stable)^td **131.0.6753.0(0/dev)^d (~)131.0.6778.24(0/beta)^td then I ran a sync manually # eix-sync * Running emerge --sync >>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... * Using keys from /usr/share/openpgp-keys/gentoo-release.asc * Refreshing keys via WKD ... [ ok ] >>> Starting rsync with rsync://[2a00:1828:a00d:ffff::6]/gentoo-portage... >>> Checking server timestamp ... rsync: did not see server greeting rsync error: error starting client-server protocol (code 5) at main.c(1850) [Receiver=3.3.0] >>> Retrying... >>> Starting retry 1 of 1 with rsync://89.238.71.6/gentoo-portage >>> Checking server timestamp ... rsync: did not see server greeting rsync error: error starting client-server protocol (code 5) at main.c(1850) [Receiver=3.3.0] >>> Retrying... !!! Exhausted addresses for rsync.gentoo.org Action: sync for repo: gentoo, returned code = 1 * emerge --sync failed * Time statistics: 7 seconds for syncing 7 seconds total I'll try again later in the day.
Oh I am on 131 Installed versions: 131.0.6778.24(0/beta)^td(17:29:01 03/11/24) # emerge -pv chromium These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 3.02 s (backtrack: 0/20). [ebuild R ~] www-client/chromium-131.0.6778.24:0/beta::gentoo USE="X hangouts official proprietary-codecs pulseaudio qt5 qt6 screencast system-harfbuzz system-icu system-png system-zstd vaapi wayland widevine -bindist -cups -custom-cflags -debug -ffmpeg-chromium -gtk4 (-headless) -kerberos -pax-kernel (-pgo) (-selinux) -test" L10N="-af -am -ar -bg -bn -ca -cs -da -de -el -en-GB -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -ur -vi -zh-CN -zh-TW" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB
Thanks for confirming. Is it _only_ YouTube or any HTML5 video site? Does other audio work within Chromium? Since you've mentioned no sound but working video I'm curious; ffmpeg should be getting audio from whatever MPEG container the h264 stream is coming from... unless it's VP9. If you right-click on a video and select `stats for nerds`, it should show you the codec in use: Codecs av01.0.05M.08 (398) / opus (251) I can confirm that with 131.0.6778.24 (Official Build) (64-bit) I have working audio for the videos I've tried.
www-client/chromium-131.0.6778.24:0/beta::gentoo [131.0.6778.24:0/dev::gentoo] USE="X cups hangouts official proprietary-codecs pulseaudio qt5 qt6 screencast system-harfbuzz system-icu system-png system-zstd vaapi wayland widevine -bindist -custom-cflags -debug -ffmpeg-chromium -gtk4 (-headless) -kerberos -pax-kernel (-pgo) (-selinux) -test*" L10N="-af -am -ar -bg -bn -ca -cs -da -de -el -en-GB -es -es-419 -et -fa -fi -fil -fr -gu -he -hi -hr -hu -id -it -ja -kn -ko -lt -lv -ml -mr -ms -nb -nl -pl -pt-BR -pt-PT -ro -ru -sk -sl -sr -sv -sw -ta -te -th -tr -uk -ur -vi -zh-CN -zh-TW" 0 KiB
Codecs vp09.00.51.08.01.01.01.01.00 (247) / opus (251) From the look of it, it does seem that chromium is playing sound (but I can't hear anything). I got a new Lenovo monitor the day before I reported this, so it was after I lost sound. Sound was going to the new monitor, yesterday sound stopped completely, so I rebooted, then sound switched to my old monitor. I'm going to play around with cables, single head, HDMI/DP to see what happens, although it will be later in the day.
> From the look of it, it does seem that chromium is playing sound (but I can't hear anything). I once accidentally muted a game in KDE and it took me _months_ to work out why only that app was not playing audio. I'd gotten to the point of attaching a debugger and verifying that it was actually trying to use sound... Keep the ticket open and let us know what you work out. If you get stuck update the ticket and we can come up with some more suggestions on things to check. Suggest looking at your audio mixers (etc), If using KDE make sure that there is not a tiny "mute" icon instead of a speaker when the app is supposed to be playing audio. If I have any other thoughts I'll let you know.
In the pulseaudio control & KDE system sound settings, Firefox is shown as an application but chromium is not. If I unplug my older Samsung, so just using the newer Lenovo, neither Firefox nor chromium gives any sound, so the speakers on the Lenovo have died. With just the Samsung (Lenovo unplugged) Firefox has sound, chromium does not. In KDE sound setting I can select either device, test sounds work on the Samsung, not on the Lenovo. So I now know why sounds switched back to the Samsung, it's still mysterious why chromium is not appearing as a sound using application. I also plugged in my really old monitor, which is crap other than having quite good speakers. In that configuration Firefox sound switched to the old monitor, chromium still has no sound.
I found out that the Lenovo monitor does not have speakers, so I was wrong about loosing sound from it. I swapped the DP & HDMI cables over, so the HDMI is now in the Samsung monitor (which does have speakers), I had to swap sound to the HDMI as well. I still have sound in Firefox, but not in chromium. I think I've ruled out cabling & HDMI vs DP causes.
I played a video using Dragon Player & the sound works. It also shows up in the sound settings as an application. I have - notification sounds - speech-dispatcher-dummy:playback - Firefox ... youtube - dragonplayer: audio stream
OK so if there's no audio from Chromium we need to look into why that is. > In the pulseaudio control & KDE system sound settings, Firefox is shown as an application but chromium is not. We link directly against pulseaudio libs so if there was an issue there it _should_ have come up earlier. You have the pulseaudio USE enabled. The only real difference I can see between our builds is that you have CUPS disabled. There's no way that touching printing support should disable audio; right?
Created attachment 907988 [details] libtree /usr/lib64/chromium-browser/chrome Just in case, maybe compare with your system?
Created attachment 907989 [details] diff of my libtree with other attachment diff with my libtree first, then the other one.
Since sound was working 2 versions back, I quickpkg'd 131, deinstalled chromium, & I'm now installing 129. If sound works for it, it's probably a chromium problem, if it doesn't, it's likely something else that updated around the same time. It will probably be tomorrow before I have a result.
Regressed to 129 & no sound, so it's not chromium directly.
I've open a post in KDE Discuss, as KDE seems the most likely cause, but since I'm not sure I didn't post a bug. https://discuss.kde.org/t/chromium-not-in-pulseaudio-control-and-no-sound-from-it/25115
I also have this bug without KDE (Using sway). It seems to affect all Chromium based browsers, since there's no sound with the official ebuild, the ungoogled binary at ::pf4public and the steam launcher itself (games work correctly). With the "bindist" use flag, a "Aw, Snap!" page is shown when most webpages play sound (Youtube and online sound tests), for pages that load correctly (Unity WebGL games) no sound is played.
Created attachment 908768 [details] emerge --info of an unrelated problem, believed to be the same
(In reply to s7y7nqmof from comment #20) > It seems to affect all Chromium based browsers, since there's no sound with > the official ebuild, the ungoogled binary at ::pf4public and the steam > launcher itself (games work correctly). > > With the "bindist" use flag, a "Aw, Snap!" page is shown when most webpages > play sound (Youtube and online sound tests), for pages that load correctly > (Unity WebGL games) no sound is played. This sounds like a different issue. Please log a new bug and include the output of `emerge -pv www-client/chromium` and the console output from running Chromium and triggering a crash. It sounds a lot like your ffmpeg is hosed.
Comment on attachment 908768 [details] emerge --info of an unrelated problem, believed to be the same [ Was emerge --info of an unrelated problem, believed to be the same ]
Created attachment 908821 [details] emerge --info
I have found that the pulseaudio sink is unmuted. I believe pulse copies this to a "sink input" when an application plays sound. For Firefox, Dragon player, etc the sink input is unmuted. However for chromium it is muted. I can see this with "pacmd list". However I can't get it to see or report on a specific sink or sink input.
