Libnotify and notify-send problems

J_Humphrey · 01-31-2010, 06:00 AM

I installed libnotify using slackbuilds.org, and when I am in screen, I used to be able to `notify-send example` while in screen. But now, I am no longer able to use it. I get this error:

Code:

$ notify-send hello
libnotify-Message: Unable to get session bus: Failed to connect to socket /tmp/dbus-VVqepgiwYi: Connection refused

If I restart screen while in X, I can use notify-send while in screen, but once I restart X, it no longer works. I have "export DISPLAY=:0" in my .zshrc. I've googled around for this problem, but I've been unable to find a solution. "export DISPLAY=:0" worked for a while, but for some reason, it no longer works.

Thanks

ozanbaba · 01-31-2010, 06:20 AM

i came around something like this:http://ubuntuforums.org/archive/index.php/t-775170.html

basically it gets DBUS session address and uses it. not X's display.

it think it has nothing to do with X but with DBUS itself.

J_Humphrey · 01-31-2010, 03:37 PM

I'm still having trouble. I don't think that init script is getting the PID for dbus, I tried to get it then echo it if it found it instead, and nothing was echoed. when I echo the DBUS variable in screen I get this:

Code:

$ echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-VVqepgiwYi,guid=97a5ab86dfc26459dacd69ef4b64925c

But when I do the same thing in a regular terminal, I get this:

Code:

$ echo $DBUS_SESSION_BUS_ADDRESS
unix:abstract=/tmp/dbus-mH5076K30K,guid=b818f3dee8bf0d0b5295bc834b65f08e

As you can see, they are two different things for the same variable. I've also tried of exporting the one from terminal into the screen variable, but I get this:

Code:

$ export $DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-mH5076K30K,guid=b818f3dee8bf0d0b5295bc834b65f08e'
export: not valid in this context: unix:abstract

What else could it be....

edit: fixed my echo

J_Humphrey · 01-31-2010, 05:00 PM

So, I fixed my export and did this:

Code:

export DBUS_SESSION_BUS_ADDRESS='unix:abstract=/tmp/dbus-mH5076K30K,guid=b818f3dee8bf0d0b5295bc834b65f08e'

and it now works. so how would I automate this process for screen....

grissiom · 01-31-2010, 07:29 PM

What groups are you in? I have no troubles here...

J_Humphrey · 01-31-2010, 11:42 PM

gid=100(users) groups=6(disk),10(wheel),11(floppy),17(audio),18(video),19(cdrom),20(games),83(plugdev),84(power),86 (netdev),100(users)

Old_Fogie · 02-01-2010, 03:36 AM

Did you *only* install libnotify? I'm going to assume that's all you built.

Installing libnotify on it's own won't show a pop-up.

I build:
libsexy
libnotify
exo-notify (from SBo only it's a virtual package - it's a rebuild of xfce's exo but seeing the libnotify package, then the SBo script just put's the relavant binary into a package.)
notification-daemon-xfce

Then using 'notify-send ...' works with a popup. also then the pidgin-libnotify app, xchat (if rebuilt) will work with the toaster pop-ups too.

Also make sure that the /etc/rc.d/rc.messagebus is running.

On kde 3.5 series, I had issues with dbus in kde. The only tweak I found for that was to use dbus-launch exit with session ( I forget the exact command, it's used in the startxfce scripts)

hope this helps.

grissiom · 02-01-2010, 05:38 AM

Quote:

Originally Posted by J_Humphrey

gid=100(users) groups=6(disk),10(wheel),11(floppy),17(audio),18(video),19(cdrom),20(games),83(plugdev),84(power),86 (netdev),100(users)

Mine:

Code:

grissiom daemon disk wheel dialout audio video cdrom messagebus haldaemon plugdev power netdev users

I think you may need to add yourself to messagebus group.

Perceptor · 07-27-2010, 04:43 PM

Add the line

Code:

term xterm

to your ~/.screenrc. I had the same problem and this fixed it.