https://bugs.kde.org/show_bug.cgi?id=356225
--- Comment #297 from Michael Butash <mich...@butash.net> --- I have tried most of these things at some point. Different distributions on a clean build pc this last build, even different video, and found that the experience has been consistent in the same ways, particularly worse with these samsung 4k displays. Those being mostly the window placements and compositing stability over time. First was Ubuntu, probably with old data imported. I think it was suggested then to try a clean profile, so I did with no suitable difference, then later arch. Originally I was using an old ATI 7980 to drive 6x 1080p displays, and not only back to 4.x kde did it have issues dealing with the displays, but only marginally got better with 5.x. It worked better when using the oss ati drivers once they stabilized circa 2016, but then I upgraded the video and displays. Moving to nvidia and the 3x 4k displays, I moved to arch to even try a different distro, clean everything, but same compositing weirdness as before, plus now it also jumbled everything everything I powered down the displays. The compositing seems to deteriorate quicker with the 3x4k res too. Quickest and laziest solution I find is to not power them off. This means they remain on with a "no signal" message moving around all night, and burn power like mad still. I find doing so angers kde, cinnamon, or whatever DE, but all in very different, interesting ways. So yes, various ways I've gone through and purged all my .local and related kde files, or entirely new profile/drives, and can try again next weekend. It's tough to throw my main rig into a live cd, as it usually takes some time of use, and a few cycles of the displays coming and going before kde gets really angry. If I can do so over a few days, I will try this too, but need a long weekend without work. I do appreciate the help, and will try these. I'd love to see KDE just work again for myself and everyone, as I miss it - no other DE is quite like it. -- You are receiving this mail because: You are watching all bug changes.
