Bug 460529

Summary:	Second monitor always disabled when logging in
Product:	[Plasma] kwin	Reporter:	Loïc Droz <lk.droz>
Component:	platform-drm	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	5.26.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Loïc Droz 2022-10-16 11:35:09 UTC

SUMMARY
After every login, my second monitor is always disabled.
Enabling it in the display settings fixes the issue for the current session.
However, after restarting my computer and logging in again, the second monitor is again disabled.
If merely logging out and back in without restarting, the second monitor stays enabled.

STEPS TO REPRODUCE
1. Start the PC
2. Log in
3. Enable both monitors
4. Restart the PC
5. Log in
6. Observe how the second monitor is disabled

OBSERVED RESULT
The second monitor is always disabled after restarting the PC, regardless of the display settings.

EXPECTED RESULT
The second monitor should be enabled whenever it has been enabled in the display settings.

SOFTWARE/OS VERSIONS 
Linux/KDE Plasma: EndeavourOS (Arch Linux) Kernel 6.0.1-arch2-1 / KDE Plasma 5.26.0 Wayland
KDE Plasma Version: 5.26.0 Wayland
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION
The bug only shows up in KDE Plasma. In the SDDM greeter, the second monitor is always enabled.

Comment 1 Vlad Zahorodnii 2022-10-17 10:06:44 UTC

If you remove the contents of .local/share/kscreen and reboot the computer, is the second screen still disabled on startup? (make sure to make a backup of .local/share/kscreen before testing this)

Comment 2 Loïc Droz 2022-10-17 19:14:21 UTC

(In reply to Vlad Zahorodnii from comment #1)
> If you remove the contents of .local/share/kscreen and reboot the computer,
> is the second screen still disabled on startup? (make sure to make a backup
> of .local/share/kscreen before testing this)

Unfortunately I cannot answer as I am no longer able to reproduce the bug.

I will try this and update if the bug re-appears.

Thank you for your reply.

Comment 3 Nate Graham 2022-10-17 20:20:40 UTC


*** This bug has been marked as a duplicate of bug 460341 ***