Summary: | www-client/firefox-108.0: fails to start and gives sandbox error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mickaël Bucas <mbucas> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | herrtimson |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mickaël Bucas
2022-12-18 21:55:29 UTC
Upgraded to www-client/firefox-108.0.1 Same problem Hmm, no immediate ideas. From the symptoms you describe it sounds like a vaapi issue, but your "hwaccel" is disabled. Maybe you have some weird profile settings (that'd overwrite hwaccel anyway). Can you try: 1) with a brand new firefox profile, 2) with the -bin version? With your CFLAGS (didn't read them all) it could also be some sort of an issue in a dependency - e.g. some time ago lto on system libdav1d/libvpx broke video playback in firefox. Now using www-client/firefox-108.0.2 CFLAGS are set this way for distcc. I can disable distcc for Firefox if it may lead to a solution. I tried the suggested options, but I get the same messages: - with a new profile - with www-client/firefox-bin-108.0.2 I've been able to make some progress. Before, I was having a message about "VA-API test failed", then many "signal 15" or "signal 11" errors $ MOZ_DISABLE_CONTENT_SANDBOX=1 firefox Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: VA-API test failed: failed to initialise VAAPI connection. (t=0.577445) [GFX1-]: glxtest: VA-API test failed: failed to initialise VAAPI connection. [Parent 1012, IPC I/O Parent] WARNING: process 2391 exited on signal 15: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 1012, IPC I/O Parent] WARNING: process 18384 exited on signal 15: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 1012, IPC I/O Parent] WARNING: process 29230 exited on signal 15: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 1012, IPC I/O Parent] WARNING: process 7211 exited on signal 15: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 1012, IPC I/O Parent] WARNING: process 14381 exited on signal 15: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 1012, IPC I/O Parent] WARNING: process 25733 exited on signal 15: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 1012, IPC I/O Parent] WARNING: process 3619 exited on signal 15: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 1012, IPC I/O Parent] WARNING: process 17876 exited on signal 15: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 1012, IPC I/O Parent] WARNING: process 1493 exited on signal 11: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 1012, IPC I/O Parent] WARNING: process 1079 exited on signal 11: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 I've enabled "vaapi" USE flag globally, "hwaccel" USE flag for Firefox and recompiled. I also discovered that x11-libs/libva-vdpau-driver was removed some time ago (https://bugs.gentoo.org/866557), so I tried the driver from https://github.com/elFarto/nvidia-vaapi-driver using the ebuild from https://github.com/Tatsh/tatsh-overlay/tree/master/media-plugins/nvidia-vaapi-driver VA-API seems to work: $ export LIBVA_DRIVER_NAME=nvdec $ vainfo Trying display: x11 libva info: VA-API version 1.16.0 libva info: User environment variable requested driver 'nvdec' libva info: Trying to open /usr/lib64/va/drivers/nvdec_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.16 (libva 2.16.0) vainfo: Driver version: VA-API NVDEC driver [egl backend] vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD <unknown profile> : VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD Now I've no more messages about VA-API from Firefox, but I still get error messages, and video still doesn't work. $ export LIBVA_DRIVER_NAME=nvdec $ MOZ_DISABLE_CONTENT_SANDBOX=1 firefox [2023-01-13T23:16:57Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-01-13T23:16:57Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-01-13T23:16:57Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-01-13T23:16:57Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-01-13T23:17:11Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-01-13T23:17:11Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-01-13T23:17:11Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-01-13T23:17:12Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [Parent 6173, IPC I/O Parent] WARNING: process 7802 exited on signal 11: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 6173, IPC I/O Parent] WARNING: process 7820 exited on signal 11: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 6173, IPC I/O Parent] WARNING: process 7968 exited on signal 11: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 6173, IPC I/O Parent] WARNING: process 7994 exited on signal 11: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 6173, IPC I/O Parent] WARNING: process 8065 exited on signal 11: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 6173, IPC I/O Parent] WARNING: process 8097 exited on signal 11: file /var/tmp/portage/www-client/firefox-108.0.2/work/firefox-108.0.2/ipc/chromium/src/base/process_util_posix.cc:256 If it happens with firefox-bin I fear it's upstream-related and not Gentoo. So you should take it upstream from here :I However with firefox-109.0 (pushed today) there's a configure option, --enable-real-time-tracing, that helps to debug these video/audio issues. I've turned it off as: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9015dd67ba712b2cde668d3659f2a1571fa698bb but you should try to update to 109, enable the flag and see if you get more verbose / exact messages. Also check your dmesg, it may contain other kind of hints. And yeah I'd suggest turning distcc off and compiling firefox with "-march=native -O3 -pipe", although it may be a long shot. Could also discover firefox isn't distcc'able anymore... (In reply to Joonas Niilola from comment #4) > > However with firefox-109.0 (pushed today) there's a configure option, > --enable-real-time-tracing, that helps to debug these video/audio issues. > I've turned it off as: > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=9015dd67ba712b2cde668d3659f2a1571fa698bb > Oh right forgot to mention: EXTRA_ECONF="--enable-real-time-tracing" 'emerge -uav firefox' should do the trick. You can use package.env too. Firefox 109.0.1 Problem solved, though I can't tell what was the real cause. Recently GCC 12 became stable, so I updated my desktop and my distcc servers to this version. Then I recompiled everything with "emerge -e @world" and genkernel and after a reboot, Firefox works normally. The good news is that distcc wasn't involved. I suspect something was wrong with my previous kernel and the Nvidia proprietary driver. I still get some messages, without consequences: $ LIBVA_DRIVER_NAME=nvdec firefox [2023-02-06T19:10:46Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-02-06T19:10:46Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-02-06T19:10:48Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-02-06T19:10:48Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-02-06T19:11:48Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-02-06T19:11:48Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-02-06T19:11:49Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2023-02-06T19:11:49Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [Parent 8333, IPC I/O Parent] WARNING: process 12832 exited on signal 15: file /var/tmp/portage/www-client/firefox-109.0.1/work/firefox-109.0.1/ipc/chromium/src/base/process_util_posix.cc:256 [Parent 8333, IPC I/O Parent] WARNING: process 21058 exited on signal 15: file /var/tmp/portage/www-client/firefox-109.0.1/work/firefox-109.0.1/ipc/chromium/src/base/process_util_posix.cc:256 Hey, well glad it got solved. By disabling distcc I presume? If you're referring to the mp4parse "ERRORS" they're just harmless debug messages. A fix for that has been landed in https://bugzilla.mozilla.org/show_bug.cgi?id=1810613 on Firefox-111. Looking at the file time of /etc/portage/package.env/firefox, distcc was disabled for firefox even before the problem occurred. |