On Mon, Feb 11, 2013 at 3:51 AM, Stefan G. Weichinger <li...@xunil.at> wrote: > Am 10.02.2013 20:47, schrieb Canek Peláez Valdés: > >> Yep, had the same problem, solved with: >> >> LidSwitchIgnoreInhibited=no >> >> in /etc/systemd/logind.conf. Since then it has happened again maybe a >> couple of times (I have no idea why), but most of the time (and I'm >> talking above 99%), it works as intended. >> >> These options are pretty new, I think they went live after GNOME 3.6, >> so I hope that with GNOME 3.8 we will be able to comment that line >> again and everything will work automagically. > > hopefully ... > > Unfortunately that parameter didn't help so far. > > Do you have acpid installed/enabled? Anything aside the default > acpi-scripts?
The last time I installed acpid was in November of 2010, and I uninstalled for the last time in April 2011. My machines are all acpid free since then; systemd + UPower takes cares of everything AFAIK. > I removed hibernate-script from my system now just to check things. I haven't used scripts to suspend or hibernate in ages; again UPower does everything, or perhaps some other part of the GNOME stack. sys-power/pm-utils is still being pulled in by upower-0.9.19, but it only calls pm-is-supported (src/linux/up-backend.c:363-390) to determine if the machine can suspend/hibernate. Which is kinda stupid, since pm-is-supported is only a set of scripts which test files in the /sys directory. UPower should test for those files directly (is in the linux backend anyway), and remove the pm-utils dependency. For the kernel I use vanilla-sources unstable; I haven't used gentoo-sources in ages (long before systemd), and I never used tuxonice-sources. Suspend/hibernate works perfectly in all my machines; I haven't had a failed resume in (literally) years. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
