Bug 387296

Summary: Kscreen completely confused when using 3 screens
Product: [Plasma] KScreen Reporter: Swâmi Petaramesh <swami>
Component: commonAssignee: Sebastian Kügler <sebas>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 5.11.3   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Swâmi Petaramesh 2017-11-25 14:04:55 UTC 
Hi,

The following bug has at least been there for 3 years in all successive versions of KDE, and I have noticed it in on 2 different laptops :

- in 2015 and later, on an HP EliteBook 820 with Intel graphics, running (several successive versions of) Fedora (from 21 to 25), with 2 external HP screens (connected to its dock).

- Now (nov 2017), a Lenovo Thinkpad P51 with NVidia graphics running Manjaro, with 2 external Samsung screens (connected to its dock).

My setup was, and is, as follows :

- Laptop to the left on its dock, with 2 external screens to its right.

- When booting with NO ~/.local/share/kscreen/* config files, the system "automagically" put things in the CORRECT order.

But, if
- Suspending then resuming the system
OR
- Having the external screeens turned off via energy saving

Then at resume all the screens flicker for ~10 seconds, then the laptop screen appears to have been moved "logically" to the right of the 2 externals, and KDE dashboard (which used to be on the laptop screen) appears on the 1st external monitor.

Going to KDE control center to try to fix things only shows that kscreen is completely confused with which screen is which and there is NO WAY to get things back in order.

Every attempt at changing something causes all the screens to flicker for 10 seconds before turning back on with the laptop screen "logically" to the right and dashboard on an external screen.

The only way I found to fix things is then :
- Exit KDE
- Login to a text terminal
- rm -rf ~/.local/share/kscreen/*
- Reboot

This is a serious annoyance...

TIA for a fix.
Comment 1 Nate Graham 2022-11-08 20:13:15 UTC 
Thank you for the bug report. Unfortunately we were not able to get to it yet. Can we ask you to please see if you can reproduce the issue with Plasma 5.25 or 5.26?

If you can, please change the status to CONFIRMED when replying. Thanks a lot!
Comment 2 Bug Janitor Service 2022-11-23 05:15:20 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 3 Bug Janitor Service 2022-12-08 05:14:53 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!