Suspend Not Working Post 2013-09-17 Move Away From Init

Question

Hello,
    I would first like to say I have been happily using Arch for about a year now and I'm very thankful for the wonderful arch wiki that has answered more questions than I can count. However, I seem to be stuck on this one. Recently, after updating my system I am no longer able to suspend my system reliably. Initially all my Fn keys worked out of the box on my Lenovo laptop, as well suspend upon closing the lid. I would say it works about 10% of the time now. I believe this problem stems from something in my systemd configs although I do not know that to be the case. This became a problem after arch officially moved to systemd around 2013-09-17. Now most times I cannot suspend, hibernate, or power off my machine safely. Normally I am forced to use 'sudo poweroff -f' as it is the only command that works. My function keys for screen brightness etc have become laggy or unresponsive at times as well. As this is a fairly obtrusive issue, any help would be appreciated.
    Thanks!

Answer 1

crf wrote: Where have you been? Final notice of end of initscripts support is https://www.archlinux.org/news/end-of-i … s-support/.
As mentioned, I am a fairly new user, even more so this install itself is only about 6 months old so this post was before my time. I was referring to https://www.archlinux.org/news/deprecat … ysctlconf/
cfr wrote:Work through https://wiki.archlinux.org/index.php/Sy … nitscripts if you have not already done so.
I have gone through this with no luck.
cfr wrote:Make sure polkit is installed. Remove yourself from any potentially problematic groups (e.g. power etc.)
polkit is installed, although I'm rather confused as to how this would cause an issue as I'm not sure I entirely understand it's function.
cfr wrote:Make sure you do not have multiple things trying to handle the suspend, although usually this causes a double-suspend rather than none at all.
Once again, my newbie status leaves me unsure of how to pursue this one.
crf wrote:What were you using to control this stuff? Do you know what is being used now?
Thankfully my suspend worked out of the box, as a result I didn't investigate as to how it was working so I don't really know. For the few things that didn't work (volume keys, lock screen) I used xbindkeys.
cfr wrote:Is your system completely up to date? Have you dealt with all pacnew and pacsave files?
Yes, I have updated my system several times since then to no avail. As to the pacnew and pacsave files, This is new for me, am I correct in saying these are saved config files that were replaced during a previous update that I need to somehow reincorporate? I searched for them but from what I can see none of them seem to be related to my issue.
$ find / -regextype posix-extended -regex ".+\.pac(new|save|orig)" 2> /dev/null
/etc/group.pacnew
/etc/gshadow.pacnew
/etc/colord.conf.pacnew
/etc/pacman.d/mirrorlist.pacnew
/etc/ppp/ip-down.d/00-dns.sh.pacnew
/etc/ppp/ip-up.d/00-dns.sh.pacnew
/boot/grub/grub.cfg.pacnew
/boot/grub/grub.cfg.pacsave
Also, I would like to note that at the time of this post suspend is working perfectly fine, however the problem is not solved as its functionality phases in and out. I don't know if its sporadic behavior is helpful in this troubleshoot or not, just throwing it out there.
Update: its not working again, tried to shutdown via terminal and this was the error.
sudo shutdown -h now
[sudo] password for _____:
Failed to open /dev/initctl: No such device or address
Failed to talk to init daemon.
Last edited by Specter (2013-10-03 04:47:52)