Bug 350322

Summary: Restart after having connected a third monitor resulted in "lockout"
Product: [Plasma] plasmashell Reporter: Larpon <lp>
Component: generic-multiscreenAssignee: Aleix Pol <aleixpol>
Status: RESOLVED WORKSFORME    
Severity: grave CC: germano.massullo, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.3.0   
Target Milestone: 1.0   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: xsession-errors of plasma login-black-screen-crash

Description Larpon 2015-07-17 16:27:41 UTC
Created attachment 93627 [details]
xsession-errors of plasma login-black-screen-crash

Hi bug hunters

I have a Lenovo T450s wich I use with a docking station. When docked I have a bigger Samsung SyncMaster connected as my second monitor - this setup works pretty well.

The other day I tried connecting my Wacom Cintiq Companion Hybrid device to see how everything would react. Everything seemed fine until the next reboot/login where I had unplugged the Cintiq during reboot. Plasma seemed to start loading fine but halfway into the load progress my two screens in the "normal" setup both went black and plasma restarted to the login screen. After trying a lot of configuration juggling and rebooting I eventually gave up and cleared my ~/.config and ~/.local to fix the problem - not a desirable solution :)

I think it can be reproduced by connecting a third monitor (not necessarily a Cintiq device) while plasma is running then do a reboot without the monitor/device attached and login to plasma.

I kept the ~/.config, ~/.local and xsession-errors-crash.txt afterthe incident. The laptop is my bread-and-butter computer so haven't tried connecting any more than two monitors since then to avoid setting it all up again.

I've attached the xsession-errors.txt that was written after the plasma login-black-screen-crash
Comment 1 Germano Massullo (Thetra) 2019-10-04 20:30:54 UTC
Is this bug still happening on newer Plasma versions?
Comment 2 Bug Janitor Service 2019-10-19 04:33:09 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 2019-11-03 04:33:10 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!