https://bugs.kde.org/show_bug.cgi?id=457487
--- Comment #4 from Luke-Jr <luke-jr+kdeb...@utopios.org> --- (In reply to Hans-Peter Jansen from comment #3) > (In reply to Luke-Jr from comment #2) > > Is this going to get fixed? (Alternatively, is there a maintained fork of > > KWin somewhere out there we can switch to?) > > Be careful with such expressions: kwin is maintained! Not fixing a major regression like this after so long would lead one to think otherwise ;) > It's the X11 part, > that is problematic, and here, it's related to a feature, that doesn't even > exist under wayland, yet! If you want this feature for wayland, please show > your interest here: https://bugs.kde.org/show_bug.cgi?id=377162 My approach for now is to simply not use Wayland. It seems to introduce problems and regressions like this, for no benefit. > FTR: I tried different approaches already to backport to an earlier state of > the shaded window feature, aas well as backing out those changes, in order > to get back to the state of the good ol' times, but the kwin codebase was > shuffled around so heavily, that it would end up into something similar, > what Vlad did already. Duuh. This is what I'm successfully using as of 5.26.1: http://dpaste.com/EHULW6PHM The only thing that seems broken is if I maximise a shaded window, unshade it, then try to unmaximise. But I'm not sure if that ever worked. Shading and replacing kwin does seem to be fine, though. -- You are receiving this mail because: You are watching all bug changes.
