no output from notify-send

antis · 2008-12-30 12:03:54

I don't know if it's the latest upgrade of the notification-daemon that caused this but I can't get notify-send to show me anything anymore.
Does anyone know how to track down the problem? notify-send doesnt seem to have alot of verbose switches to use and I can't find any logs.

Also, are you supposed to be able to run the notification-daemon executable?
If i run /usr/lib/notification-daemon/notification-daemon I get the following error:

GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed
aborting...
Aborted

Am I missing something maybe...?

antis · 2009-01-01 12:18:02

Ok, so I understand that noone else is having this problem

This is what I've done so far:
* Re-installed dbus, notification-daemon and libnotify (didn't help).
* Created a test user to see if notify-send works there (it doesn't).
* Made sure that the display envirnoment variable is set (it is).

If anyone has a good idea how to track down the problem I'd be greatful. All I need is an error message or some sort of feedback from the system.

Oxyd · 2009-01-01 13:34:24

I never had this problem, even though I've seen lots of simillar Glib error messages that did not cause the application to abort.

But you can try running the daemon through strace and gdb. Rebuild it with debugging symbols for better debugging. Perhaps that will give you an idea about what it is that is failing.

You could also try looking at notification-daemon's dependencies and reinstall them -- it could be some sort of incompatibility issue. Also, downgrading to a previous version of notification-daemon may be worth a shot.

Last edited by Oxyd (2009-01-01 13:34:55)

antis · 2009-01-01 15:11:33

Thanks for your answer Oxyd. I did what you suggested and re-installed all dependencies but that didn't help either.
As I didn't have the previous version in my pacman cache I downloaded the pkgbuild and build it myself.

Now when I downgraded from verision 0.4.0 to 0.3.7 everything works again. Very strange. Maybe there are some new dependencies for 0.4.0 that I am missing...
I think I'll take a look at that when I get som time left over. It's aways nice to be able to run the latest packages.

badboy · 2009-01-02 12:06:17

same problem here.
notification-daemon-0.3.7-3 works
notification-daemon-0.4.0-1 doesn't work

edit: I created a bug report

Last edited by badboy (2009-01-02 12:17:13)

Dieter@be · 2009-01-02 19:30:24

fwiw: yes, the daemon _must_ be running, otherwise you won't see notifications

badboy · 2009-01-02 20:06:45

the daemon was running and I'm sure that I restarted it after the update, but it didn't work.
Today I did the same thing (update to latest version and restart dbus-daemon) and now it works

archspeps · 2009-01-03 03:36:38

Same problem here with notification-daemon package version 0.4.0-1 on Arch64.

fwojciec · 2009-01-03 04:07:34

Does rebuilding using abs make it work?

antis · 2009-01-03 09:08:07

No, rebuilding 0.4.0 does not help, not here anyway. I just tried to rebuild package 0.4.0 but no go. 0.3.7 works...

In the bug report (which is now closed) it says that the "dbus session bus" must be running. How do I determine that it is running properly? If it is not running, why does it stop as soon as I try installing 0.4.0 of the notification-daemon? And why does it start working when I install 0.3.7 again?

I'm using slim and openbox with a minimum of libraries installed. Surely I must be missing something on my system that is causing the daemon to fail...

Last edited by antis (2009-01-03 09:10:40)

badboy · 2009-01-03 12:51:56

oh...weird. it stopped working today. I just re-installted 0.3.7, because I don't want to mess with this broken package and I don't have time to find out, why it is broken.

roylez · 2009-01-13 03:08:44

I have exactly the same problem. I am using fluxbox and gdm.

According to http://bugs.archlinux.org/task/12639, the bug is closed. But my problem is still there. I use gdm, so I really doubt it is caused by dbus session.

Comment by Jan de Groot (JGC) - Friday, 02 January 2009, 10:42 GMT-5
/etc/rc.d/dbus is not the dbus session bus. The session bus is the one launched by dbus-launched from whatever you use to start X (gdm starts it by default).

junminh · 2009-01-13 07:35:41

same problem here! 0.3.7 works good. but 0.4.0 not.

i followed this guide http://trac.galago-project.org/wiki/InstallingGalago to ensure what i should have done beofre i run notify-send.
anyway, no good result. problem continues..

junminh · 2009-01-14 07:49:02

solved.

you guys have to install gstreamer0.10-good

or

add flag --enable-sound=no to the compile configuration

i have sent a patch to maitainer, hope it can be acepted and updated soon.

badboy · 2009-01-14 12:50:25

hm, okay, i will try it

Arch Linux

#1 2008-12-30 12:03:54

no output from notify-send

#2 2009-01-01 12:18:02

Re: no output from notify-send

#3 2009-01-01 13:34:24

Re: no output from notify-send

#4 2009-01-01 15:11:33

Re: no output from notify-send

#5 2009-01-02 12:06:17

Re: no output from notify-send

#6 2009-01-02 19:30:24

Re: no output from notify-send

#7 2009-01-02 20:06:45

Re: no output from notify-send

#8 2009-01-03 03:36:38

Re: no output from notify-send

#9 2009-01-03 04:07:34

Re: no output from notify-send

#10 2009-01-03 09:08:07

Re: no output from notify-send

#11 2009-01-03 12:51:56

Re: no output from notify-send

#12 2009-01-13 03:08:44

Re: no output from notify-send

#13 2009-01-13 07:35:41

Re: no output from notify-send

#14 2009-01-14 07:49:02

Re: no output from notify-send

#15 2009-01-14 12:50:25

Re: no output from notify-send

Board footer