[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 --- Comment #36 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 --- Comment #35 from fanzhuyi...@gmail.com --- (In reply to fanzhuyifan from comment #33) > fyi I tried on neon unstable and this issue is no longer happening for me. > Could other people also test on neon unstable, if possible? Thanks! Plasma beta1 is

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 --- Comment #34 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|---

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 --- Comment #32 from Zamundaaa --- One thing you could try is to test the Plasma 6 alpha in a live boot, which has the new output configuration system for the Wayland session, and see if it still happens there. It's better at persistently identifying

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 --- Comment #31 from shin...@o2.pl --- Yeah, I have still that "bug" too :D -- You are receiving this mail because: You are watching all bug changes.

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 --- Comment #30 from fanzhuyi...@gmail.com --- I can reproduce this behavior on wayland. For me this happens after suspend (I don't have hibernate configured on my laptop). I am using the "for any display arrangement setting". My KDE plasma version is

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com -- You are

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 --- Comment #29 from Zamundaaa --- Git commit ae84480fbfdc684b8ee4b0207d3ce679f6fb4cd7 by Xaver Hugl. Committed on 05/10/2023 at 20:29. Pushed by zamundaaa into branch 'master'. outputconfigurationstore: add new config system Instead of an external

[KScreen] [Bug 466342] While 2 screens are connected, after resuming from hibernation, the secondary screen is set as the primary screen

https://bugs.kde.org/show_bug.cgi?id=466342 Nate Graham changed: What|Removed |Added Product|kwin|KScreen Component|wayland-generic