| Summary: | [2023.1] Upgrade to 112.0.2 broke firefox: crash and coredump at startup - REGRESSION | ||
|---|---|---|---|
| Product: | [ROSA-based products] ROSA Fresh | Reporter: | Giovanni Mariani <mc2374> |
| Component: | Packages from Main | Assignee: | ROSA Linux Bugs <bugs> |
| Status: | RESOLVED FIXED | QA Contact: | ROSA Linux Bugs <bugs> |
| Severity: | critical | ||
| Priority: | High | CC: | a.proklov, m.novosyolov, s.matveev |
| Version: | Plasma5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Platform: | 2023.1 | ROSA Vulnerability identifier: | |
| RPM Package: | firefox-112.0.2-1.src.rpm | ISO-related: | |
| Bad POT generating: | Upstream: | ||
| Attachments: |
Dmesg output after firefox crash
Coredumpctl info about firefox core dump |
||
|
Description
Giovanni Mariani
2023-04-28 16:24:43 MSK
Hi, may be this link helps get more info (ex. vainfo) https://github.com/elFarto/nvidia-vaapi-driver/issues/131 (In reply to Aleksandr from comment #1) > Hi, may be this link helps get more info (ex. vainfo) > https://github.com/elFarto/nvidia-vaapi-driver/issues/131 Vainfo output: ***************** libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib64/dri/vmwgfx_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ***************** Evidently firefox cannot find the right driver (vmwgfx_drv_video.so does not exist at all AFAICT)... But then why did work seamlessly the version installed before the last update? Nothing changed in my vmware VM setup but the firefox package (even the firefox profile was the default one initially, no custom settings at all) and in the release notes for version 112.0.2 I did not find a clue about what changed from 112.0/112.0.1 to 112.0.2. Perhaps wayland-related? As in: https://bugzilla.mozilla.org/show_bug.cgi?id=1826583... (In reply to Giovanni Mariani from comment #2) > (In reply to Aleksandr from comment #1) > > Hi, may be this link helps get more info (ex. vainfo) > > https://github.com/elFarto/nvidia-vaapi-driver/issues/131 > > Vainfo output: > ***************** > libva info: VA-API version 1.14.0 > libva info: Trying to open /usr/lib64/dri/vmwgfx_drv_video.so > libva info: va_openDriver() returns -1 > vaInitialize failed with error code -1 (unknown libva error),exit > ***************** > > Evidently firefox cannot find the right driver (vmwgfx_drv_video.so does not > exist at all AFAICT)... > > But then why did work seamlessly the version installed before the last > update? > Nothing changed in my vmware VM setup but the firefox package (even the > firefox profile was the default one initially, no custom settings at all) > and in the release notes for version 112.0.2 I did not find a clue about > what changed from 112.0/112.0.1 to 112.0.2. > > Perhaps wayland-related? > As in: https://bugzilla.mozilla.org/show_bug.cgi?id=1826583... Install the lib64dri-drivers-vmwgfx package.Only I think it will not save because the 2023 branch is not stable. What does dmesg show about the crash? Created attachment 5882 [details]
Dmesg output after firefox crash
Created attachment 5883 [details]
Coredumpctl info about firefox core dump
In dmesg output I cannot see a thing evidently related to the vaapi error.
I have on disk the actual core dump (14 Mb), if needed.
(In reply to Svyatoslav Matveev from comment #3) > Install the lib64dri-drivers-vmwgfx package.Only I think it will not save > because the 2023 branch is not stable. The package is already installed: without it there is no real graphics support in the VM... We with Svyatoslav had a look at the backtrace (Svyatoslav reproduced the crash himself) and saw that it crashes somewhere internally in Firefox in code that handles CSS. That is very strange. I don't have ideas where the difference with rosa2021.1 may be. (In reply to Mikhail Novosyolov from comment #8) > We with Svyatoslav had a look at the backtrace (Svyatoslav reproduced the > crash himself) and saw that it crashes somewhere internally in Firefox in > code that handles CSS. That is very strange. I don't have ideas where the > difference with rosa2021.1 may be. Same thing here... perhaps trying to diff the two codebases related to CSS could give more clues? BTW, on 2021.1 the 112.0.2 release has this output in konsole:
************************
giovanni@Rivendell ~ $ firefox
(firefox-default:11564): Gtk-WARNING **: 17:03:43.332: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:43.332: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:43.472: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:43.472: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:43.544: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:43.544: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:43.569: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:43.569: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: option value of option mesa_glthread ignored.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: option value of option mesa_glthread ignored.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: option value of option mesa_glthread ignored.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: option value of option mesa_glthread ignored.
(firefox-default:11564): Gtk-WARNING **: 17:03:44.046: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:44.046: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:44.115: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:44.115: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:44.140: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name
(firefox-default:11564): Gtk-WARNING **: 17:03:44.140: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
[ERROR glean_core] Error setting metrics feature config: Json(Error("EOF while parsing a value", line: 1, column: 0))
************************
With the latest 115.0.2 now it works... closing. |