Brian May writes: > As of several days ago, it no longer sleeps when I close the lid with > Gnome. The trigger was moving to Brisbane, in Melbourne it was fine. Hasn't > come good since moving back to Melbourne however. > > If I manually type in "sudo systemctl start systemd-suspend" then it goes > to sleep fine. So I suspect this isn't the typical issue of suspend not > working, it is more like suspend isn't even getting triggered. > > Looking at /var/log/auth.log I see events being generated by systemd-login > for "Lid closed" and "Lid opened" - how do I debug why these aren't getting > turned into sleep events? > > It is possible this problem come about as a result of upgrading from a 4.0 > kernel to a 4.1 kernel, however I couldn't get get reproducible results > under 4.0. As in if I make a random change to the system, it can start > working and after a reboot it stops working.
Per logind.conf(5), * is HandleLidSwitch set to "suspend"? (the default) * is a userland daemon inhibiting systemd? e.g. XFCE4.10 doesn't; allegedly XFCE4.12 does. I assume gnome3 inhibits by default. If you don't want that, HibernateKeyIgnoreInhibited=true in logind.conf. OR Configure gnome's power stuff, somehow. * "Only input devices with the "power-switch" udev tag will be watched for key/lid" You can determine this in /run/udev/tags/power-switch, maybe also udevadm info/monitor. FWIW I cannot make the power button work in Debian 8 with either no GUI, or XFCE4.10, unless I *also* install acpid and use its default event handler. I haven't determined why that is yet, but it's not any of the above for me. I am not using systemd on any hosts with lids. I am not using systemd on any hosts with gnome. I am using Debian 8's versions of systemd & linux (v215 & 3.16). If you solve this issue, I would like to know the details about how. _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
