SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Use a laptop with LID closed, suspend state (Dell XPS13 9370 in my case) 2. Connect it to a usb-c docking station (Dell DS-1000 in my case) connected to an external screen => the greeter for unlocking goes to the external screen, which is good. 3. Enter your password for unlocking => The external screen is empty (just wallpaper) since the screen is set to secondary. The primary screen is the internal screen, which is bad since the LID is closed. You have to open the LID and then close it so that the external screen becomes the primary. OBSERVED RESULT The primary screen is the internal one, although the LID is closed EXPECTED RESULT The primary screen should be the external one, and the internal one should be deactivated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 12 KDE Plasma Version: 5.24.5/X11 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4
Can you see if it's fixed in Plasma 5.25? We did a lot of multimonitor robustness work there. Thanks!
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 bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
This bug still exists for me in 5.25.3.
Still repro in 5.25.4.
So, actually, to be precise, it seems the problem is slightly different now in 5.25. When connecting the laptop to the docking station with LID closed and in suspend state, the laptop wakes up but the greeter goes to the laptop screen. So you have to open the LID, unlock, and then close the LID. There is another issue when unplugging the docking station with LID closed, that I will report separately. Basically, it means that when plugging/unplugging a docking station, you have to open the LID, which is not optimal. I hope these issues can be fixed.
Just to add that this problem does not always happen, it is not 100% reproducible. I would say something like 50% on average. It is not clear to me in which circumstances it happens.
Now I tried on the KDE Wayland session. Connecting to a docking station with LID closed, the greeter does go to the external screen, so that is OK. But once you unlocked the screen, the laptop screen is activated. So you have to open and close the LID, so that KDE understand that the LID is really closed.
This should hopefully be fixed with the big screen arrangement refactor for Plasma 5.27.
I do not experience this bug anymore. I am on 5.27beta.
Excellent! It makes sense because 5.27 has a ton of fixes for multiscreen issues.
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.
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?
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.
That's really weird! Can paste the output of running `kscreen-doctor -o` in a terminal window after it happens?
OK, I will try to do it next time this happens.
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
Then if I open and close the LID, things get back to normal again.