Window frozen unless cursor is moving with Sway / Qt6

[bascht]

Alright, here is an odd one - maybe someone has encountered something similar and knows a workaround. Since upgrading to the Qt6 version, my Qutebrowser window is literally stuck if I don't move the cursor.

Issue in full effect:

Left side: Qutebrowser v2.5.2, with tempdir, QtWebEngine 5.15.11
Right side: Qutebrowser v2.5.4, with tempdir, QtWebEngine 6.4.3

2023-04-17-104002.webm

With Qt6 any animation or even text rendering / page loading will only show if I move the cursor. As soon as the cursor movement stops, the window will freeze.

Details of the Qt6 version

``` ______ ,, ,.-"` | ,-` | .^ || | / ,-*^| || | ; / | || ;-*```^*. ; ; | |;,-*` \ | | | ,-*` ,-"""\ \ | \ ,-"` ,-^`| \ | \ `^^ ,-;| | ; | *; ,-*` || | / ;; `^^`` | || | ,^ / | || `^^` ,^ | _,"| _,-" -*` ****"""``

qutebrowser v2.5.2
Git commit:
Backend: QtWebEngine 5.15.11, based on Chromium 87.0.4280.144
Qt: 5.15.7

CPython: 3.10.9
PyQt: 5.15.9

sip: 6.6.2
colorama: no
jinja2: 3.1.2
pygments: 2.13.0
yaml: 6.0
adblock: 0.6.0
PyQt5.QtWebEngineWidgets: yes
PyQt5.QtWebEngine: 5.15.4
PyQt5.QtWebKitWidgets: no
pdf.js: 2.14.305 (/nix/store/9jbpp3148y5vhykmq0rmdwlpk7xq7ng8-source/build/pdf.js)
sqlite: 3.39.4
QtNetwork SSL: OpenSSL 3.0.8 7 Feb 2023

Style: QFusionStyle
Platform plugin: wayland-egl
OpenGL: AMD, 4.6 (Compatibility Profile) Mesa 22.2.5
Platform: Linux-5.15.94-x86_64-with-glibc2.35, 64bit
Linux distribution: NixOS 23.05 (Stoat) (nixos)
Frozen: False
Imported from /nix/store/d5j2jd8a7fyi1cl2vvwsx923j9fd3fa6-qutebrowser-2.5.2/lib/python3.10/site-packages/qutebrowser
Using Python from /nix/store/lyyf8kvn8fbgvwl9cypallvv032g47lr-python3-3.10.9/bin/python3
Qt library executable path: /nix/store/31grkiwl03rfcrcx5dd3dx0lkk3kxxhq-qtbase-5.15.7/libexec, data path: /nix/store/31grkiwl03rfcrcx5dd3dx0lkk3kxxhq-qtbase-5.15.7

Paths:
cache: /run/user/1000/qutebrowser-basedir-39a9lz62/cache
config: /run/user/1000/qutebrowser-basedir-39a9lz62/config
data: /run/user/1000/qutebrowser-basedir-39a9lz62/data
runtime: /run/user/1000/qutebrowser-basedir-39a9lz62/runtime
system data: /nix/store/d5j2jd8a7fyi1cl2vvwsx923j9fd3fa6-qutebrowser-2.5.2/share/qutebrowser

Autoconfig loaded: yes
Config.py: no config.py was loaded
Uptime: 0:00:00

</p>
</details> 

<details><summary>Details of the Qt5 version</summary>
<p>

    ______     ,,
,.-"`      | ,-` |

.^ || |
/ ,-^| || |
; / | || ;-```^.
; ; | |;,- \ | | | ,-* ,-"""\
| \ ,-"` ,-^`| \ |
\ `^^ ,-;| | ; |
; ,-` || | / ;;
`^^ | || | ,^ / | || `^^` ,^ | _,"| _,-" -*` ****"""

qutebrowser v2.5.4
Git commit:
Backend: QtWebEngine 6.4.3, based on Chromium 102.0.5005.177 (from override)
Qt: 6.4.3

CPython: 3.10.10
PyQt: 6.4.2

sip: no
colorama: no
jinja2: 3.1.2
pygments: 2.14.0
yaml: 6.0
adblock: 0.6.0
objc: no
PyQt6.QtWebEngineCore: 6.4.0
pdf.js: 2.14.305 (/nix/store/9jbpp3148y5vhykmq0rmdwlpk7xq7ng8-source/build/pdf.js)
sqlite: 3.41.2
QtNetwork SSL: OpenSSL 3.0.8 7 Feb 2023

Style: QFusionStyle
Platform plugin: wayland-egl
OpenGL: AMD, 4.6 (Compatibility Profile) Mesa 22.3.4
Platform: Linux-5.15.94-x86_64-with-glibc2.37, 64bit
Linux distribution: NixOS 23.05 (Stoat) (nixos)
Frozen: False
Imported from /nix/store/70bqik2nq38g6kw2cb2ljiqy3n9cgvyz-qutebrowser-unstable-2023-03-19/lib/python3.10/site-packages/qutebrowser
Using Python from /nix/store/fdqpyj613dr0v1l1lrzqhzay7sk4xg87-python3-3.10.10/bin/python3
Qt library executable path: /nix/store/d8g1cqiy0v21kshgjdgrydjzkwmigplg-qtbase-6.4.3/libexec, data path: /nix/store/d8g1cqiy0v21kshgjdgrydjzkwmigplg-qtbase-6.4.3

Paths:
cache: /tmp/qutebrowser-basedir-mxb13904/cache
config: /tmp/qutebrowser-basedir-mxb13904/config
data: /tmp/qutebrowser-basedir-mxb13904/data
runtime: /tmp/qutebrowser-basedir-mxb13904/runtime
system data: /nix/store/70bqik2nq38g6kw2cb2ljiqy3n9cgvyz-qutebrowser-unstable-2023-03-19/share/qutebrowser

Autoconfig loaded: yes
Config.py: no config.py was loaded
Uptime: 0:00:00

</p>
</details> 

Any hints? Otherwise it looks like I'll be downgrading to Qt5 again. :grin: 

[toofar]

Looks like #7532 which is apparently fixed by a slight newer mesa version than you are running.