Bug 370206

Summary: KScreenlocker not unlockable after switching to new session when not using systemd
Product: [Plasma] kscreenlocker Reporter: vlaomao
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: bhush94, christiandehne, kde, kde, mgraesslin, nate, postix, tuxgirl
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Black window

Description vlaomao 2016-10-06 18:17:38 UTC 
I'm not use systemd, just updgraded to plasma and screenlocker 5.8, and bug still exist

Reproducible: Always

Steps to Reproduce:
1. Login to account (session 1)
2. Press Menu, then select 'Switch User'
3. Create new session and login the same user (session 2)
4. Close this session (session2)
5. Try to lock session (session 1)

Actual Results:  
Appears a black window says 'The screen locker is broken and unlocking is not possible anymore. In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2), log in and execute the command: loginctl unlock-sessions. Afterwards switch back to the running sesion (Ctrl +Alt+F7)'

Expected Results:  
KDE must show normal unlock dialog

Ask for additional information
Comment 1 vlaomao 2016-10-06 18:20:51 UTC 
Created attachment 101453 [details]
Black window
Comment 2 Martin Flöser 2016-10-07 05:31:11 UTC 
@Kai: any idea why switching the session breaks the lock screen?
Comment 3 Tux 2020-05-10 02:56:00 UTC 
I have the same problem on multiple computers running kubuntu.
Comment 4 Nate Graham 2021-06-21 22:34:35 UTC 
What are you using instead of systemd? consolekit? Something else?
Comment 5 Bug Janitor Service 2021-07-06 04:33:47 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 6 vlaomao 2021-07-07 19:18:45 UTC 
I'm using elogind 246.10-r1
Comment 7 David Edmundson 2021-07-19 22:32:47 UTC 
And you have this issue 5 years later? 

What Plasma version?
Comment 8 Bug Janitor Service 2021-08-03 04:33:37 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 9 Bug Janitor Service 2021-08-18 04:36:34 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!