Created attachment 117401 [details] Screenshot of the desired state of the screen configuration. HARDWARE/SOFTWARE SETUP ======================= My setup is a laptop (Thinkpad T450s with Intel graphics). I have an external monitor connected as follows: Mini displayport - Mini DP to HDMI adapter - HDMI to DVI cable. The monitor is some old Sony DVI-only monitor. OS: Kubuntu 18.10 KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 grep LoadModule /var/log/Xorg.0.log outputs the following which to my untrained eye means that my system may not be using the dreaded broken Intel Xorg drivers mentioned in Martin Flöser's blog post "Multi-screen woes in Plasma 5.7". [1] [ 10.804] (II) LoadModule: "glx" [ 10.813] (II) LoadModule: "modesetting" [ 10.814] (II) LoadModule: "fbdev" [ 10.815] (II) LoadModule: "vesa" [ 10.819] (II) LoadModule: "fbdevhw" [ 10.819] (II) LoadModule: "glamoregl" [ 11.135] (II) LoadModule: "fb" [ 11.326] (II) LoadModule: "libinput" ISSUE ===== The issue that I'm seeing is that when returning from suspend, my display configuration is forgotten and reset in different ways. In all my test cases, the display cable has been connected through the suspend process and I've simply closed and opened the lid. The issue seems localized to returning form suspend. I do not see the same issue when cold-booting, and I can reset to a valid state by unplugging and replugging the monitor cable. There are various invalid states the configuration can end up in, and it's never consistent which one it is, which to me speaks for a race condition of some kind. For reference, my desired screen layout is to have the laptop monitor being primary and the external monitor to the right of the laptop monitor. That is, as seen in the attached image "multimonitor desired.png" which is a screenshot of the display settings window, or as described by the following xrandr line: $ xrandr --listmonitors Monitors: 2 0: +*eDP-1 1920/309x1080/174+0+0 eDP-1 1: +HDMI-1 1280/338x1024/270+1920+0 HDMI-1 Here are some examples of invalid states I've seen: 1) The external monitor is placed on top of (overlaps) the laptop screen and thus shows a section of it. In this case, there's a second login screen corresponding to the external monitor, both of which are functioning simultaneously. This invalid state is represented by the screenshot "multimonitor invalid 1.png" or by the following xrandr line: $ xrandr --listmonitors Monitors: 2 0: +*eDP-1 1920/309x1080/174+0+0 eDP-1 1: +HDMI-1 1280/338x1024/270+0+0 HDMI-1 2) In this state, the screen configuration is set to the desired configuration (I can move the cursor between the monitors and xrandr shows the correct configuration) however the login screen shows two overlapping login screens, much like it would in state 1. Only this time the login screen on the secondary monitor is essentially non-functional. This suggests to me that the configuration was at some point during wakeup in invalid state 1, and was later set to the desired state. I can provide a photo of this if needed for clarification. 3) Like 2, but the primary screen is not drawing the login screen, so the screen is black apart from the cursor, if moved to that screen. It does however contain a functional login screen which can be used by clicking on the black screen and typing the password blindly. 4) This is an oddball. In this state, the laptop screen becomes disabled, and also moved to the top right corner of the screen configuration area, and the primary display value is unset. Refer to screenshot "multimonitor invalid 2.png". In this case, seeing that the laptop screen is disabled, the xrandr line becomes $ xrandr --listmonitors Monitors: 1 0: +HDMI-1 1280/338x1024/270+0+0 HDMI-1 I've produced this particular state exactly once, and I'm mentioning it only to point out the random nature of the issue. I have tried adding an xorg config file /usr/share/X11/xorg.conf.d/99-monitors.conf containing Section "Monitor" Identifier "eDP-1" Option "Primary" "true" EndSection Section "Monitor" Identifier "HDMI-1" Option "RightOf" "eDP-1" EndSection Section "Monitor" Identifier "DP-1" Option "RightOf" "eDP-1" EndSection The last line was an attempt at trying the hypothesis that maybe the HDMI adapter is detected as a DP output early in the detection, throwing something off. This configuration file however has not had the desired effect. If there are any other logs I should post, or anything I should try to fix the issue (that doesn't have a significant chance of locking me out of the machine -- this is a productivity machine after all) I'd be happy to try it. References: [1] https://blog.martin-graesslin.com/blog/2016/07/multi-screen-woes-in-plasma-5-7/
Created attachment 117402 [details] Screenshot of invalid state 1 of the screen configuration.
Created attachment 117403 [details] Screenshot of invalid state 2 of the screen configuration.
I do have a similar issue, on wayland.
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please check if this is still an issue with Plasma 5.25 or 5.26? If it is, please change the status to CONFIRMED when replying. If not, or if you can't because you no longer use this setup, you can change the status to RESOLVED WORKSFORME. Thanks a lot!
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!