https://bugs.kde.org/show_bug.cgi?id=341497
Michael Butash <mich...@butash.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mich...@butash.net
--- Comment #59 from Michael Butash <mich...@butash.net> ---
Is a backport possible for 16.04 ubuntu users not likely to see this in lts
until 18.04?
Sadly, kde4 was terrible with unfixed bugs for setting up xrandr geometry as
well that made it unusable when relying on radeon modules, upgraded to 5 (and
16.04 to do so), was massively better, but affected by this now as well it
seems. Going back to 4 really isn't an option being left unresolved too.
I'm using 3x displays, 48" 4k samsung tv's as my desk monitors, which don't do
dpms keepalive over hdmi cables it seems. Rather they shut off/down, and "go
away" on the wire to the video card and xrandr, leaving it without a native
display, or your "dummy display" concept it seem to keep it sane when it has
none. Waking up the displays, and thus xrand + kde figuring out where to put
things back to, is an entire crapshoot now whether it 1) lives perfect, 2)
lives broken needing xrandr fixing, 3) needs sddm restart from different tty,
or 4) needs rebooted as nothing wakes it up. Feels windoze-y now.
Oddly, it doesn't always crash kwin, and sometimes recovers perfectly. Other
times not so much, but its very random sadly.
I've created xrandr scripts myself and with arandr to deal with it when kde5 as
a whole decides to go weird, but it's also seeming to have identity issues with
what is the "primary" display as well, as it seems to change upon these events
which is really primary, or which primary is really linked to which monitor
index. Sometimes I just have to try setting the primary monitor randomly to
figure out which it thinks is currently actually display 2 for example.
SDDM also has recovery issues with are likely to be related but their own
beast, yet systemic of the fact no one seems to actually test kde with multiple
monitors extensively. I was using kde4 happily with amd blob drivers and 6x
1080p montiors that did the setup itself for years, but using radeon now (with
4.x kernels that amd doesn't support yet for blob), which now works 2000x
better, breaks this with xrandr quirks like this.
--
You are receiving this mail because:
You are watching all bug changes.
