Am 07.12.2013 21:17, schrieb Jonathan McDowell: > Package: systemd > Version: 204-5 > Severity: normal > > This could be a gnome-power-manager (3.8.2-1) or upower (0.9.23-2+b1) > issue, but it seems to have started at the point a GNOME upgrade pulled > in systemd for logind. > > Since this time my laptop's sleep button no longer works correctly. > Pressing it results in the screen being locked and the LCD being turned > off, but doesn't actually suspend the laptop. I get the following errorse > in /var/log/daemon.log: > > Dec 7 12:12:59 makguksu dbus[3877]: [system] Activating service > name='org.freedesktop.systemd1' (using servicehelper) > Dec 7 12:12:59 makguksu dbus[3877]: [system] Activated service > 'org.freedesktop.systemd1' failed: Launch helper exited with unknown return > code 1 > > Choosing the "Suspend" menu option from the GNOME panel or invoking > pm-suspend from the command line both continue to work fine. I've tried > setting HandleSuspendKey to both ignore and suspend in > /etc/systemd/logind.conf (rather than the default commented out option) > and neither seems to change the behaviour. > > I am not running systemd as my init; still using sysvinit (2.88dsf-43).
suspend/hibernate requires systemd = PID 1 logind just forwards the request to systemd. IIRC the gnome-shell menu still calls upower. The component which handles lid close events in GNOME is gnome-settings-daemon and that package has been switched to work with systemd/logind. Upstream not really supports a standalone logind, this is one reasons why. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
