Its ssh, putty,

dady@linuxbox:~$ systemctl poweroff
==== AUTHENTICATING FOR org.freedesktop.login1.set-wall-message ===
Authentication is required to set a wall message
Multiple identities can be used for authentication:
 1.  ,,, (dady)
 2.  ,,, (danca)
Choose identity to authenticate as (1-2): 1
Password:
==== AUTHENTICATION COMPLETE ===
==== AUTHENTICATING FOR org.freedesktop.login1.power-off ===
Authentication is required for powering off the system.
Multiple identities can be used for authentication:
 1.  ,,, (dady)
 2.  ,,, (danca)
Choose identity to authenticate as (1-2): Failed to power off system via logind: Spojení bylo přílií
Failed to start poweroff.target: Spojení bylo příliš dlouho neaktivní
See system logs and 'systemctl status poweroff.target' for details.
dady@linuxbox:~$
dady@linuxbox:~$ loginctl show-session $XDG_SESSION_ID
Id=5
User=1000
Name=dady
Timestamp=Po 2016-07-11 14:30:44 CEST
TimestampMonotonic=1861158573
VTNr=0
Remote=yes
RemoteHost=192.168.1.101
Service=sshd
Scope=session-5.scope
Leader=3608
Audit=5
Type=tty
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
LockedHint=no
dady@linuxbox:~$ loginctl list-sessions
   SESSION        UID USER             SEAT
         5       1000 dady
        c1        116 Debian-gdm       seat0
         2       1000 dady             seat0

3 sessions listed.


Thank you
Pavel





Michael Biebl napsal(a) dne 11.7.2016 v 14:26:
How exactly did you trigger the bug?

Typically, a systemctl shutdown should be possible (without a password
prompt) when you are logged in locally and your session is marked as active.

What's the output of

$ loginctl show-session $XDG_SESSION_ID

$ loginctl list-sessions


Reply via email to