https://bugs.kde.org/show_bug.cgi?id=393881
Duncan <1i5t5.dun...@cox.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |1i5t5.dun...@cox.net
--- Comment #3 from Duncan <1i5t5.dun...@cox.net> ---
This is very likely a dup of (my) bug #389141, filed back when the problem was
probably still in unreleased live-git only. Unfortunately it wasn't fixed, tho
I can't say my bug report was as good a quality as I'd have liked and I never
did get the bisect done I wanted to do.
I too have two displays, one a 4k/3840x2160, the other a full-hd/1920x1080.
Tho in my case the problem appeared after the screen-blanker activated (no
lockscreen configured) and the monitors, having no signal any longer,
automatically turned off, when I turned them back on -- no actual need to
logout/reboot. Another difference, my higher-res 4k primary is to the right of
the full-hd secondary, while in your case it's to the left.
But an additional behavior detail I noticed after I filed the bug, that I had
been meaning to add, that from your screenshots applies in your case to:
Plasmashell is apparently mistakenly repositioning the widget to conform to the
lower full-hd resolution of the /other/ monitor in an effort to keep it
in-frame/on-monitor, failing to account for the larger 4k resolution of the
monitor it's actually on. With the monitor-relative 0,0 origin at top-left and
the 4k monitor being twice the resolution of the smaller one in each direction,
the top-left quadrant is the monitor-relative size and position of the smaller
monitor, so the repositioning is into it.
Thus, anything outside the top-left quadrant will be repositioned into it,
while anything in it should stay where it is.
Hopefully with this additional description of the apparent repositioning
trigger for the bug we're both seeing, they can figure out what's going wrong
and patch it. =:^)
Meanwhile, here's a workaround (assuming you can't just put your widgets into
the top-left quadrant as a workaround) that I've been using here that should
help: Find the plasma-org.kde.plasma.desktop-appletsrc file in your config (my
settings are customized but check in ~/.config and its subdirs) and set it
read-only when it has the correct config (as it should if you setup the widgets
as you want and then killall plasmashell, you can restart it again from krunner
after setting the file readonly). That should prevent the bad positioning from
being written to the file, but note that you'll need to set it writable again
to make other changes to your widgets and panels or most of them (the ones
saved in that file) won't save either.
With the file set read-only, I'm not sure if plasma will set the correct
position at bootup/login, it may depend on the monitor detection and setup
sequence as plasma starts up, but if not you can always killall plasmashell and
restart it again, and it should then load the correct config.
--
You are receiving this mail because:
You are watching all bug changes.
