Hi, After booting my laptop it's screen is overlapping with external screen. I.e. it's bottom *left* corner is snapped to the bottom *left* corner of the external screen. Reproducible: Always Steps to Reproduce: 1. Plug in external display 2. Reboot Actual Results: Laptop's native display overlaps with the external display. I.e. is snapped by bottom left corner to the bottom left corner of the external display (see attached screen shot for details). Expected Results: Laptop's screen shold be snapped as configured before (e.g. laptop's right edge to external's left edge). I am running Kubuntu Willy (15.10) on top of Dell XPS 15z laptop (screen resolution 1366x768). The notebook has an NVIDIA GeForce 525M graphics adapter, which is driven by the NVIDIA proprietary driver version 352.41. Also I am using the NVIDIA adapter as primary (primus-select nvidia). Also I have a Dell 24" external screen connected to the HDMI port (which is directly connected to the NVIDIA card). In fact, this is the reason I am using NVIDIA as my primary graphics adapter: the HDMI port is not working when Intel graphics is selected (via prime-select intel). Also, I am using Plasma (kscreen) 5.4.1 on top of KDE Frameworks 5.14.0 (the most recent version for Kubunty Willy).
Created attachment 94803 [details] KScreen after reboot
This issue looks really similar to mine (resolved, invalid): bugs.kde.org/show_bug.cgi?id=338091 Also, I am experiencing the issue described here: https://bugs.kde.org/show_bug.cgi?id=345728
Note to the screenshot: It was shoot when I started krunner (alt+f2 hotkey) with laptop's screen having "focus". As a result, you can see krunner's pannel in the center of external display's screen.
Created attachment 95028 [details] Screens after rm -rf ~/.local/share/kscreen/* Discovered interesting fact: if, before X starts (i.e. on logon screen) switch to tty and remove contents of ~/.local/share/kscreen. Then, when starting, displays do not overlap (eventually, they are located like on attached screenshot). Hoowever, after re-login problem appears again.
Created attachment 95029 [details] File, that is created in ~/.local/share/kscreen after logging in Attaching a settings file, created in ~/.local/share/kscreen
Probably, the bug is in SDDM's side. Because it has a similar problem initially: when SDDM shows up, the laptop's screen is attached by the upper left corner to the upper left corner of external screen. Here is the video of SDDM/plasma bootup process: https://youtu.be/tvLjQBa3Hd4 Also, I've noticed that plasma crashes when I connect/disconnect my external screen. This might be related or another bug as vell. (I'll attach debug information later)
Created attachment 96694 [details] KWin stacktrace when disconnecting external screen (SIGABRT) KWIn, Plasma and KRunner crash when I disconnnect the external screen. Attaching their backtraces. Also, when I connect the external screen, (laptop's) display switches to tty1 (while X is on tty7) and after switching back to tty7 I see login screen again (plasma session closed, probably SDDM crashed)
Created attachment 96695 [details] Plasmashell stacktrace when disconnecting external screen
Created attachment 96696 [details] Krunner stacktrace when disconnecting external screen
Still actual with Plasma 5.5.3
I was experimenting with kscreen configuration(s) in ~/.local/share/kscreen lately. And finally (when II have almost given up trying) I've decided to prevent anybody from modifying configs there: # in case smth. gets too smart and uses chmod before changing the file sudo chown root:root ~/.local/share/kscreen/* # allow everybody (including myself) to read the file sudo chmod 0644 ~/.local/share/kscreen/* This leads to a conclusion that *something intentionally changes kscreen config on logon*. It may be kubuntu-specific stuff. Can you please check? BTW, with recent sddm updates in kubuntu my external smth. started disabling my external screen on logon so I've actually decided to make an investigation on the topic.
*** Bug 394625 has been marked as a duplicate of this bug. ***
(In reply to Kyrylo Bohdanenko from comment #11) > This leads to a conclusion that *something intentionally changes kscreen > config on logon*. It may be kubuntu-specific stuff. Can you please check? > > BTW, with recent sddm updates in kubuntu my external smth. started disabling > my external screen on logon so I've actually decided to make an > investigation on the topic. This bug occured on my arch linux installation as well, so it is not exclusive to kubuntu.
This happens on my Manjaro desktop system as well. At first I thought it is some kind of driver issue, but it doesn't seem to be the case. For me, the screen config is working upon first boot. However, when the screensaver is shown (the system is left alone and locks after timeout), there is a high chance that the two screens overlap completely.
Thank you for the bug report, Kyrylo. 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, and paste the output of `kscreen-doctor -o` when it's working properly, and then right after you make the bug happen. 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!