Summary: | [systemd startup] Can't unlock session with loginctl | ||
---|---|---|---|
Product: | [Plasma] ksmserver | Reporter: | Eve Kaczmarek <evekaczmarek> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bharadwaj.raju777, bhush94, i, nate, plasma-bugs |
Priority: | VHI | Keywords: | regression |
Version: | 5.21.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/plasma/kscreenlocker/commit/a59f0d75f36fcfccf6ef3a256afbab5143353f7b | Version Fixed In: | 5.22 |
Description
Eve Kaczmarek
2021-02-21 06:55:58 UTC
Are you using the optional systemd startup feature? (In reply to Nate Graham from comment #1) > Are you using the optional systemd startup feature? Yes. Thanks, I thought so. I can confirm this. Raising priority since this effectively locks you out of your session entirely when you hit Bug 433054. QStringLiteral("GetSessionByPID")); well there's our problem A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/35 Git commit a59f0d75f36fcfccf6ef3a256afbab5143353f7b by David Edmundson. Committed on 08/05/2021 at 22:59. Pushed by davidedmundson into branch 'master'. Port from GetSessionByPid GetSessionByPid is broken especially when the calling process is in a different cgroup to the session object. Rather than using the magic "/auto" object path, calling GetSession with the argument "auto" seems to work on even distros with old bases and is the smallest code change. M +2 -2 logind.cpp https://invent.kde.org/plasma/kscreenlocker/commit/a59f0d75f36fcfccf6ef3a256afbab5143353f7b |