You are not logged in.
On my laptop, closing the lid will suspend the system after a certain period of time. When this happens while multiple users are logged in, waking the computer and logging in is met with the message modal "Authentication Required". Text of modal (screenshot linked at the end):
Authentication is required to suspend the system while other users are logged in.
<password prompt>
Action: Suspend the system while other users are logged in
ID: org.freedesktop.login1.suspend-multiple-sessions
Vendor: The systemd Project
The problem is that I have no custom rules in /etc/polkit-1/rules.d nor in /usr/share/polkit-1/rules.d. How else could this action be triggering?
https://pasteboard.co/2n3sDI9kBng1.png
Last edited by Zosoled (2024-07-30 22:59:00)
Offline
Looks like KDE?
https://bbs.archlinux.org/viewtopic.php?id=297757 (unresolved/disappeared)
=> powerdevil, are you running two KDE sessions?
Does the system suspend at all (and the dialog is just spurious)?
Online
I am in fact using Wayland and have the same DisplayServer value as that other user. I will remove that and try to replicate.
Offline
Remove the DisplayServer value did not resolve the issue, but I see that there is more info on the thread you linked, so I will read up on that.
In the meantime, I wanted to post my journalctl output: https://0x0.st/XO3p.txt
Offline
I could only replicate by closing the lid; using KDE "Sleep" did not exhibit the issue. I am using sddm.service to launch SDDM and log in upon boot.
The following process replicated the issue reliably:
Log in as User A.
Switch to User B.
Close the lid.
Open the lid and switch back to User A.
Observe authentication modal for suspend-multiple-sessions.
User B was never presented with the dialog. Basically, the dialog is shown to the user who did not trigger sleep by closing the lid.
Offline
More info:
Entering a password and hitting OK just cancels the dialog: the system does not sleep after authorizing.
I tried waiting about 2 minutes to account for the HoldoffTimeoutSec value but it did not make a difference.
Offline
I tried adding a logind rule as described here: https://bbs.archlinux.org/viewtopic.php … 2#p1649022
This time entering a password at the authentication dialog did put the system to sleep, but it also might be because I entered the password quicker than previous times.
http://0x0.st/XOg5.txt
Offline