Summary: | www-client/firefox-78: Enabling pulseaudio USE flag should give a message that ALSA will not work with firefox 78 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | segmentation fault <segmentation-fault> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
segmentation fault
2020-11-02 21:46:03 UTC
Technically alsa would work with USE=pulseaudio if you emerge apulse, and I'd argue it's the preferred way to use alsa with firefox because upstream hardly care to keep the native support in good shape (and will probably get removed entirely eventually). Firefox also has poor support for choosing output at runtime, at the base it expects you to use pulseaudio and nothing else (especially if built with it). Thanks for answering. Before upgrading to 78, I had 68.8.0 and don't remember to have had problems like this. My intention in writing this bug was to urge you to print some advice in the messages that appear after installation of a package. You can choose to do it in case one has disabled pulseaudio, or enabled it - or, probably better, both. Otherwise, how is one supposed to know what the "preferred way" is? Actually (and this has nothing to do with Gentoo or the ebuild), I have an aversion for software that fails so miserably on tasks so fundamental like "audio" or "video" and requires me to install extra software I wouldn't otherwise use - so I guess I'll take a notice of my open tabs in Firefox (as it currently spends more time crashing than doing useful work) and ditch it altogether. My main browser for daily use is PaleMoon anyway, so I will not miss anything - because (guess what) PaleMoon Just Works(TM)... :-) The exact semantics of USE flags like this aren't really defined. While most software does indeed still have an ALSA code path when built with USE=pulseaudio, that's not necessarily the case. Take note of all the software that merges apulse[sdk] instead of pulseaudio when the flag is disabled nowadays, for example. Those don't work without some form of pulseaudio library either, anymore. I think this is a more general Gentoo issue, since flags like "sdl" can also mean things like "prefer sdl-mixer instead of gtk for audio" or "build an sdl frontend", but I'm not sure how it'd be solved without creating a bunch of new and sometimes arbitrary USE flags. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6f52fc46e933f32f68a6a00cddffbff41be88fc3 commit 6f52fc46e933f32f68a6a00cddffbff41be88fc3 Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2023-07-05 07:41:27 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2023-07-05 07:59:42 +0000 www-client/firefox: redefine 'pulseaudio' flag to mention apulse Closes: https://bugs.gentoo.org/752387 Signed-off-by: Joonas Niilola <juippis@gentoo.org> www-client/firefox/metadata.xml | 2 ++ 1 file changed, 2 insertions(+) |