https://bugs.kde.org/show_bug.cgi?id=377162
--- Comment #57 from Grósz Dániel <[email protected]> --- (In reply to Gordon Lack from comment #56) > (In reply to ✨ Audrey ✨ from comment #54) > > It wasn't disabled. It's not supported by the wayland protocol, which > > delegates control of a window to the client. > > Which makes it odd that when I first tried a Wayland session, some windows > (Wine ones?) actually COULD shade! > The fact that most could not is why I switched back to X11 very quickly. > > > Even to get that MR ready would take a lot of work, and there's no clear > > benefit. Based on earlier comments, AFAIK shading works under kwin_wayland for applications that use XWayland (an X11 compatibility layer), rather than native Wayland windows. It should be possible to tell all apps to use XWayland by setting some environment variables (clear WAYLAND_DISPLAY, or set toolkit-specific ones like QT_QPA_PLATFORM?); openSUSE for a few years shipped two KDE Wayland sessions, a "full wayland" one that had apps that support Wayland use native Wayland windows, and one that used kwin_wayland, but had apps connect to it using the X11 protocol, i.e. use XWayland. -- You are receiving this mail because: You are watching all bug changes.
