Notifications don't show up (notify-send notify-osd)
Mehturt
mehturt at gmail.com
Tue May 6 09:07:35 PDT 2014
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.
Sorry, how do I know if it's the right daemon? I have some dbus-daemon
running, but the socket is not visible on command line.
> Note that the script you pasted will only set the address for the session bus.
> It doesn't affect the accessibility bus, which your application also found out
> about. The accessibility bus is not part of the D-Bus spec, so we can't help
> you with it, but it might point to your problem. Your environment variables
> may not be properly set up.
Yes, that's what the script is supposed to be for, setting the env
variables properly. What env var do I need to set for the
accessibility bus?
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
$ cat ~/.dbus/session-bus/1256b075bc99dcab8bbcb024522a5607-0
# This file allows processes on the machine with id
1256b075bc99dcab8bbcb024522a5607 using
# display :0 to find the D-Bus session bus with the below address.
# If the DBUS_SESSION_BUS_ADDRESS environment variable is set, it will
# be used rather than this file.
# See "man dbus-launch" for more details.
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-GWnKyuCbfH,guid=d007a02e77281c5071f58d2453676047
DBUS_SESSION_BUS_PID=3173
DBUS_SESSION_BUS_WINDOWID=10485761
So I source that file basically, run notify-osd but I still get the
same error as before (and basically all my programs which use dbus
report errors).
m.
More information about the dbus
mailing list