Yes, the nicer interfaces are systemd units tied to sleep.target.I use just one, to lock my screen on resume with i3lock.
on 10/30/2012 – Made popular on 10/30/2012
mellowmaroon wrote:The way net-auto-wireless has worked for me since having rc.conf was that it would establish a connection at boot. If I put my laptop to sleep and reopened it at my friend's house, it doesn't attempt to establish a connection even though I have a profile in /etc/network.d for the wifi.This is known, related bug report here: https://bugs.archlinux.org/task/31037 ,
Everything that you see during boot up is in systemd's journal, so don't worry about it scrolling too fast. The error messages there should be enough for you to sort it out.FWIW my NFS shares work fine under systemd, and I'm also using netcfg with static ip.
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.
Assuming that /etc/systemd/system/macchanger@.service is exactly as provided on that wiki page, use systemctl and/or journalctl to investigate why it failed, just as you would with any other failing systemd service.