FS#28386 - [systemd] non root user fails to shutdown or reboot using systemd in KDE
Attached to Project:
Arch Linux
Opened by Ike Devolder (BlackEagle) - Sunday, 12 February 2012, 19:18 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 04 April 2012, 11:12 GMT
Opened by Ike Devolder (BlackEagle) - Sunday, 12 February 2012, 19:18 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 04 April 2012, 11:12 GMT
|
Details
Description:
with the latest systemd installed: systemd 42 i can no longer reboot or shutdown from a loggedin kde session, when i do so im dropped back to kdm downgrading systemd to 37-3 all is working fine again, i dont see special failures in the logfiles or with systemd 42 installed i dont see anything special with systemd-journalctl -a Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Wednesday, 04 April 2012, 11:12 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 44-3
Wednesday, 04 April 2012, 11:12 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 44-3
This commit seems relevant: http://cgit.freedesktop.org/systemd/systemd/commit/?id=89f134406af6
Feel like reverting it and testing?
Also, need the output from 'systemd-loginctl'
then i'm unfortunately 2 or more days without internet
i can try again with kde and patched systemd this evening, maybe kde is doing something weird
systemd-loginctl:
SESSION UID USER SEAT
0 sessions listed.
lxdm + xfce systemd reboot; shutdown ok
systemd-loginctl:
SESSION UID USER SEAT
0 sessions listed.
kdm + kde systemd reboot; shutdown fail
systemd-loginctl:
SESSION UID USER SEAT
c1 1000 ike seat0
1 sessions listed.
kdm + xfce systemd reboot; shutdown ok
systemd-loginctl:
SESSION UID USER SEAT
c2 1000 ike seat0
1 sessions listed.
ok i found enough space on my virtual machine to install kde and narrowed a little bit down
kdm + kde is a fail
systemd-loginctl:
SESSION UID USER SEAT
1 0 root seat0
c5 1000 eric seat0
polkitd(authority=local): Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name :1.99 [/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)
and when the session is closed:
polkitd(authority=local): Unregistered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session6 (system bus name :1.99, object path /org/kde/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)
Shutdown and restart also work well when kdm is started manually, not through systemd.
Disabling pam_systemd makes restart/shutdown work.
remove pam_systemd from
/etc/pam.d/kde
/etc/pam.d/kde-np
did work fine
so is this then a packaging bug in kdebase-workspace ?
is sshd also affected ? i saw that /etc/pam.d/sshd also had a reference to pam_systemd
http://www.freedesktop.org/wiki/Software/systemd/writing-display-managers
http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/4392/focus=4414
Not really a bug, persay, just lacking support.
dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static)
Active: active (running) since Mon, 20 Feb 2012 10:10:38 +0100; 6h ago
Process: 1528 ExecStartPre=/bin/rm -f /var/run/dbus.pid (code=exited, status=0/SUCCESS)
Process: 1524 ExecStartPre=/usr/bin/dbus-uuidgen --ensure (code=exited, status=0/SUCCESS)
Main PID: 1534 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
â 1534 /usr/bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation
â 1667 /usr/lib/polkit-1/polkitd --no-debug
â 1683 /usr/sbin/modem-manager
â 1778 /usr/lib/upower/upowerd
â 1806 /usr/lib/udisks/udisks-daemon
â 1807 udisks-daemon: not polling any devices
â 4092 /usr/sbin/wpa_supplicant -u
dbus.service - D-Bus System Message Bus
Loaded: loaded (/lib/systemd/system/dbus.service; static)
Active: active (running) since Mon, 20 Feb 2012 19:29:03 +0100; 1min 22s ago
Process: 322 ExecStartPre=/bin/rm -f /var/run/dbus.pid (code=exited, status=0/SUCCESS)
Process: 317 ExecStartPre=/usr/bin/dbus-uuidgen --ensure (code=exited, status=0/SUCCESS)
Main PID: 324 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
├ 324 /usr/bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation
├ 331 /usr/lib/polkit-1/polkitd --no-debug
├ 338 /usr/sbin/wpa_supplicant -u
├ 479 /usr/bin/ntpd -g -p /run/ntpd.pid
├ 612 /usr/lib/upower/upowerd
├ 634 /usr/lib/udisks/udisks-daemon
└ 640 udisks-daemon: not polling any devices
Feb 20 19:29:40 BlackEagle dbus-daemon[324]: **** CHANGING /sys/devices/pci0000:00/0000:00:11.0/host0/target0:0:0/0:0:0:0/block/sda/sda4
Feb 20 19:29:40 BlackEagle dbus-daemon[324]: **** UPDATING /sys/devices/pci0000:00/0000:00:11.0/host0/target0:0:0/0:0:0:0/block/sda/sda4
Feb 20 19:29:40 BlackEagle dbus-daemon[324]: **** CHANGED /sys/devices/pci0000:00/0000:00:11.0/host0/target0:0:0/0:0:0:0/block/sda/sda4
Feb 20 19:29:40 BlackEagle dbus-daemon[324]: helper(pid 643): completed with exit code 0
Feb 20 19:29:40 BlackEagle dbus-daemon[324]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:11.0/host0/target0:0:0/0:0:0:0/block/sda
Feb 20 19:29:46 BlackEagle dbus-daemon[324]: dbus[324]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freede....service'
Feb 20 19:29:46 BlackEagle dbus[324]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 20 19:29:46 BlackEagle dbus-daemon[324]: dbus[324]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit ... details.
Feb 20 19:29:46 BlackEagle dbus[324]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesk...r details.
Feb 20 19:29:55 BlackEagle polkitd(authority=local)[331]: Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session1 (sys...E.UTF-8)
From a broken _and_ working session, the exit codes/output of:
pkcheck --action-id org.freedesktop.login1.reboot -u --process $$
pkcheck --action-id org.freedesktop.consolekit.system.restart -u --process $$
Make sure this is done from a fresh terminal and not something like a leftover tmux/session session of a previous login.
system is freshly started
should the output be different ?
any suggestions what to look for, the only things i find in the dbus-monitor log is logout in both cases
when i find the time i'll look into this lateron, i have no more time now
http://cgit.freedesktop.org/systemd/systemd/commit/?id=75c8e3cffd7da8eede614cf61384957af2c82a29