LMDE UP8 - mate does not suspend anymore when closing laptop lid

[Tim]

Right after installing the update pack 8, mate does not suspend anymore when i close the lid. Neither would it hibernate. Simply locks the screen, when i choose suspend or hibernate. Choosing "do nothing" DOES work.

dconf-editor shows, that configuration is correctly changed by the gui. Unfortunately I am not experienced enough to search deeper for problems...
Any idea?

I am running LMDE 64bit with mate on a thinkpad x200.

[Elmar (elmar-hagemeyer)]

I'm having the same problem (LMDE 64, HP-Notebook 625) since the recent dist-upgrade (probably UP8).
If I choose "hibernate" from the menu ist works fine, so there seems to be a problem with handling the acpi-event(?).

[Elmar (elmar-hagemeyer)]

I found out that on other debian-systems the same problem could be solved by adding "init=/lib/systemd/systemd" to the line starting with "GRUB_CMDLINE_LINUX_DEFAULT=" (Mine is now: "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash init=/lib/systemd/systemd radeon.audio=1") in the file /etc/default/grub.
After running "sudo update-grub" and restarting the system a service called "systemd" gets the process ID (PID) 1, which for whatever reason makes hibernate on lid-close work again.

(Source: https://wiki.debian.org/systemd)

Worked for me, but someone else has to explain why.

[Tim (tim-bader)]

loading systemd at system startup fixes the suspend issue on lid closure - but causes a lot of others, like compiz crashing and extremely high system load.
...so doesn't really work for me.

dmesg gives me the following:

[14821.222906] systemd-logind[4923]: Lid closed.
[14821.223061] systemd-logind[4923]: Suspending...
[14821.232498] systemd-logind[4923]: Failed to execute operation: Launch helper exited with unknown return code 1
[14821.232562] systemd-logind[4923]: Suspending...
[14821.235940] systemd-logind[4923]: Failed to execute operation: Launch helper exited with unknown return code 1
[14821.236026] systemd-logind[4923]: Suspending...
[14821.240097] systemd-logind[4923]: Failed to execute operation: Launch helper exited with unknown return code 1
[14822.835248] systemd-logind[4923]: Suspending...
[14822.851516] systemd-logind[4923]: Failed to execute operation: Launch helper exited with unknown return code 1
[14824.812898] systemd-logind[4923]: Lid opened.

so it obviously is linked to systemd. syslog also seems to complain about systemd:

dbus[3397]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper)
dbus[3397]: [system] Activated service 'org.freedesktop.systemd1' failed: Launch helper exited with unknown return code 1

at the same time suspending works excellently via dbus:

dbus-send --print-reply --system --dest=org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.Suspend

do i necessarily need systemd?

let me know if i can help any further for bug testing.

[John White (wfx)]

I have this same bug using Mate, if I login to LMDE using Cinnamon the suspend on lid close works correctly. I prefer Mate so what is the fix? In detail please as I am not real experienced in linux.

[dmdsoftware (ddurdle)]

Witnessing the same problem on UP8 w/ mate on both a X61s and T420. The suspend and hibernation keys also don't work -- simply lock the system. Looks like,from the error presented when pressing they keys, the systemd is at play here.

[HansPL (hans011)]

Same problem here, with LMDE Mate 32bit on an eeePC 901GO, immediately since update to UP8:  Suspend works via menu, but not via the suspend key.
If the screen saver is NOT set to »lock«, nothing happens upon pressing Suspend, only tailf /var/log/syslog shows

Feb 17 10:50:04 hpl10 dbus[2284]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Feb 17 10:50:04 hpl10 dbus[2284]: [system] Activated service 'org.freedesktop.systemd1' failed: Launch helper exited with unknown return code 1

If the screen saver IS set to »lock«, the screen is locked upon pressing Suspend.  And, with this setting, when the screen saver activated itself due to longer inactivity, I could not log back in while the drive activity LED was continuously active and the screen remained black.  I tried then to login on a terminal via Ctrl-Alt-F1, but »could not spawn process / no space«.  I only could cut power.  After reboot the system ran again and I could not find any error logs.  VERY annoying.

[HansPL (hans011)]

I also notice many udev errors on the boot screen and thought that might be related.  Did  apt-get remove hal  (see http://forums.linuxmint.com/viewtopic.php?f=198&t=158709).  While that removed the udev boot errors it did not help on this topic here.

[Elmar (elmar-hagemeyer)]

The solution of my last post did not help for a long time; maybe some other updates ("debian-system-adjustments") reverted it??

So I searched a little deeper and finally found a solution which definately works for me.

Installing the package systemd-sysv and uninstalling sysvinit made my HP625 hibernate on lid-close again.

As sysvinit is essential for the system to startup, you should do a system backup before or at least cross your fingers.

As far as I understood, sysvinit and systemd both manage services, where sysvinit is the robust, old school and user configurable one and systemd the newer and faster one.

It is obviously planned to make future debian versions work with systemd instead of sysvinit, a fact that seems to be much discussed.
Anyway, maybe lmde is suffering from its "rolling-release" in-between-status here??

(LMDE, HP625, AMD-Athlon, 64bit)

[Clement Lefebvre (clementlefebvre)]

MATE can work with or without systemd, but it doesn't detect it properly. It basically checks for logind and assumes systemd is running.

So when you switch to full systemd, it works in systemd mode.

And if you were to remove libpam-systemd and systemd, it would work fine in legacy mode.

The problem in LMDE is that we have logind but we don't use systemd itself...

So anyway, the easiest solution was to force MATE not to use systemd. That means people don't need to do anything but to accept the update to mate-power-manager 1.6.2-2+lmde and logout/login again.

Now.. for those who want to run systemd instead of init, please stick to mate-power-manager 1.6.2-1+lmde and hold onto it.

I've kept both versions in the repositories (1.6.2-1 in import, 1.6.2-2 in upstream) so everybody's happy :)