[plasmashell] [Bug 443986] Use serial numbers to identify displays instead of interface names
https://bugs.kde.org/show_bug.cgi?id=443986 Daniel Noga changed: What|Removed |Added CC||noga.d...@gmail.com --- Comment #6 from Daniel Noga --- For some reason it works correctly in Wayland, no constant changing of monitor IDs when using Thunderbolt dock station. Is it there implemented the better way? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443986] Use serial numbers to identify displays instead of interface names
https://bugs.kde.org/show_bug.cgi?id=443986 --- Comment #5 from gudv...@gmail.com --- (In reply to David Edmundson from comment #3) > if you ever upgrade your single monitor you have > unrecoverable data loss. This is kinda what it is now. If you reboot PC and DRM driver decides to mangle interface names it'll lead to configuration loss unless you mitigate it in some way. So either way you need to work around that. But I really doubt that there are displays out there with changing serials. Unless there is some way to get reliable and consistent data from DRM. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443986] Use serial numbers to identify displays instead of interface names
https://bugs.kde.org/show_bug.cgi?id=443986 Vladimir Yerilov changed: What|Removed |Added CC||openmind...@gmail.com --- Comment #4 from Vladimir Yerilov --- >>It's not Why not? It just means that the algo used should take into account monitors' serials as well. And that the primary monitor/screen configuration should apply to any connected screen if it's the only one. Also, a concept of laptop screen should be introduced, which should be possible to be permanently set as a secondary one unless it's the only one in which case it becomes primary until another monitor is detected. I also have 2 monitors and it's a total mess every time I login - in X it's race conditions resulting in weird bugs like Night Color failures to apply its settings, plasmashell crashes due to it trying to start while the external monitor is being detected; and in Wayland - there's no way to set the external monitor as a primary display, it's always a "reversed X" layout. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443986] Use serial numbers to identify displays instead of interface names
https://bugs.kde.org/show_bug.cgi?id=443986 David Edmundson changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk --- Comment #3 from David Edmundson --- >This seems like a very good idea to me It's not. I have two monitors in this house with the same serial. But even ignoring that, if you ever upgrade your single monitor you have unrecoverable data loss. There is definitely work to do on screen management, see the open invent tickets, but this isn't it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443986] Use serial numbers to identify displays instead of interface names
https://bugs.kde.org/show_bug.cgi?id=443986 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com --- Comment #2 from Alexandre Pereira --- nice catch with that kernel bug report :) I filed that kernel bug report because of exactly what this bug report describes :) ( the amdgpu.dc=1 enabled daisy chaining and amdgpu.dc=0 disables it ) btw ... I noticed that between 5.23.0 and 5.23.1, my plasma configuration switched monitors. Nothing a lastScreen switch in .config/plasma-org.kde.plasma.desktop-appletsrc didnt fix though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443986] Use serial numbers to identify displays instead of interface names
https://bugs.kde.org/show_bug.cgi?id=443986 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org --- Comment #1 from Nate Graham --- This seems like a very good idea to me and would fix multiple issues faced by users, in particular https://bugzilla.kernel.org/show_bug.cgi?id=206387. -- You are receiving this mail because: You are watching all bug changes.
