Notifications don't show up (notify-send notify-osd)

[Alban Crequy]

On Tue, 6 May 2014 18:07:35 +0200
Mehturt <mehturt at gmail.com> wrote:

> On Tue, May 6, 2014 at 5:50 PM, Thiago Macieira <thiago at kde.org>
> wrote:
> > Em ter 06 maio 2014, às 17:42:36, Mehturt escreveu:
> >> ** (notify-osd:30409): WARNING **: Couldn't connect to
> >> accessibility bus: Failed to connect to
> >> socket /tmp/dbus-JOB9rCGFAt: Connection refused
> >>
> >> ** (notify-osd:30409): WARNING **: dbus_create_service_instance():
> >> Got error "Failed to connect to socket /tmp/dbus-GWnKyuCbfH:
> >> Connection refused"
> >
> > Check if the dbus-daemons running the buses above are still running.
> 
[...]
> These are my dbus processes:
> $ ps -ef|grep dbus
> 
> message+  2237     1  0 máj05 ?       00:00:22 /usr/bin/dbus-daemon
> --system user    2909     1  0 14:00 ?
> 00:00:00 /usr/bin/dbus-launch --autolaunch
> 1256b075bc99dcab8bbcb024522a5607 --binary-syntax --close-stderr
> user    2910     1  0 14:00 ?        00:00:00 /usr/bin/dbus-daemon
> --fork --print-pid 5 --print-address 7 --session
> user    2916  2912  0 14:00 ?        00:00:00 /usr/bin/dbus-daemon
> --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address
> 3

On Debian, the accessibility bus is started
by /etc/xdg/autostart/at-spi-dbus-bus.desktop so it runs within the
session bus environment.

So I would get the pid of dbus-daemon used for the accessibility bus:
PID=2916
in your logs.

Or any other process you know is running inside the session bus:
PID=`pidof gnome-shell`

Then, get the bus address it uses:
cat /proc/$PID/environ|tr '\0' '\n'|grep DBUS_SESSION_BUS_ADDRESS

You can check if it is the same as given by your script.

Are you using notify-send in a persistent screen(1) after the session
is terminated?

Alban