Bug 376154 - Second screen identified incorrectly
Summary: Second screen identified incorrectly
Status: RESOLVED WORKSFORME
Alias: None
Product: KScreen
Classification: Plasma
Component: libkscreen (show other bugs)
Version: 5.9.0
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-07 20:27 UTC by David Heijkamp
Modified: 2022-11-30 05:16 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kscreen.log (2.45 MB, text/x-log)
2017-02-07 20:30 UTC, David Heijkamp
Details
Config files in .local/share/kscreen (405.98 KB, application/gzip)
2017-02-12 16:16 UTC, David Heijkamp
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Heijkamp 2017-02-07 20:27:02 UTC
When I connect my laptop with an external / second screen using HDMI after a fresh boot, the second screen gets recognized correctly: in the Displays System Settings Module the proper name shows up (i.e. DELL U2515H). When I unplug the screen, close the lid of my laptop, go to work and connect the laptop to another external screen this screen will be recognized incorrectly as the first screen I connected after a fresh boot into a X session. As a result the incorrect monitor setup is recognized and applied which forces me to either correct the display settings or to reboot (after which the second screen is recognized correctly).

Looking at the kscreen.log (attached) a likely related logline is: "Failed to find a matching mode - this means that our config is corruptedor a different device with the same serial number has been connected (very unlikely).Falling back to preferred modes."

In the past I've reset the kscreen settings by removing the .local/share/kscreen directory before logging in to my Plasma desktop session. After the upgrade from 5.8.x to 5.9.0 the problem seemed to be resolved, but after a day or so it unfortunately reappeared.

My Laptop is Dell Latitude 5250 with integrated Intel video card, using the i915 drive. I'm more than happy to help troubleshoot the issue, if I get some instructions.
Comment 1 David Heijkamp 2017-02-07 20:30:25 UTC
Created attachment 103892 [details]
kscreen.log
Comment 2 Sebastian Kügler 2017-02-09 17:40:17 UTC
Thanks for the bug report!

Could you attach the config files in ~/.local/share/kscreen/* ? This can give me an idea of what's configured to compare with what should be set.
Comment 3 David Heijkamp 2017-02-12 16:16:03 UTC
Created attachment 104006 [details]
Config files in .local/share/kscreen

As requested, all the config files in .local/share/kscreen.
Comment 4 Gero Müller 2017-02-12 21:29:32 UTC
Hi,

ich have the same Problem. KDE does not recognize that a different monitor was plugged in on the same port.
Comment 5 Justin Zobel 2022-10-31 04:31:46 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-11-15 05:15:12 UTC
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!
Comment 7 Bug Janitor Service 2022-11-30 05:16:42 UTC
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!