https://bugs.kde.org/show_bug.cgi?id=475653
Michael Butash <mich...@butash.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mich...@butash.net
--- Comment #1 from Michael Butash <mich...@butash.net> ---
I get a similar issue with mine my primary display changes randomly with
hotplug events using same, nvidia gpu and wayland on a laptop (hard set to
nvidia-only in bios). When displays change their ID with every hotplug with
Wayland, I find every time KDE plays 50 first dates with building a new config
for it. This means my primary window changes between displays, latte errors out
and doesn't show my bars anymore (it sees a new graphic config when displays
change), and worst at times it just hard locks in doing so when combined with
the constant memory leak I have in kwin.
Every time my displays change, KDE chooses random ID's for them (DP-1, DP-3,
DP-5), and it wreaks havoc on things. I suspect yours might be similar. Until
someone makes wayland far more deterministic around display ID's, I suspect kde
will remain a basketcase for multi-monitor.
After a while, I find KDE builds like 50 different display configs for them
each time it changes randomly, which seems to just confuse the hell out of
things. Per Nate Graham, clearing them fixed things, but they start building up
with the shuffling again over time, and each time clearing them makes my life
better since learning this, which I've done periodically over a bit since
figuring this out. You probably should as well with hot plugging your second
display probably causes similar.
My problem is mostly thunderbolt docks, randomly mine resets, jumbles things,
makes a mess of everything. If KDE/Wayland continue to jumble displays every
time as a result, and creates new tuples of display variations, it'll continue
to cause a ruckus.
--
You are receiving this mail because:
You are watching all bug changes.
