[kwin] [Bug 396711] Feature request: disable display hotplug (KWin Wayland)
https://bugs.kde.org/show_bug.cgi?id=396711 Roman Gilg changed: What|Removed |Added CC||subd...@gmail.com Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #4 from Roman Gilg --- What is meant by "removing input"? This doesn't sound like a bug that is very common. Closing for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396711] Feature request: disable display hotplug (KWin Wayland)
https://bugs.kde.org/show_bug.cgi?id=396711 --- Comment #3 from DevPre24 --- I found a hardware workaround, i had one of those cheap hdmi to dvi converters lying around, i got it straight from china for not more than 90 euro cents and with the help of this tutorial (Link: https://meanwhileblog.wordpress.com/2016/01/08/disable-hot-plug-detect/ ) i removed the hotplug pin. It's more of a workaround than of a solution, i will report the individual bugs as soon as i have a little bit of spare time and i can reproduce them on my laptop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396711] Feature request: disable display hotplug (KWin Wayland)
https://bugs.kde.org/show_bug.cgi?id=396711 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- > To go back to the previous state not only i have to switch back inputs but > also restart the session. In any case, this part is a bug that needs fixing. Same for the bit about the task manager. If you can file individual bugs about those, they'll get addressed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396711] Feature request: disable display hotplug (KWin Wayland)
https://bugs.kde.org/show_bug.cgi?id=396711 Martin Flöser changed: What|Removed |Added Component|wayland-generic |platform-drm Flags||Wayland+, X11- --- Comment #1 from Martin Flöser --- This is quite a corner case. Most monitors I have seen don't disconnect when switching inputs. I'm not sure whether we can add a workaround for such hardware. Our output handling is based on hutplug. I doubt we can ignore the events without causing harm in other areas (e.g. crashes). Due to the corner case situation such a change would be quite likely to bitrot and break. -- You are receiving this mail because: You are watching all bug changes.
