On Fri, 2014-03-14 at 01:45 +0100, Lennart Poettering wrote: > On Thu, 13.03.14 18:07, Martin Langhoff (martin.langhoff@xxxxxxxxx) wrote: > > > My Lenovo X220, running up-to-date F20 occasionally gets into a state where > > closing the laptop lid does not trigger suspend. > > > > I want to narrow down on the problem, but I'm slightly lost on how > > "the signal is routed" through the stack. udev->?-> systemd-suspend -> > > kernel ? > > The lid switch is exposed as input device in Linux. logind opens that > device and reacts on it. However it gives DEs the chance to inhibit > this if they desire so. Gnome at least doesn't inhibit it perminantly > though, but some components might delay suspends, for example Telepathy > to log you out of your Jabber server... > > Normally when you close the lid logind should log something about "Lid > closed" or so... Look around the logs around this to figure out what > mightbe going on. I've run into this too, is there a quick command to get the list of offending suspend inhibitors so we can debug further? (pressing the power button to initiate suspend usually works for me when lid close does not...) Dan -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
