https://bugs.kde.org/show_bug.cgi?id=383410
--- Comment #8 from Martin Flöser <mgraess...@kde.org> --- I just created a test case for the situation and this results in: wl_surface@13: error 1: Surface already constrained It looks to me like what XWayland does is not valid on Wayland. And I just checked with the spec (https://cgit.freedesktop.org/wayland/wayland-protocols/tree/unstable/pointer-constraints/pointer-constraints-unstable-v1.xml): " For any surface, only one lock or confinement may be active across all wl_pointer objects of the same seat. If a lock or confinement is requested when another lock or confinement is active or requested on the same surface and with any of the wl_pointer objects of the same seat, an 'already_constrained' error will be raised." The problem might now be that XWayland gets a protocol error that causes the hang in KWin as XWayland goes down. I think the change in XWayland should be reverted or fixed ASAP! -- You are receiving this mail because: You are watching all bug changes.
