glxtest error when starting ESR 91.3.0 on Linux via ssh X forwarding
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | fixed |
firefox93 | --- | unaffected |
firefox94 | --- | wontfix |
firefox95 | --- | fixed |
People
(Reporter: james-p, Assigned: rmader)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
When starting ESR 91.3.0 on Linux (CentOS 7.9) via ssh X forwarding, the following is output to the terminal:
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: X error, error_code=1, request_code=143, minor_code=32 (t=1.85423) [GFX1-]: glxtest: X error, error_code=1, request_code=143, minor_code=32
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: X error, error_code=1, request_code=143, minor_code=32 (t=1.85423) |[1][GFX1-]: glxtest: process failed (exited with status 1) (t=1.85432) [GFX1-]: glxtest: process failed (exited with status 1)
Firefox appears to start and work OK
This doesn't happen with ESR 91.2.0 via ssh X forwarding
Starting ESR 91.3.0 directly on a workstation doesn't output these 'errors' - only happens when using X forwarding over ssh
I'm assuming the errors are harmless?
Comment 1•3 years ago
|
||
Thanks for the report!
https://hg.mozilla.org/releases/mozilla-esr91/pushloghtml?fromchange=FIREFOX_91_2_0esr_RELEASE&tochange=FIREFOX_91_3_0esr_RELEASE
The error is most likely caused by:
95c4aa0fd3dab04aec9981111cc3da2ad1d400b6 Robert Mader — Bug 1710400 - Blocklist HW-WR on Intel DDX driver, r=aosmond a=RyanVM
bug 1737499 comment 16 found out that a minimum version check is required for xrandr because X11 forwarding has a different and extremely outdated xrandr version.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
This was fixed in FF 95 by https://phabricator.services.mozilla.com/D129522 / bug 1737499. For ESR we'd need to backport the toolkit/xre/glxtest.cpp
part of that. Ryan, can you do that easily or should I prepare a patch?
Comment 3•3 years ago
|
||
Go ahead and post a backport patch here and request uplift.
Assignee | ||
Comment 4•3 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #3)
Go ahead and post a backport patch here and request uplift.
Ah, I see, the backport was not completely trivial (which is why I didn't do a backport right away). Uplift request in bug 1737499 comment 29.
Comment 5•3 years ago
|
||
bugherder uplift |
Description
•