https://bugs.kde.org/show_bug.cgi?id=374908
--- Comment #11 from John B <john+kde_...@daaave.org> --- As an alternative to waiting for this to be addressed in a more robust manner, would it be possible to just have kwin completely ignore the displays when it comes to this? In other words, don't rearrange the windows even if I do physically disconnect the display; just _never_ rearrange anything. Not windows, not Plasma widgets, not panels...nothing. I realize the gotcha to this is that if you do actually disconnect a monitor (or there's a hardware failure, etc.) then you're going to have to be brushed up on your kwin fu to be able to get them back, but the blunt reality of the situation for those of us with multiple DisplayPort monitors is thus: 1. Do we want a system that does what we want once every 3-5 years when we replace a monitor, or 2. ...do we want a system that does what we want 5-10 times per day when the displays' power save kicks in? Notes: 1. This behaviour should be optional. If nothing else, laptop users who (un)dock a lot may very well prefer the current behaviour. 2. The default setting of this option should be to have it turned off; first off because changing defaults violates the Principle of Least Surprise, but also because having to rearrange your windows 5-10 times per day is annoying but "permanently" losing an important window is _much worse_ for someone who doesn't know how to get it back. 3. Since we're not rearranging windows any more, we need to account for the edge case where you actually _do_ lose a display unexpectedly (let's say you have a hardware failure). This is fine (for people who have enabled this functionality) unless the display you lose is the primary, at which point the main panel that you need to re-home your windows is gone. I propose adding an item to the context menu that you get when you right-click on the desktop that says "Make this display the primary" that executes the same code that would normally execute if you went into the Control Center and fiddled the appropriate checkbox. This also brings the K menu back to a visible display, so that you can (for example) reconfigure the panel so that all applications show on all displays. YES YES YES I fully and completely understand that #3 is fiddly as all get out. The only reason I'm asking for any of this is because the status quo is EVEN WORSE. I am to the point where I'm about to buy physical adapters to proxy my DP GPU and DP monitors through HDMI or DVI so that the OS can't see the power state changes, even if it means having to change the resolution from 4K to 1080p to avoid spending a zillion dollars. :) Fun fact: I was looking around on the Internet trying to figure out how MS Windows handles this problem, 'cause I get how hard it is to figure out what the "right behaviour" should be, before we even talk about writing code (that's why I used the phrase "do what we want" above, instead :P). Turns out...it doesn't. I guess I've never seen an MSW machine with multiple DP displays, but there's reports out there in the wild from Win10 users having this same problem. So this isn't just a KDE issue or even a GNU/Linux issue, it's a legitimate new conceptual problem that the advent of DisplayPort (and other display protocols that the OS can actually detect a disconnection of) has brought to the table. -- You are receiving this mail because: You are watching all bug changes.
