Bug 453957 - KScreen EDID reading is extremely error-prone
Summary: KScreen EDID reading is extremely error-prone
Status: RESOLVED FIXED
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.25.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-17 20:49 UTC by jackyguo18
Modified: 2023-04-13 16:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.27


Attachments
kscreen-console bug when EDID is not read correctly (11.35 KB, text/plain)
2022-05-17 20:49 UTC, jackyguo18
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jackyguo18 2022-05-17 20:49:05 UTC
Created attachment 148935 [details]
kscreen-console bug when EDID is not read correctly

SUMMARY
When plugging in my monitor, KScreen sometimes reads EDID data before the display is fully connected. This leads to it sometimes reading the display as "unknown HDMI-A-1 unknown" or "BOE". The differing EDID data often results in loading the wrong config. 

This GNOME thing may be of use: https://bugzilla.gnome.org/show_bug.cgi?id=779837

STEPS TO REPRODUCE
1. Open System Settings > Hardware > Display Configuration
2. Repeatedly plug and unplug the external monitor.

OBSERVED RESULT
The external monitor is sometimes seen as "unknown HDMI-A-1 unknown" or "BOE".

EXPECTED RESULT
When the external monitor is plugged in, it should always display as "Samsung Electric Company LF24T35".

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArcoLinux
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 2.94.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
See the attachment for a kscreen-console dump when things go wrong.
Comment 1 Nate Graham 2022-05-18 15:39:16 UTC
Very interesting observations, thanks.
Comment 2 Matthew Trescott 2022-06-03 23:37:42 UTC
I have noticed the same bug, but I am not sure it is caused by reading the EDID before it is fully connected, exactly. It may be that KScreen tries to read it before the EDID info is _fully transferred_. My reasoning for this is that I see the same problem when plugging in a display that's connected via USB-C dock (where the port would have to be fully connected in order to do the handshaking necessary to switch to DP alt mode).

Possibly related reddit post: https://www.reddit.com/r/kde/comments/staakr/unknown_displays/
Comment 3 jackyguo18 2022-06-21 19:27:31 UTC
If anything, a small workaround *might* be possible, but I can't seem to find a way to force KScreen to reload its configuration.
Comment 4 jackyguo18 2022-06-26 18:19:00 UTC
Update with 5.25.1: the bug seems to persist somewhat.

If I launch Plasma without plugging in my monitor, the first time I plug it in, it will show as "unknown HDMI-A-1 unknown". However, when I plug it in the second time, it is recognized correctly. Still quite annoying.
Comment 5 Marco Martin 2022-10-14 09:16:59 UTC
does this happen on wayland? x11? or both?
Comment 6 Matthew Trescott 2022-10-14 22:00:38 UTC
Only happens on Wayland in my testing.
Comment 7 Matthew Trescott 2023-03-11 15:53:08 UTC
Kernel 6.2.1 and Plasma 5.27.2, can no longer reproduce this issue. I guess it must be fixed!
Comment 8 Nate Graham 2023-03-13 15:04:48 UTC
Good news! Makes sense given all the multi-monitor fixes that made it into that release. Jacky Guo, what about you? Are you able to reproduce the bug in Plasma 5.27.2 or later?
Comment 9 Bug Janitor Service 2023-03-28 03:45:38 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 10 Bug Janitor Service 2023-04-12 03:45:56 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!