[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 [email protected] changed: What|Removed |Added CC||[email protected] --- Comment #19 from [email protected] --- Hi, I would like to confirm the problem also in the recent plasma main versions. A solution to me would be that KDE respects the primary screen configuration from a certain / the only present account (my case). System info: Operating System: KDE neon User Edition KDE Plasma Version: 6.5.2 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.3 Kernel Version: 6.14.0-35-generic (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 Nate Graham changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 --- Comment #18 from [email protected] --- Then if I open and close the LID, things get back to normal again. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 --- Comment #17 from [email protected] --- This again happened to me today. I connected the laptop to the docking station with LID closed, and the laptop screen gets activated. This is the output from kscreend-doctor: $ kscreen-doctor -o QSocketNotifier: Can only be used with threads started with QThread Output: 1 eDP-1 enabled connected priority 2 Panel Modes: 0:3840x2160@60*! 1:3840x2160@48 Geometry: 0,0 1920x1080 Scale: 2 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 2 DP-5 enabled connected priority 1 DisplayPort Modes: 0:3840x2160@30*! 1:2560x1440@60 2:2048x1280@60 3:2048x1152@60 4:1920x1200@60 5:2048x1080@24 6:1920x1080@60 7:1920x1080@60 8:1920x1080@60 9:1920x1080@50 10:1920x1080@24 11:1920x1080@24 12:1600x1200@60 13:1680x1050@60 14:1280x1024@75 15:1280x1024@60 16:1280x800@60 17:1152x864@75 18:1280x720@60 19:1280x720@60 20:1280x720@50 21:1024x768@75 22:1024x768@60 23:800x600@75 24:800x600@60 25:720x576@50 26:720x576@50 27:720x480@60 28:720x480@60 29:720x480@60 30:720x480@60 31:640x480@75 32:640x480@60 33:640x480@60 34:640x480@60 35:720x400@70 Geometry: 1920,0 1920x1080 Scale: 2 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 --- Comment #16 from [email protected] --- OK, I will try to do it next time this happens. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 --- Comment #15 from Nate Graham --- That's really weird! Can paste the output of running `kscreen-doctor -o` in a terminal window after it happens? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 --- Comment #14 from [email protected] --- Yes, indeed, this is what seems to happen. For example, I saw that when minimizing an app by clicking on its icon on the task bar, the window seems to come from the left of the screen, while there should be just one screen activated. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #13 from Nate Graham --- So you're saying that when you plug in the docking station while the lid is closed, the laptop wakes up and starts displaying output on the laptop screen despite the lid being closed? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 [email protected] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 --- Comment #12 from [email protected] --- Hmm, I think I spoke too quickly. It still sometimes happen to me that the screen laptop is still activated when I connect the laptop to the docking station, despite the LID being closed. There should be better checking that the LID is closed when waking up from suspend. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 Nate Graham changed: What|Removed |Added Version Fixed In||5.27 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Nate Graham --- Excellent! It makes sense because 5.27 has a ton of fixes for multiscreen issues. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 --- Comment #10 from [email protected] --- I do not experience this bug anymore. I am on 5.27beta. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 Nate Graham changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=458633| -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456003] When connecting laptop to a docking station with LID closed, internal screen inappropriately remains the primary one
https://bugs.kde.org/show_bug.cgi?id=456003 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED Summary|When connecting to a|When connecting laptop to a |docking station with LID|docking station with LID |closed, lock-screen greeter |closed, internal screen |goes to laptop |inappropriately remains the ||primary one --- Comment #9 from Nate Graham --- This should hopefully be fixed with the big screen arrangement refactor for Plasma 5.27. -- You are receiving this mail because: You are watching all bug changes.
