-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Comments
@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 |
I did have the same issue on Intel Xe and UHD Graphics 630 with new mesa and downgrading the mesa packages resolved it. |
As noted in this bug, exporting |
This fixes it. Thanks! Idk if I should close the issue now |
Please leave the issue open. We'll close when the workaround is no longer needed. |
I had a chance to try the
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. |
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-21.3.3-fix-bug-5731.patch try this patch from https://gitlab.freedesktop.org/mesa/mesa/-/issues/5731 |
Should be fixed in 1bf20e9 |
(please reopen if not) |
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):
This is my changed
/etc/modprobe.d/intel-graphics.conf
:I use AwesomeWM if that's related.
The text was updated successfully, but these errors were encountered: