Freeze with Qt 6.6.3 + NVidia + Wayland/wlroots #8154
Comments
andyhunne
changed the title
|
Which Qt package specifically is the cause of this? How did you find which one to downgrade? |
|
No issues here (~150 tabs opened): qutebrowser v3.1.0 ... Style: QFusionStyle |
|
I don't know the specific one, but my hunch was the Qt6 upgrade I'd performed earlier in the day was the cause as I've had this happen before. Previously it was qt6-webkit that was the issue. I just downgraded all of them as I was in a bit of a rush to get back to work, rebooted and it resolved. Downgrade was done with the following procedure: And for the moment, adding the following line to /etc/pacman.conf will ignore the qt6 upgrades: |
|
Works fine for me too (though I only tried X11, not Wayland). I also asked in IRC, and nobody there seems to have the same issue with Qt 6.6.3, even with someone on Wayland. @andyhunne could you see how things look if you run the testbrowser script? |
|
Hello, I have the same issue. The browser hangs completely and i had to kill it. Didn't have the time to investigate yet. Hyprland,Wayland and Nvidia |
|
A few questions for people who are affected:
|
|
Also, if this is NVidia specific: Long shot, but does If so, this is the culprit: |
|
Hi @The-Compiler, I've debugged a little, here are my findings:
All observations were tested with the testbrowser script. My version settings, currently writing this in Hyprland + Intel. Hope this helps! |
|
@The-Compiler Will try to test later today with your suggested steps, but I did try the testbrowser script when the problem initially surfaced already, and had the same results. |
|
export QT_OPENGL_NO_SANITY_CHECK=1 works |
The-Compiler
changed the title
|
Originally thought it'd be wlroots-specific but I can reproduce with Gnome/mutter, Plasma 6/kwin, and Hyprland + NVIDIA (1070 card w/ 550.67 drivers), so probably safe to say it's wayland+nvidia anything. In all 3 case QT_OPENGL_NO_SANITY_CHECK=1 indeed did the trick, fwiw it also unsurprisingly works when using xwayland (QT_QPA_PLATFORM=xcb). That was with Qt6.6.3, but I'm going to try 6.7.0 later (need to compile webengine so it'll be some time). |
|
I can confirm this workaround (QT_OPENGL_NO_SANITY_CHECK=1) also works for me |
No issues with 6.7.0 that I could see, no workarounds needed. Edit: haven't took time to look at the git history / bugs but kind of wish I knew what fixed it so could potentially backport in qtwayland-6.6.3 without rushing 6.7.0 to stable users in Gentoo -- albeit qtwebengine itself bumped chromium among other major changes so perhaps it just no longer cause issues rather than a fix in qtwayland |
Same issue here, and this worked for me. |
|
https://bugreports.qt.io/browse/QTBUG-124174 exists now, which pretty much confirms what's already known here Recent comments gave some insight on why 6.7.0 is fine despite qtwayland remaining unchanged in that regard, which is most likely because of qt/qtwebengine@088408f from a quick look. So if do a qutebrowser-side workaround, it's really only needed with exactly 6.6.3 -- In Gentoo we got rid of 6.6.3 at this point so not going to worry about it though. |
Version info:
qutebrowser v3.1.0
Git commit: 3d86d78 on main (2024-03-27 23:58:36 +0100)
Backend: QtWebEngine 6.6.2, based on Chromium 112.0.5615.213 (from api)
Qt: 6.6.2 (compiled 6.6.3)
CPython: 3.11.8
PyQt: 6.6.1
Qt wrapper info:
PyQt6: success
PyQt5: not imported
-> selected: PyQt6 (via autoselect)
colorama: 0.4.6
jinja2: 3.1.3
pygments: 2.17.2
yaml: 6.0.1
adblock: 0.6.0
objc: no
PyQt6.QtWebEngineCore: 6.6.0
PyQt6.sip: 6.7.12
pdf.js: 4.0.379 (/usr/share/pdf.js/build/pdf.mjs)
sqlite: 3.45.2
QtNetwork SSL: OpenSSL 3.2.1 30 Jan 2024
Style: Qt6CTProxyStyle
Platform plugin: wayland
OpenGL: OpenGL ES
Platform: Linux-6.8.2-arch2-1-x86_64-with-glibc2.39, 64bit
Linux distribution: Arch Linux (arch)
Frozen: False
Imported from /usr/lib/python3.11/site-packages/qutebrowser
Using Python from /usr/bin/python3
Qt library executable path: /usr/lib/qt6, data path: /usr/share/qt6
Paths:
cache: /home/andy/.cache/qutebrowser
config: /home/andy/.config/qutebrowser
data: /home/andy/.local/share/qutebrowser
runtime: /run/user/1000/qutebrowser
system data: /usr/share/qutebrowser
Autoconfig loaded: yes
Config.py: /home/andy/.config/qutebrowser/config.py has been loaded
Uptime: 3:29:53
I tried the *-git version of qutebrowser for initial troubleshooting. The issue is also present with the non git version, v3.1.0 from Arch repos.
Does the bug happen if you start with
--temp-basedir?:Yes
Description
Upgrading to Qt 6.6.3 causes qutebrowser to freeze & become unresonsive.
How to reproduce
Upgrade to Qt 6.6.3, and watch qutebrowser freeze for a running session, or any subsequently launched sessions.
Downgrade to Qt 6.6.2 and the problem is 'fixed'.
Apologies for the lack of further info - I needed to downgrade to get back to work. Posting this for more of a warning/caution to fellow Arch users. Please let me know any further info you'd like to assist with troubleshooting.
The text was updated successfully, but these errors were encountered: