Notifications with systemd timer disappear to fast

thufirhawat · 2014-05-30 18:09:04

Hi,

I use systemd timers as cron replacement to display a low battery warning with dunst. Everything works fine, except that the dunst notification disappears almost imediately.

Any hints how it last longer than a millisecond?

Cheers and thanks

SolarBoyMatt · 2014-05-30 18:46:35

Can you post the .timer file you're using?

thufirhawat · 2014-05-30 21:01:43

Sure, here you go:

# cat battery-warning.timer
[Unit]
Description=Battery Timer

[Timer]
OnCalendar=*:0/1
Persistent=true
Unit=battery-warning.service

[Install]
WantedBy=basic.target

Stebalien · 2014-05-31 00:33:27

And the service. Also, you probably don't need it to be persistent and it should have WantedBy=timers.target instead of basic.target.

Last edited by Stebalien (2014-05-31 00:35:11)

thufirhawat · 2014-05-31 17:28:53

Here's the service:

[Unit]
Description=Check battery and display warning

[Service]
User=xhr
Environment=DISPLAY=:0
Type=oneshot
ExecStartPre=
ExecStart=/home/x/bin/low-battery

And the script:

$ cat low-battery
#!/bin/bash

# From https://faq.i3wm.org/question/1730/warn … -very-low/

BATTINFO=`acpi -b`

if [[ `echo $BATTINFO | grep Discharging` && `echo $BATTINFO | cut -f 5 -d " "` < 00:15:00 ]] ; then
DISPLAY=:0.0 /usr/bin/notify-send -u critical -t 1000 "Low Battery" "$BATTINFO"
fi

Stebalien · 2014-05-31 18:08:01

When you run notify-send from a systemd service, it doesn't know about your dbus session bus (the DBUS_SESSION_BUS_ADDRESS environment variable isn't set). Basically, notify-send is forking a dbus instance, telling it to display a notification (which causes the dbus instance to start dunst), and then exiting. Unfortunately, when it exits, systemd helpfully cleans up any leftover children (the dbus instance and dnust).

The correct way to do this is to use a systemd user instance (https://wiki.archlinux.org/index.php/Systemd/User). Basically, just move those units over to the user instance and make sure to configure dbus correctly.

Also, in the future, please use code tags when pasting blocks of code.

Last edited by Stebalien (2014-05-31 18:09:46)

jrk · 2015-07-15 13:51:34

I'd like to add that the proper way of doing this would be to listen for a dbus signal emitted for example by UPower. That'd avoid polling completely.

Stebalien · 2015-07-15 14:04:51

jrk wrote:

I'd like to add that the proper way of doing this would be to listen for a dbus signal emitted for example by UPower. That'd avoid polling completely.

UPower also polls (every 30s when discharging/120s otherwise). Regardless, this topic is over a year old, pease don't necrobump.

ewaller · 2015-07-15 14:13:19

Time to close this topic. If someone wishes to continue, please pick it up in a new thread and link back to this one.

Thanks.

Arch Linux

#1 2014-05-30 18:09:04

Notifications with systemd timer disappear to fast

#2 2014-05-30 18:46:35

Re: Notifications with systemd timer disappear to fast

#3 2014-05-30 21:01:43

Re: Notifications with systemd timer disappear to fast

#4 2014-05-31 00:33:27

Re: Notifications with systemd timer disappear to fast

#5 2014-05-31 17:28:53

Re: Notifications with systemd timer disappear to fast

#6 2014-05-31 18:08:01

Re: Notifications with systemd timer disappear to fast

#7 2015-07-15 13:51:34

Re: Notifications with systemd timer disappear to fast

#8 2015-07-15 14:04:51

Re: Notifications with systemd timer disappear to fast

#9 2015-07-15 14:13:19

Re: Notifications with systemd timer disappear to fast

Board footer