https://bugs.kde.org/show_bug.cgi?id=436218
Fabio <ctrlal...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Resolution|DUPLICATE |---
Status|RESOLVED |REOPENED
--- Comment #3 from Fabio <ctrlal...@gmail.com> ---
I'm now running spectacle 21.04.2 on plasma 5.22, and the bug is still present.
I saw the introduction of the new PlatformKWinWayland2 interface but it still
uses QGuiApplication::screens() to get the screen name used in the dbus request
to KWin.
When running spectacle in a mixed wayland/xwayland session (as used by suse and
slackware), spectacle will default using the xcb backend.
This means that QGuiApplication::screens() will return the dummy XWayland
screen, while KWin expects to get a request for a Wayland screen name.
This obviously fails.
My current workaround just comments out QGuiApplication::screens() and
hardcodes my laptop screen name QStringLiteral("eDP-1"), but that's obviously a
dirty hack.
I found no way from a qt app running inside xwayland to get the wayland screen
names.
I can see a few possible solutions to this problem:
* let kwin enumerate the available screens somewhere in its dbus interface for
spectacle to pick it up
* always force spectacle to use the wayland backend if available
--
You are receiving this mail because:
You are watching all bug changes.
