Bug 375341 - Screen lock freezes after removing external screens
Summary: Screen lock freezes after removing external screens
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.9.0
Platform: openSUSE Linux
: NOR major
Target Milestone: 1.0
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-20 16:15 UTC by Gábor Katona
Modified: 2019-10-04 20:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gábor Katona 2017-01-20 16:15:39 UTC
I use my laptop either with two external screens connected to a docking station while the laptop screen is disabled (lid is closed) or only on laptop screen.

When I remove the computer from the docking (thus the external screens are disconnected) while the screen is locked and after this I open the lid, the screen is black, only the mouse pointer is visible (it can be moved) and the screen cannot be unlocked. The only way to unlock the screen is to go to a terminal screen and issue 

loginctl unlock-sessions

After this the screen is back and everything works normal. This seems to be a major issue, since the user is practically locked out of the computer, and for most users the only solution is hard reset.

This also happens when I suspend the laptop with the screens connected and resume it after removing it from the docking.

In some cases I even cannot switch to the terminal screen.

This bug appeared in 5.8.5. Maybe it is connected to bug 371734 and it's fix. I guessed it is a multiscreen issue rather than kscreenlocker.

My system is Opensuse Tumbleweed, Plasma 5.8.5, Frameworks 5.29.0, Qt 5.7.1, kernel 4.9.3 64bit
Comment 1 Gábor Katona 2017-02-06 16:48:11 UTC
The problem is still here with Plasma 5.9.0.
Comment 2 Germano Massullo 2018-12-04 16:23:37 UTC
Can you confirm if the bug still happens with new Plasma versions?
Comment 3 Germano Massullo 2019-10-04 20:18:25 UTC
Can you confirm if the bug still happens with new Plasma versions?
Comment 4 Gábor Katona 2019-10-04 20:21:48 UTC
Now using Plasma 5.16.5 and the bug is not present
Comment 5 Germano Massullo 2019-10-04 20:25:16 UTC
Ok then we can close it