how to (re)enable notify-osd?

blueblob · 2015-12-03 16:55:09

I have used notify-osd in the past, I am not sure when it stopped working for me.

I use notify-send to send notifications to notify-osd for both my email and a song name from pandora with pianobar such as the following:

notify-send -i /tmp/pandora.png "Pandora Radio" "Now playing: $title by $artist"

I know this notify-send line should work as long as the notification daemon is running, but I cannot figure out how to get the notification daemon running using systemd. I can start it manually by running /usr/lib/notify-osd/notify-osd but that's a hack. When I manually start notify-osd, the notifications work.

pacman -Ql notify-osd|grep \\.service
notify-osd /usr/share/dbus-1/services/org.freedesktop.Notifications.service

The contents of the service file are:

[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=/usr/lib/notify-osd/notify-osd

So as far as I can tell dbus is supposed to automatically start these services (and apparently was in the past).

Following the dbus wiki page I installed d-feet and looked at org.freedesktop.Notifications which gave me:

org.freedesktop.Notifications : g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.Notifications exited with status 1 (25)

ewaller · 2015-12-03 17:22:28

What WM/DE do you use? I use i3wm and, after reading your post, I realized I had not yet installed it on this new installation on the laptop beside me. I ran notify-send, (as a control) and it did not work. I installed notify-osd, exited i3, restarted i3 and run notify-send. It worked, easy as cake. And it was started by the dbus service. And the dbus service started when I started i3. What is the output of systemctl status --no-pager ?

Last edited by ewaller (2015-12-03 17:22:44)

blueblob · 2015-12-03 17:31:43

I run openbox. I am pretty sure the failed unit is httpd because I haven't updated my apache conf file.

systemctl status --no-pager
● blueblob
    State: degraded
     Jobs: 0 queued
   Failed: 1 units
    Since: Thu 2015-12-03 12:04:45 EST; 20min ago
   CGroup: /
           ├─init.scope
           │ └─1 /sbin/init
           ├─system.slice
           │ ├─slim.service
           │ │ └─422 /usr/lib/xorg-server/Xorg -nolisten tcp vt07 -auth /var/run/slim.auth
           │ ├─dbus.service
           │ │ └─383 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
           │ ├─org.cups.cupsd.service
           │ │ └─382 /usr/bin/cupsd -l
           │ ├─fail2ban.service
           │ │ └─429 /usr/bin/python /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -b
           │ ├─atd.service
           │ │ └─391 /usr/bin/atd
           │ ├─systemd-journald.service
           │ │ └─165 /usr/lib/systemd/systemd-journald
           │ ├─ntpd.service
           │ │ └─418 /usr/bin/ntpd -g -u ntp:ntp
           │ ├─systemd-logind.service
           │ │ └─387 /usr/lib/systemd/systemd-logind
           │ ├─system-getty.slice
           │ │ └─getty@tty1.service
           │ │   └─401 /sbin/agetty --noclear tty1 linux
           │ ├─sshd.service
           │ │ └─411 /usr/bin/sshd -D
           │ ├─systemd-udevd.service
           │ │ └─208 /usr/lib/systemd/systemd-udevd
           │ ├─polkit.service
           │ │ └─450 /usr/lib/polkit-1/polkitd --no-debug
           │ ├─cronie.service
           │ │ └─381 /usr/bin/crond -n
           │ └─rtkit-daemon.service
           │   └─447 /usr/lib/rtkit/rtkit-daemon
           └─user.slice
             └─user-1000.slice
               ├─user@1000.service
               │ ├─gvfs-daemon.service
               │ │ ├─543 /usr/lib/gvfs/gvfsd
               │ │ └─548 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
               │ ├─dbus.service
               │ │ ├─458 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
               │ │ ├─465 /usr/lib/GConf/gconfd-2
               │ │ ├─531 /usr/lib/at-spi2-core/at-spi-bus-launcher
               │ │ ├─536 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
               │ │ └─538 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
               │ ├─pulseaudio.service
               │ │ ├─446 /usr/bin/pulseaudio --daemonize=no
               │ │ └─463 /usr/lib/pulse/gconf-helper
               │ └─init.scope
               │   ├─440 /usr/lib/systemd/systemd --user
               │   └─441 (sd-pam)
               └─session-c1.scope
                 ├─ 402 /usr/bin/slim -nodaemon
                 ├─ 466 /usr/bin/openbox --startup /usr/lib/openbox/openbox-autostart OPENBOX
                 ├─ 512 xcompmgr -C
                 ├─ 513 bmpanel2 -c /home/blueblob/.config/bmpanel2/bmpanel2rc
                 ├─ 514 python2 /usr/bin/adeskmenu --no-tray
                 ├─ 516 urxvtd
                 ├─ 517 sh /home/blueblob/.config/openbox/autostart
                 ├─ 524 megasync
                 ├─ 527 /usr/bin/python3 /usr/share/system-config-printer/applet.py
                 ├─ 528 pasystray
                 ├─ 566 wbar
                 ├─ 572 -bash
                 ├─ 751 -bash
                 ├─ 886 firefox
                 ├─1388 -bash
                 ├─1463 /usr/bin/tmux new -s piano -d ; new-window pianobar ; kill-window -t0 ; attach
                 ├─1465 /usr/bin/tmux new -s piano -d ; new-window pianobar ; kill-window -t0 ; attach
                 ├─1476 pianobar
                 ├─4154 -bash
                 └─4247 systemctl status --no-pager

ewaller · 2015-12-03 17:39:51

That is weird. I think this is a dbus issue, but I don't have any suggestions. Sadly, I cannot dig into this right now.

Arch Linux

#1 2015-12-03 16:55:09

how to (re)enable notify-osd?

#2 2015-12-03 17:22:28

Re: how to (re)enable notify-osd?

#3 2015-12-03 17:31:43

Re: how to (re)enable notify-osd?

#4 2015-12-03 17:39:51

Re: how to (re)enable notify-osd?

Board footer