I have a Dell Precision 3510 laptop which has 1920x1080 screen. I use this laptop with 2 monitors on different places: 1) Dell U2415 with 1920x1200, 2) Eizo EV2450 with 1920x1080. I will describe now my problem (both monitors have been already correctly set long time ago): * I started my laptop and then connected Dell monitor and the resolution on this monitor was correctly set to 1920x1200. * I disconnected Dell monitor and put a laptop into Sleep mode. * Then I resumed the laptop and worked on it without any monitor and after 2 hours I put it into Sleep mode again. * At home I resumed the laptop, plugged Eizo monitor but it has not been correctly detected as Eizo but as Dell as shown on the screenshot "monitor-0". * After restart of the system and plugging of Eizo again this monitor has been correctly detected as Eizo as shown on "monitor-1". These steps do not show the real problem but if we would swap usage of those monitors in the description we would end up with Dell 1920x1200 detected as Eizo but with the resolution set to 1920x1080 and in this case we would have to set it manually to 1920x1200 but this would lead to changing the KScreen's configuration for Eizo and not for Dell.
Created attachment 106222 [details] monitor-0
Created attachment 106223 [details] monitor-1
1 thing I have noticed - after restart of the system there was no primary output set - see screenshots "monitor-1" and "monitor-0".
Could it be related to #340548?
Is there anybody who can check this issue?
Hi Petr, Sorry that I didn't get back to you yet. Could you attach more information to this bugreport so I can have a closer look? https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information Additionally to that, could you run xrandr -q for each step and attach the output? With that output, you can already check yourself if X is reporting the correct information about your screens, but I'm happy to check as well.
OK, I have enabled logging so when I have something to share I will attach it here.
Created attachment 106747 [details] kscreen-0-console
Created attachment 106748 [details] kscreen-0-0
Created attachment 106749 [details] kscreen-0-1
Created attachment 106750 [details] kscreen-0-2
See my log and configuration files for this issue: * kscreen-0-0 after resume with no monitor connected, * kscreen-0-1 after resume and connected Dell U2415 (assumes it as Eizo EV2459 with 1920x1080, see also the screenshot), * kscreen-0-2 after restart and connected Dell U2415. I also attached outputs from a command "kscreen-console bug" (file kscreen-0-console).
Created attachment 106751 [details] screenshot-0
Created attachment 106773 [details] kscreen-1 And here are the logs and configurations when playing with EIZO monitor. It seems that KScreen has a problem to identify a monitor after disconnecting a different monitor.
What does xrandr -q report, though?
Ahh, I forgot to execute this command. I'll do it next week when I am in the office with Dell, currently I am at home with Eizo.
Created attachment 106829 [details] kscreen-2 I performed today a way of connecting Dell in the office and then Eizo at home and the results with "xrandr -q --verbose" are attached "kscreen-2".
Created attachment 106851 [details] kscreen-3 And in "kscreen-3" archive there are logs after resuming of my laptop (Eizo 1080p was connected before suspend), connecting Dell 1200p where 1080p was activated and then restarting of the system.
For me this bug is the same as bug 360058. Bug 360058 is specific on when the system is suspended, but from the time of the report I think the bug worsened, because now it happen also as described by Petr Nehez. Bug 360058 has already quite a lot of debugging information. I experience the same behaviour, and the only solution is restarting. Disconnecting and reconnecting video cables works sometimes but not all the time. @Sebastian Kügler A suggestion: Isn't there a way to show the user that is reporting a bug for KScreen the link to the page where it is explained how to gather better debugging information that you posted here? Would be very useful I think. I haven't attached this information in my other bug report because I thought that all the debug information was stored in .local/share/kscreen /kscreen.log, even though often were not enough.
@Petr Nehez Are you using a docking station?
@Simone Gaiarin Nope, I do not use docking station, just laptop's HDMI. And always 1 screen at the time - when a monitor is connected laptop's screen is off.
Is here anything else I can do to help you out? This issue is making me crazy...
I have an update on this - since the time I switched to Manjaro KDE this is not the issue anymore. So I would say there must be an issue in KScreen on Kubuntu while it had a problem to identify the monitor after resume.
I'll close this bugreport since it's apparently fixed by an upgrade, not worth spending valuable development time on it as underlying issues area already reported most likely. Thanks!