Florian Bruhin

@tinywrkb How did you get Qt 6.4 to run? When trying to build the current PyQt6 snapshot against the beta 2, I get: ``` /tmp/tmpfu2ikqgr/QtGui/sipQtGuiQDragLeaveEvent.cpp:47:16: error: invalid covariant return type...

@tinywrkb ok, reproduced now. Let's keep this for new features (which likely aren't as important) and move the `--webEngineArgs` discussion to #7314 instead.

What does "has failed to open" mean precisely? Could you please do `:report` when it happens, so I could take a look at the logs?

Alright! Note there might not be much that qutebrowser can do in any case - this sounds more like an issue in the underlying QtWebEngine/Chromium.

Don't really see anything special in there I'm afraid. Have you tried the Qt 6 build from #7202?

Not sure if there's much qutebrowser can do about this. Could you check how this looks with a) another QtWebEngine-based browser such as KDE Falkon; and b) with Chromium?

@noisersup do you happen to be on Wayland and/or Nouveau graphics as well?

_Split to separate issue here_: https://github.com/qutebrowser/qutebrowser/issues/7621 # No focused element in insert mode **Still reproducible with the release candidate** ``` FAILED tests/end2end/test_insert_mode.py::test_insert_mode[100-textarea.html-qute-textarea-clipboard-qutebrowser] - end2end.fixtures.testprocess.WaitForTimeout: Timed out after 5000ms waiting for...

# Missing `--webEngineArgs` See [Introduce "--webEngineArgs" to prevent unexpected sub-process args (I57b3921d) · Gerrit Code Review](https://codereview.qt-project.org/c/qt/qtwebengine/+/376704). For a proper solution, we might want to split Qt and QtWebEngine args (#6065),...

_Looks like the same as #7621_ # Hinting in iframes **still reproducible with the release candidate** ``` FAILED tests/end2end/features/test_hints_bdd.py::test_using_hintfollow_inside_an_iframe_button - end2end.fixtures.testprocess.WaitForTimeout: Timed out after 5000ms waiting for {'message': 'navigation request:...