Try using systemd suspend instead of pm-utils.
tomk
https://bbs.archlinux.org/profile.php?id=1822
2012-11-06T15:44:43Z
Not a solution, but you could try systemd suspend as an alternative - works perfectly for me.
tomk
https://bbs.archlinux.org/profile.php?id=1822
2013-03-02T11:51:50Z
Yes, the nicer interfaces are systemd units tied to sleep.target.I use just one, to lock my screen on resume with i3lock.
tomk
https://bbs.archlinux.org/profile.php?id=1822
2012-10-31T00:40:49Z
This is the point. xautolock don't want be dead with killall command, and even by -exit option... This is what i can't fix.And you're right i should kill it only when dischargins changed, but i haven't idea how do this...
xorgx3
https://bbs.archlinux.org/profile.php?id=54689
2012-09-13T14:29:25Z
So happy to be corrected Thanks, lucke, works perfectly now.
tomk
https://bbs.archlinux.org/profile.php?id=1822
2012-09-15T23:30:51Z
Well, it seems to be something to do with your wifi card - read up about your device and its power management capabilities.
tomk
https://bbs.archlinux.org/profile.php?id=1822
2012-09-19T20:46:45Z
That's what I'm using (place it e.g. at the bottom of .xinitrc):pidof -s xautolock >& /dev/null
if [ $? -ne 0 ]; then
xautolock -time 60 -locker "systemctl suspend" &
fi
bohoomil
https://bbs.archlinux.org/profile.php?id=41264
2013-02-01T12:39:28Z
First of all, don't presume things - establish the facts. I have no experience with Gnome, so my advice would be to see if 'systemctl suspend' works in a terminal. If it does, then you need to make sure that's what Gnome uses.
Ehmm... it's the circle of life.
tomk
https://bbs.archlinux.org/profile.php?id=1822
2012-12-15T15:35:28Z
Email this page