Open Bug 1839163 Opened 2 years ago Updated 2 years ago

INTEL: today Firefox did not start with vaap error

Categories

(Core :: Widget: Gtk, defect, P3)

Product:
Core
Component:
Widget: Gtk
Version:
Firefox 114
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: support, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/114.0

Steps to reproduce:

OS: Fedora 37
firefox-113.0.1-4.fc37.x86_64

Start Firefox

Actual results:

"today"/"this" refers to the 13-06-2023.

The problem today was, firefox failed to start. It told us, when started in a terminal, that VAAP tests failed.

A "vainfo" showed no more intel GPU drivers on the system:

/usr/lib64/dri/iHD_drv_video.so
/usr/lib64/dri/i965_drv_video.so

Those two were missing and no (Fedora) rpm provided them. Luckily rpmfusion provides a package. After installing libva-intel-driver , firefox still refused to start,
but could get reactivated in --safe-mode. After that, it started normaly again, without complaining about VAAP test fails.

I'm not 100% sure, if it failed because of the missing VAAP drivers or "just failed in general" due some internal hickup.

Expected results:

--

The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Graphics
Product: Firefox → Core
Component: Graphics → Widget: Gtk
OS: Unspecified → Linux
Hardware: Unspecified → x86_64

Please update to 114.0 package. Then try to run from terminal as:

MOZ_GFX_DEBUG=1 firefox > log.txt 2>&1

and attach the log here.

You may also test upstream binaries directly to avoid possible Fedora packaging bug:
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries

Thanks.

Flags: needinfo?(support)
Priority: -- → P3

As already written:

Firefox stopped complaining after installing libva-intel-drivers from rpmfusion
Firefox started again after starting it via --safe-mode once.

I got no new issue reports since.

The bugreport in RH Bugzilla was for the intel drivers issue, which Fedora should be able to ship directly.

This bugreport was about the hickup Firefox had. As we do not have, and won't get, new data why FF did not start,
this can't be more than a hint, that there is something going wrong in this version, if other users report the same issue.

If i had acquired a usable stacktrace, there would have been a chance to trace it, but we do not have one :(

Flags: needinfo?(support)

--safe-mode means without extensions. So it may not be related to VA-API at all. Firefox should always start no matter of VA-API/libva-intel-drivers state.

correct.. both issues could be just accidently found at the same time.

You need to log in before you can comment on or make changes to this bug.