Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with qutebrowser (and only it) after Mesa upgrade #34674

Closed
intpl opened this issue Dec 23, 2021 · 11 comments
Closed

Problem with qutebrowser (and only it) after Mesa upgrade #34674

intpl opened this issue Dec 23, 2021 · 11 comments
Labels
bug Something isn't working

Comments

@intpl
Copy link

intpl commented Dec 23, 2021

After system upgrade three days ago Qutebrowser started to behave terribly. Entire window become white for milliseconds, scattered parts of window. Pretty much unusable. Chromium and Google Chrome and Firefox which I have installed on the system all work fine. The issue is only with Qutebrowser. It worked perfectly fine before the upgrade.

I can see in the xbps log these 4 Mesa packages were updated (but also libglapi and libgbm which may also be related):

mesa-21.3.2_1
mesa-dri-21.3.2_1
mesa-intel-dri-21.3.2_1
mesa-vulkan-intel-21.3.2_1

This is my changed /etc/modprobe.d/intel-graphics.conf:

options i915 enable_dc=2 enable_fbc=1 fastboot=1

I use AwesomeWM if that's related.

@intpl
Copy link
Author

intpl commented Dec 23, 2021

qb-scatter
Things like this happening all the time

@ericonr
Copy link
Member

ericonr commented Dec 23, 2021

@ahesford has had the same issues, I believe.

Downgrading the packages locally can fix it temporarily, fwiw.

Possibly https://gitlab.freedesktop.org/mesa/mesa/-/issues/5745

@ericonr ericonr added the bug Something isn't working label Dec 23, 2021
@ahesford
Copy link
Member

I did have the same issue on Intel Xe and UHD Graphics 630 with new mesa and downgrading the mesa packages resolved it.

@jsbronder
Copy link
Contributor

As noted in this bug, exporting MESA_LOADER_DRIVER_OVERRIDE=i965 appears to have resolved this for me.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/5744

@intpl
Copy link
Author

intpl commented Dec 24, 2021

As noted in this bug, exporting MESA_LOADER_DRIVER_OVERRIDE=i965 appears to have resolved this for me.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/5744

This fixes it. Thanks! Idk if I should close the issue now

@intpl intpl changed the title Problem with qutebrowser (and only it) after Mesa upgrade [solved] Problem with qutebrowser (and only it) after Mesa upgrade Dec 24, 2021
@ahesford
Copy link
Member

Please leave the issue open. We'll close when the workaround is no longer needed.

@ahesford
Copy link
Member

I had a chance to try the MESA_LOADER_DRIVER_OVERRIDE workaround (it isn't really a fix) on an Intel Xe device, and was met with errors reporting

gfx12 and newer are not supported on i965
libGL error: failed to create dri screen
libGL error: failed to load driver: i965

There were no glitches, but it seems Mesa fails entirely here. Thus, the workaround seems to be limited to older devices.

It seems that a proper fix may have been merged; maybe we can test a backport pending another upstream release.

@ahesford ahesford changed the title [solved] Problem with qutebrowser (and only it) after Mesa upgrade Problem with qutebrowser (and only it) after Mesa upgrade Dec 27, 2021
@intpl
Copy link
Author

intpl commented Jan 1, 2022

in case anybody is wondering, installing 21.3.3 from this commit does NOT fix the issue: #34768

again, for wonderers: no WebGL support when setting MESA_LOADER_DRIVER_OVERRIDE=i965 can be fixed by providing --qt-flag ignore-gpu-blocklist argument to qutebrowser (btw you may want to enable --qt-flag enable-gpu-rasterization also)

@ardadem
Copy link
Contributor

ardadem commented Jan 8, 2022

@ericonr
Copy link
Member

ericonr commented Feb 5, 2022

Should be fixed in 1bf20e9

@ericonr
Copy link
Member

ericonr commented Feb 5, 2022

(please reopen if not)

@ericonr ericonr closed this as completed Feb 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants