Hiya,
When installing latest Anki from the website tar dist, it does not run my PC. I’m using SwayWM with QT_QPA_PLATFORM=wayland . I’m guessing some Wayland client libs are missing from the bundled Qt distribution.
Output:
Qt warning: QSocketNotifier: Can only be used with threads started with QThread
Qt warning: Failed to load client buffer integration: "wayland-egl"
Qt warning: Available client buffer integrations: ()
Qt warning: No shell integration named "xdg-shell" found
Qt warning: No shell integration named "xdg-shell-v6" found
Qt warning: No shell integration named "wl-shell" found
Qt warning: No shell integration named "ivi-shell" found
Qt warning: Loading shell integration failed.
Qt warning: Attempted to load the following shells ("xdg-shell", "xdg-shell-v6", "wl-shell", "ivi-shell")
Qt warning: Wayland does not support QWindow::requestActivate()
install anki from pip (sudo pip install anki aqt)
this works fine as it uses my system Qt libs (in fact I’d go so far as to recommend this to other Linux users as it also picks up my desktop themes, settings etc)
run anki with QT_QPA_PLATFORM=xcb
For reference, here is output from pip-installed anki, which works:
Output from pip-installed anki with QT_DEBUG_PLUGINS=1: pip anki output - Pastebin.com
N.B. I tried to include the above pastes in this with <details><summary> etc, but it went over the post size limit
Is there anyone else successfully using the packaged builds with Wayland? If it’s universally broken then perhaps it would make sense to force the platform to xcb on startup.
Thanks for looking into this - for anyone else testing, could you check as well if your Anki is using xwayland or native Wayland? Some distros will set xwayland as default for Qt via env vars.
It would be good if the package build could support native Wayland so you get e.g. proper scaling when you drag the window from a high dpi laptop screen to a normal dpi desktop monitor… But showing the window at all will still be an improvement
I’ve pushed a change that should force xcb if wayland is set when running the packaged build - please let me know if that at least allows startup when the next alpha is available. Native support would of course be preferable, but that’ll need to wait for now.
