You are not logged in.
Pages: 1
Hi,
I have been experiencing an odd issue lately with my Thinkpad T520. I don't remember when it started exactly, but it is starting to get really annoying. The problem is everytime my laptop wakes from sleep, it immediately goes to sleep again. This can be seen by the snippet from everything.log
Oct 3 07:47:15 think systemd-sleep[7236]: System resumed.
Oct 3 07:47:15 think acpid: client connected from 8921[0:0]
Oct 3 07:47:15 think acpid: 1 client rule loaded
Oct 3 07:47:15 think systemd[1]: Started Suspend.
Oct 3 07:47:15 think systemd[1]: Service sleep.target is not needed anymore. Stopping.
Oct 3 07:47:15 think systemd[1]: Stopping Sleep.
Oct 3 07:47:15 think systemd[1]: Stopped target Sleep.
Oct 3 07:47:15 think systemd[1]: Starting Suspend.
Oct 3 07:47:15 think systemd[1]: Reached target Suspend.
and from journalctl
Oct 03 07:47:15 think kernel: PM: resume of devices complete after 655.190 msecs
Oct 03 07:47:15 think kernel: PM: Finishing wakeup.
Oct 03 07:47:15 think kernel: Restarting tasks ... done.
Oct 03 07:47:15 think kernel: video LNXVIDEO:00: Restoring backlight state
Oct 03 07:47:15 think systemd[1]: Started Suspend.
Oct 03 07:47:15 think systemd[1]: Service sleep.target is not needed anymore. Stopping.
Oct 03 07:47:15 think systemd[1]: Stopping Sleep.
Oct 03 07:47:15 think systemd[1]: Stopped target Sleep.
Oct 03 07:47:15 think systemd[1]: Starting Suspend.
Oct 03 07:47:15 think systemd[1]: Reached target Suspend.
I am using systemd with KDE 4.9.1 (powermanagment configured). I don't have any other DE so I don't know if it is KDE specific. I'm not sure why systemd is putting the system back to sleep.
How do I find out what is going on and how would I prevent the laptop from going to sleep again?
Last edited by ayr0 (2012-10-03 15:57:14)
Offline
Always good to search before posting:
Offline
Always good to search before posting:
I'm not sure how this relates to my issue. I didn't have a problem upgrading util-linux and removing eject.
Offline
Sorry - I meant this one:
https://bbs.archlinux.org/viewtopic.php?id=149711
Last edited by tomk (2012-10-03 15:02:48)
Offline
Sorry - I meant this one:
Thank you so much. It fixed the problem (at least until KDE patches it). I kept searching in the Laptop Issues forum and couldn't really find anything about it.
Just a quick blurb about the solution for future reference.
The bug is a KDE bug (that is apparently still present in 4.9.2). My solution was to add a sleep.sh and put it in .kde4/Autostart and make it executable.
sleep.sh
systemd-inhibit --what=handle-lid-switch:handle-power-key:handle-suspend-key:handle-hibernate-key sleep 9999d
Last edited by ayr0 (2012-10-03 16:08:18)
Offline
Pages: 1