https://bugs.kde.org/show_bug.cgi?id=359531
Martin Gräßlin <mgraess...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Martin Gräßlin <mgraess...@kde.org> ---
xdg_shell is not yet a standardized protocol with API compatibility guarantees.
This makes it almost impossible to wrap it in an ABI stable library as KWayland
is.
Even if we added support for it, it is unlikely that this would solve the
problem of gtk applications crashing. Due to the unstable xdg_shell one needs
to have exactly the same version of the unstable protocol to have it working.
As GTK+, Wayland, Qt and KWin releases are not synced it becomes unlikely that
all of them have the same magic version. KWin would probably follow the version
used in the QtWayland release of the Qt build dep. That's about 1 year behind
what Wayland has and thus most likely also behind what GTK+ has. Given that it
would still not work.
Overall that's the reason why I so far refused to spend time on adding support
for xdg_shell. I simply don't see how it would fix anything of this
compatibility issue. I have it on my todo list, but it will be hidden behind an
explicit compile time flag. This is the only way how we can solve the API
instability problem in our stable KWayland library.
Obviously the problem here is that gtk hard depends on an unreleased, not
standardized interface. It should check whether it exists and if not either
exit (heck one could also use X11, no need to crash just because there's a
Wayland socket) or fall back to wl_shell as Qt does.
I'm setting to INVALID as the bug in question is in GTK and not in KWin.
Support for xdg_shell will be added eventually but I do not see the lack of
support for an unstable interface as a bug in KWin.
--
You are receiving this mail because:
You are watching all bug changes.
