[arch-general] immediate sleep after resume
This started happening sometime after I switched to systemd (tho I am not finger pointing). Upon resume - the laptop immediately sleeps - the second resume is fine. Not every time either. Fresh boot - sleep - resume cycle seems to work fine. Googling suggested putting this in /etc/systemd/login.conf LidSwitchIgnoreInhibited=no However this makes no sense to me - as surely systemd knows the difference between the open and close lid events. The argument made was that there was competition between kde and systemd to sleep/resume and this would keep systemd from doing anything. Anyway - above makes no difference :-) Anyone have any ideas? testing repo fully updated - using kde and systemd. gene/
On 15 Nov 2012 13:52, "Genes MailLists" <lists@sapience.com> wrote:
This started happening sometime after I switched to systemd (tho I am not
finger pointing).
Upon resume - the laptop immediately sleeps - the second resume is fine. Not every time either. Fresh boot - sleep - resume cycle seems to work
fine.
Googling suggested putting this in /etc/systemd/login.conf
LidSwitchIgnoreInhibited=no
However this makes no sense to me - as surely systemd knows the
difference between the open and close lid events. The argument made was that there was competition between kde and systemd to sleep/resume and this would keep systemd from doing anything.
Anyway - above makes no difference :-)
Anyone have any ideas?
testing repo fully updated - using kde and systemd.
gene/
Hmm I am having the same behaviour without testing repos enabled, up to date, and with slim + xfce. I am also using systemd. It might have to do with the WiFi. Mine is a broadcom chip and unfortunately i found only the closed source drivers work (wl). I will try the suggested from Google config. Thanks, Leonidas
Hi I had a similar problem using systemd+KDE. I think I manged to fix it by setting these values in /etc/systemd/logind.conf: HandlePowerKey=ignore HandleSuspendKey=ignore HandleHibernateKey=ignore HandleLidSwitch=ignore As I understand the manual for these options, this will prevent systemd from handling all those Power/Suspend/Lid events. They will be handled by KDE. Also I tried to disable power management in KDE, as I remember it fixed the immediate sleep, but then I was not able to sleep/hibernate using KDE menus. Best regards -- Maciej Sitarz
On 11/15/12 at 02:11pm, Leonidas Spyropoulos wrote:
On 15 Nov 2012 13:52, "Genes MailLists" <lists@sapience.com> wrote:
This started happening sometime after I switched to systemd (tho I am not
finger pointing).
Upon resume - the laptop immediately sleeps - the second resume is fine. Not every time either. Fresh boot - sleep - resume cycle seems to work
fine.
Googling suggested putting this in /etc/systemd/login.conf
LidSwitchIgnoreInhibited=no
However this makes no sense to me - as surely systemd knows the
difference between the open and close lid events. The argument made was that there was competition between kde and systemd to sleep/resume and this would keep systemd from doing anything.
Anyway - above makes no difference :-)
Anyone have any ideas?
testing repo fully updated - using kde and systemd.
gene/
Hmm I am having the same behaviour without testing repos enabled, up to date, and with slim + xfce. I am also using systemd.
It might have to do with the WiFi. Mine is a broadcom chip and unfortunately i found only the closed source drivers work (wl).
I will try the suggested from Google config.
Thanks, Leonidas
In your apparent google adventure, I find it suprising yuo did not find the correct answer as I have seen it come up in the forums many many times. Also suprising is that when you found the suggestion to use LidSwitchIgnoreInhibited=no, you didn't then find that logind.conf has other options in that file. See the logind.conf man page for the answer. -- Curtis Shimamoto sugar.and.scruffy@gmail.com
On Thu, Nov 15, 2012 at 2:52 PM, Genes MailLists <lists@sapience.com> wrote:
This started happening sometime after I switched to systemd (tho I am not finger pointing).
Upon resume - the laptop immediately sleeps - the second resume is fine. Not every time either. Fresh boot - sleep - resume cycle seems to work fine.
Googling suggested putting this in /etc/systemd/login.conf
LidSwitchIgnoreInhibited=no
However this makes no sense to me - as surely systemd knows the difference between the open and close lid events. The argument made was that there was competition between kde and systemd to sleep/resume and this would keep systemd from doing anything.
Anyway - above makes no difference :-)
Anyone have any ideas?
testing repo fully updated - using kde and systemd.
gene/
I used to have that problem as well. I fixed it by setting HandleLidSwitch=ignore in /etc/systemd/login.conf. -- Daniel Egeberg
Forgot to mention in original post - it seems well understood that the window managers may or may not play nicely with systemd - as to who will do power management. If a user is not logged in - it is still nice to have systemd sleep system on lid close for example - and for this reason the window managers are given the ability to "inhibit" systemd when they are claiming to do the power management. And when they are not, then systemd does not get the "inhibit". [1] Several window managers, KDE among them are supposed to "play nice" with systemd in this regard. So, one suggestion some have is not to use KDE at all for this - and rely solely on systemd - it is of course less configurable. I have not yet tried this approach. This can be done via the same login.conf. It's not a huge deal, as I just press power button to wake it up again, but curious what others have found. gene [1] I'd rather have a positive than a triple negative LidSwitchIgnoreInhibited=no might be easier to read as LidSwitchInhibitIsActive=yes
On 11/15/12 at 11:18am, Genes MailLists wrote:
Forgot to mention in original post - it seems well understood that the window managers may or may not play nicely with systemd - as to who will do power management.
If a user is not logged in - it is still nice to have systemd sleep system on lid close for example - and for this reason the window managers are given the ability to "inhibit" systemd when they are claiming to do the power management. And when they are not, then systemd does not get the "inhibit". [1]
Several window managers, KDE among them are supposed to "play nice" with systemd in this regard.
So, one suggestion some have is not to use KDE at all for this - and rely solely on systemd - it is of course less configurable. I have not yet tried this approach. This can be done via the same login.conf.
It's not a huge deal, as I just press power button to wake it up again, but curious what others have found.
gene
[1] I'd rather have a positive than a triple negative LidSwitchIgnoreInhibited=no might be easier to read as LidSwitchInhibitIsActive=yes
Personally I just use xautolock, so I don't have to deal with these competing systemd. I just use the native systemd (actually in its default form), and it works well. I was not aware that you were working towards teh goal of having systemd actually handle the stuff, as other users typically wanted their DE to handle the power management, and have systemd do nothing. This is why I directed you to the man page, in hopes that you would find the HandleLidSwitch= setting. As far as doing it the way you want, I have heard (though I don't use KDE so I have no personal experience) that it's power management does not play nicely with this system. I am not sure what power management setups do play nicely, but every KDE user that I have come across all ended up just setting HandleLidSwitch=ignore and being done with it. If you can get your proposed setup working, I would love to hear about it. I do not use said systems, but I still welcome knowledge. Maybe a DE user can weigh in here. Best of luck. Regards, -- Curtis Shimamoto sugar.and.scruffy@gmail.com
On Thu, Nov 15, 2012 at 11:37 AM, Curtis Shimamoto < sugar.and.scruffy@gmail.com> wrote:
On 11/15/12 at 11:18am, Genes MailLists wrote:
Forgot to mention in original post - it seems well understood that the window managers may or may not play nicely with systemd - as to who will do power management.
If a user is not logged in - it is still nice to have systemd sleep system on lid close for example - and for this reason the window managers are given the ability to "inhibit" systemd when they are claiming to do the power management. And when they are not, then systemd does not get the "inhibit". [1]
Several window managers, KDE among them are supposed to "play nice" with systemd in this regard.
So, one suggestion some have is not to use KDE at all for this - and rely solely on systemd - it is of course less configurable. I have not yet tried this approach. This can be done via the same login.conf.
It's not a huge deal, as I just press power button to wake it up again, but curious what others have found.
gene
[1] I'd rather have a positive than a triple negative LidSwitchIgnoreInhibited=no might be easier to read as LidSwitchInhibitIsActive=yes
Personally I just use xautolock, so I don't have to deal with these competing systemd. I just use the native systemd (actually in its default form), and it works well.
I was not aware that you were working towards teh goal of having systemd actually handle the stuff, as other users typically wanted their DE to handle the power management, and have systemd do nothing. This is why I directed you to the man page, in hopes that you would find the HandleLidSwitch= setting.
As far as doing it the way you want, I have heard (though I don't use KDE so I have no personal experience) that it's power management does not play nicely with this system. I am not sure what power management setups do play nicely, but every KDE user that I have come across all ended up just setting HandleLidSwitch=ignore and being done with it.
If you can get your proposed setup working, I would love to hear about it. I do not use said systems, but I still welcome knowledge.
Maybe a DE user can weigh in here. Best of luck.
Regards, -- Curtis Shimamoto sugar.and.scruffy@gmail.com
On the wiki here<https://wiki.archlinux.org/index.php/Systemd#ACPI_power_management>in the warning section it says that only Gnome and KDE play nice right now and you can put ignore in all the Handle fields in logind.conf to allow your DE or WM to manage it instead. Seems to be working for me on XFCE.
On Thu, 15 Nov 2012 08:37:00 -0800 Curtis Shimamoto <sugar.and.scruffy@gmail.com> wrote:
On 11/15/12 at 11:18am, Genes MailLists wrote:
Forgot to mention in original post - it seems well understood that the window managers may or may not play nicely with systemd - as to who will do power management.
If a user is not logged in - it is still nice to have systemd sleep system on lid close for example - and for this reason the window managers are given the ability to "inhibit" systemd when they are claiming to do the power management. And when they are not, then systemd does not get the "inhibit". [1]
Several window managers, KDE among them are supposed to "play nice" with systemd in this regard.
So, one suggestion some have is not to use KDE at all for this - and rely solely on systemd - it is of course less configurable. I have not yet tried this approach. This can be done via the same login.conf.
It's not a huge deal, as I just press power button to wake it up again, but curious what others have found.
gene
[1] I'd rather have a positive than a triple negative LidSwitchIgnoreInhibited=no might be easier to read as LidSwitchInhibitIsActive=yes
Personally I just use xautolock, so I don't have to deal with these competing systemd. I just use the native systemd (actually in its default form), and it works well.
I was not aware that you were working towards teh goal of having systemd actually handle the stuff, as other users typically wanted their DE to handle the power management, and have systemd do nothing. This is why I directed you to the man page, in hopes that you would find the HandleLidSwitch= setting.
As far as doing it the way you want, I have heard (though I don't use KDE so I have no personal experience) that it's power management does not play nicely with this system. I am not sure what power management setups do play nicely, but every KDE user that I have come across all ended up just setting HandleLidSwitch=ignore and being done with it.
If you can get your proposed setup working, I would love to hear about it. I do not use said systems, but I still welcome knowledge.
Maybe a DE user can weigh in here. Best of luck.
Regards,
Hi . Well thou not using a laptop i am using systemd and the latest kde 4.9.3 . I use the sleep button on the keyboard (logotech internet navigator usb) it all works perfectly apart from a complaint about shutting down 3 of the 4 CPU cores prior to full shutdown Reboot is almost instant working after approximately 3 seconds Pete . -- Linux 7-of-9 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64 GNU/Linux
On Thu, Nov 15, 2012 at 08:52:09AM -0500, Genes MailLists wrote:
This started happening sometime after I switched to systemd (tho I am not finger pointing).
Upon resume - the laptop immediately sleeps - the second resume is fine. Not every time either. Fresh boot - sleep - resume cycle seems to work fine.
I had this same error not too long ago, don't know if it's related, but I didn'thave my suspend hooks set up right. [1]
Googling suggested putting this in /etc/systemd/login.conf
LidSwitchIgnoreInhibited=no
However this makes no sense to me - as surely systemd knows the difference between the open and close lid events. The argument made was that there was competition between kde and systemd to sleep/resume and this would keep systemd from doing anything.
Anyway - above makes no difference :-)
Anyone have any ideas?
testing repo fully updated - using kde and systemd.
gene/
[1] https://wiki.archlinux.org/index.php/Systemd#Sleep_hooks -- William Giokas | KaiSforza GnuPG Key: 0xE99A7F0F Fingerprint: F078 CFF2 45E8 1E72 6D5A 8653 CDF5 E7A5 E99A 7F0F
participants (8)
-
Curtis Shimamoto
-
Daniel Egeberg
-
Genes MailLists
-
Leonidas Spyropoulos
-
Luke Johnson
-
Maciej Sitarz
-
P .NIKOLIC
-
William Giokas