CODEWITHSUNDEEP
pythonlinuxsystemdnotify-send
Wajahat
Wajahat

Reputation: 117

systemd service not executing notify-send

I want to generate pop-ups for certain events in my python script. I am using 'notify-send' for that purpose.

subprocess.Popen(['notify-send', "Authentication", "True/False"])

The above command executes fine on terminal but when I run it from systemd-service it does not generate any pop-up.

When I see logs there are no errors.

Upvotes: 3

Views: 5698

Answers (3)

Cirelli94
Cirelli94

Reputation: 1867

If running notify-send for desktop notifications in cron, notify-send is sending values to dbus. So it needs to tell dbus to connect to the right bus. The address can be found by examining DBUS_SESSION_BUS_ADDRESS environment variable and setting it to the same value.

Copy the value of DISPLAY and DBUS_SESSION_BUS_ADDRESS from your running environment and set them in [Service].Environment section

More info on the Arch Wiki: https://wiki.archlinux.org/index.php/Cron#Running_X.org_server-based_applications

Upvotes: 1

Abhyam Gupta
Abhyam Gupta

Reputation: 175

You need to first set the environment variable so that the root can communicate with the currently logged user and send the notification in GUI.

In my case, I did it as follow:

[Unit]
Description=< write your description>
After=systemd-user-sessions.service,systemd-journald.service

[Service]
Type=simple
ExecStart=/bin/bash /<path to your script file>.sh
Restart=always
RestartSec=1
KillMode=process
IgnoreSIGPIPE=no
RemainAfterExit=yes
Environment="DISPLAY=:0" "XAUTHORITY=/home/<User name>/.Xauthority"

[Install]
WantedBy=multi-user.target

Here,

RemainAfterExit=yes

is very important to mention in service file.

make sure to change all the parameters like Description, User name and path to your script file.

also, make sure that script file has executable permission by executing the command

sudo chmod +x <path to your script file>.sh

Here my script file is written in bash which shows the notification by using the same 'notify-send' command.

Now here the Environment parameter is doing all the magic.

you can read more about this behavior and the problem discussed overhere.

I certainly don't know the complete working of these files or how this worked, but for me, it worked just fine.

So you can give it a try.

please let me know if this worked or not in your case.

Upvotes: 3

Mark Stosberg
Mark Stosberg

Reputation: 13381

Running graphical applications requires the DISPLAY environment variable to be set, which would be set when run it from the CLI, but not when run from systemd (unless you explicitly set it).

This issue is covered more in Writing a systemd service that depends on XOrg.

I agree with the general advise that systemd may not be the best tool for the job. You may be better off using an "auto start" feature of your desktop environment to run your app, which would set the correct things in the environment that you need.

Upvotes: 0

Related Questions