Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#50626 - [plasma-workspace] User switching asks to run "loginctl unlock-sessions"

Attached to Project: Arch Linux
Opened by Dimos Dimoulis (dimosd) - Thursday, 01 September 2016, 13:48 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 09 February 2017, 07:13 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When I try to switch to another user in KDE and then back to the original, I get a message similar to this:
"""
The screen locker is broken and unlocking is not possible anymore.\n
In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),\n
log in and execute the command:\n
\n
loginctl unlock-sessions\n
\n
Afterwards switch back to the running session (Ctrl+Alt+F%1).
"""

After running "loginctl unlock-sessions" I can switch the user. However when I try to switch the user again I am asked to run the same command again.

Maybe related: https://bugs.kde.org/show_bug.cgi?id=360489
This task depends upon

Closed by  Antonio Rojas (arojas)
Thursday, 09 February 2017, 07:13 GMT
Reason for closing:  Works for me
Comment by Dimos Dimoulis (dimosd) - Friday, 02 September 2016, 03:13 GMT
Using the lock screen to create a new session and switch users works as expected.
The problem appears when switching users from the application menu.
I found a workaround, you may close if you wish.
Comment by Antonio Rojas (arojas) - Sunday, 04 September 2016, 15:25 GMT
does it work if you downgrade dbus to 1.10.8?
Comment by Dimos Dimoulis (dimosd) - Sunday, 04 September 2016, 21:10 GMT
I downgraded dbus and libdbus to 1.10.8 but I got the same message.
Comment by Antonio Rojas (arojas) - Monday, 05 September 2016, 08:05 GMT
Please attach the journal output during the failure.
Comment by Dimos Dimoulis (dimosd) - Monday, 05 September 2016, 16:55 GMT
I am attaching the output of journalctl -b with dbus 1.10
The series of events are 1) Login to first KDE session 2) Switch to user "test" from the application menu 3) Switch back to user "dimosd" the same way 4) Get an error message 5) Login to a text console and run "loginctl unlock-sessions" successfuly.
   journal.txt (186.9 KiB)
Comment by Antonio Rojas (arojas) - Monday, 05 September 2016, 17:59 GMT
Can't see anything strange at first sight... what output do you get if you run '/usr/lib/kscreenlocker_greet --testing' manually?
Comment by Dimos Dimoulis (dimosd) - Monday, 05 September 2016, 19:45 GMT
The locker starts in a window without problems. I attached the output of "journalctl -f"
Comment by Dimos Dimoulis (dimosd) - Tuesday, 06 September 2016, 05:04 GMT
I tried this on Kubuntu (Plasma 5.5). The interesting thing is that the bug also appears there with Nvidia 361 but does not appear with Nouveau drivers.
Comment by Antonio Rojas (arojas) - Friday, 03 February 2017, 15:27 GMT
status with 5.9?
Comment by Dimos Dimoulis (dimosd) - Thursday, 09 February 2017, 04:47 GMT
I am using amdgpu now so I can't directly compare. It doesn't affect amdgpu.

Loading...