Bug 466641

Summary:	Third monitor does not applies its state on reboot
Product:	[Plasma] KScreen	Reporter:	Dmitriy <dimddr87>
Component:	common	Assignee:	kscreen-bugs-null <kscreen-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	5.27.0
Target Milestone:	---
Platform:	Neon
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=466149
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	kscreen output directly after reboot kscreen output after reconfiguration

Description Dmitriy 2023-03-01 08:14:14 UTC

SUMMARY
One of the external displays does not enabled on reboot, but from the settings it looks like all the settings are the same. But when you turn it off and on, it appears disabled in the configuration page


STEPS TO REPRODUCE
1. Configure 2 additional displays in the Settings, make one of them the primary display
2. Reboot

OBSERVED RESULT
One of the 2 external displays are not started (stays on powersave state). Configuration does not changed in the Display Settings.
But when you turn off this monitor, KDE reacts on this and rebuild displays configuration. Then you can turn it on again, it appears in the settings but in the disabled state. After redoing configuration and reprioritize displays all works as expected

EXPECTED RESULT
All two external displays works the same as before reboot

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.27 
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Laptop: Lenovo P52
Lenovo Thunderbold dock
2 Lenovo ThinkVision monitors

Comment 1 Nate Graham 2023-03-01 20:44:02 UTC

Can you enable all screens, run `kscreen-console bug`, and then paste the contents of the "EDID" section for each screen?

Comment 2 Dmitriy 2023-03-02 14:39:42 UTC

Created attachment 156923 [details]
kscreen output directly after reboot

Comment 3 Dmitriy 2023-03-02 14:40:20 UTC

Created attachment 156924 [details]
kscreen output after reconfiguration

Comment 4 Nate Graham 2023-03-02 15:53:10 UTC

Okay, their EDIDs and hashes look sane, thanks. Their _KDE_SCREEN_INDEX values look correct too, but the screen identified as primary changes out of sync with the screen that has _KDE_SCREEN_INDEX=1 set.

Seems quite related to Bug 466149. I wonder if fixing that will fix this automatically.

Are you on Wayland or X11? Does it happen on both, or only one?

Comment 5 Dmitriy 2023-03-02 16:38:30 UTC

Forgot to mention, it is X11 Session, tomorrow I will check it on Wayland

Comment 6 Bug Janitor Service 2023-03-17 03:45:45 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 2023-04-01 03:45:36 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!