how to run a user script after systemd wakeup?

Question

When my debian jessie desktop box wakes up from sleep (via the new shiny systemd) my mouse settings are returned to their defaults, having reset my customisation

xinput set-prop 12 'Device Accel Constant Deceleration' 2.5

which runs when I log in.

how can I run an arbitrary user script on wakeup? (assume that the user is the owner of the X session)

As far as I can recall, the following is the only customisation I've made of the systemd setup (yes, I know it's completely wrong because it doesn't work for arbitrary users, but I've not worked out how to do that yet... this is somewhat related)

additionally, how can I run an arbitrary user script before wakeup, as the user who is currently using the X screen?

cat /etc/systemd/system/i3lock.service

#systemctl enable i3lock.service

[Unit]
Description=i3lock
Before=sleep.target

[Service]
User=fommil
Type=forking
Environment=DISPLAY=:0
ExecStart=/usr/bin/i3lock -c 000000

[Install]
WantedBy=sleep.target

Answer 1

This answer is based on askubuntu.com/a/661747/394818 (as also referred to in the comment by @sun-bear), askubuntu.com/q/616272/394818 and superuser.com/a/1269158/585953.

Using a system service:

Create the file /etc/systemd/system/my_user_script.service:

[Unit]
Description=Run my_user_script
After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target


[Service]
ExecStart=/path/to/my_user_script
#User=my_user_name
#Environment=DISPLAY=:0

[Install]
WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

Remove suspend/hibernate/hybrid in case the service should only be executed after waking up from a specific type of sleep. In case the service needs to be run by a specific user, uncomment the User= and Environment= lines and replace the relevant user name.

Install the service file with:

sudo systemctl enable my_user_script

Using a user service will not work:

In order to avoid setting a hard coded user name with User=, one could create the exact same service file at ~/.config/systemd/user/my_user_script.service and activate with

systemctl --user enable my_user_script

However, that will not work. @grawity explains in more detail at unix.stackexchange.com/a/174837/163108 why that is:

sleep.target is specific to system services. The reason is, sleep.target is not a magic target that automatically gets activated when going to sleep. It's just a regular target that puts the system to sleep – so the 'user' instances of course won't have an equivalent. (And unfortunately the 'user' instances currently have no way to depend on systemwide services.)

Answer 2

I created a file in /lib/systemd/system-sleep/ (you can call it e.g. wakeup):

#!/bin/sh
case $1 in
  post)
    /bin/runme
  ;;
esac

Then I set the executable permission bits.

# chmod +x /usr/lib/systemd/system-sleep/wakeup

The post is called on wakeup.

For further reading, look here.

Answer 3

You can also create a systemd unit file:

# /etc/sysstemd/system/awake.service
# ExecStart is executed on wake up from 'sleep' (suspend or hibernate).
[Unit]
WantedBy=sleep.target
After=systemd-suspend.service systemd-hybrid-sleep.service systemd-hibernate.service

[Service]
Type=simple
ExecStart=/bin/bash -c 'echo awake from sleep' >> /tmp/awake.notes'

Often this will be used to restart a systemd service.

ExecStart=/bin/systemctl restart fancontrol

Answer 4

Open this file:

sudo vim /lib/systemd/system-sleep/hdparm

Contents:

#!/bin/sh

case $1 in   
post)
    /usr/lib/pm-utils/power.d/95hdparm-apm resume
    ## Paste your command to run your script
    ;; 
esac

Your command will execute with admin privileges.

Answer 5

All previous solutions do not provide a way to actually start a user unit after wakeup. You may want to use a user unit since you imported your environment variables there (e.g. with dbus-update-activation-environment --all --systemd).

I could only find an ugly solution to this problem which involves creating a system service that starts the user service:

Create the system service /etc/systemd/system/[email protected]:

[Unit]
Description=Run user unit of %i after wakeup.
After=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl --user --machine=%i@ start --wait afterwakeup.service

[Install]
WantedBy=suspend.target hibernate.target hybrid-sleep.target suspend-then-hibernate.target

Inspired by https://unix.stackexchange.com/a/713646/454143.

And the user unit ~/.config/systemd/user/afterwakeup.service:

[Unit]
Description=Runs after wakeup from suspend etc.

[Service]
ExecStart=<do anything you want here, dont forget to import your environment>
Type=oneshot

Now run systemctl enable afterwakeup@<youruser>.service and don't forget to import your user environment, e.g. in .xinitrc (dbus-update-activation-environment --all --systemd).