notify_desktop plugin fails to initialize libnotify1. shambhala:~> tail -4 /var/log/syslog Jun 15 12:04:34 shambhala collectd[21814]: notify_desktop: Failed to initialize libnotify. Jun 15 12:04:34 shambhala collectd[21814]: Initialization of plugin `notify_desktop' failed with status -1. Plugin will be unloaded. Jun 15 12:04:34 shambhala collectd[21814]: plugin_unregister_read: No such read function: notify_desktop Jun 15 12:04:34 shambhala collectd[21814]: Initialization complete, entering read-loop. I tried with and without configuring notify_desktop plugin. I am using KDE 4.4.4.
Hi again, Do you have some kind of notification daemon installed? See, e.g., the "notification-daemon" package -- I'm sure, KDE provides something similar. Afaik, the only requirement is that the daemon has to comply with the "Desktop Notification Specification" [1]. Anyway, that error message should definitely be more verbose. HTH, Sebastian [1] <http://www.galago-project.org/specs/notification/>
Am Dienstag 15 Juni 2010 schrieben Sie: Hi, I seem to have one installed: shambhala:~> apt-show-versions | grep notification-daemon notification-daemon/squeeze uptodate 0.4.0-2 But I am not sure whether it got started. I have knotify4 running but whether that is compliant to the "Desktop Notification Specification" I do not know. shambhala:~> ps aux | grep notif | grep -v grep root 100 0.0 0.0 0 0 ? S May31 0:00 [kacpi_notify] martin 26944 0.0 0.5 175648 11768 ? Sl Jun14 0:08 /usr/bin/knotify4 AFAIR there might be some work underway regarding this for KDE 4.5, but I am not sure about this. Same question as for debian bug #585975. Close and report upstream or retitle here? Ciao,
Hi, Despite the name, this is not a daemon running in the background at all the times but rather some sort of plugin (or something like that) called by dbus. 'notify-send' (available in the "libnotify-bin" package) should basically do the same. I just did a quick test, but that does not seem to work either. However, I do not have the time to dig into that any further right now :-/ of it in the Debian BTS ;-) Also, given the above, this might also be a bug in libnotify, in which case this bug should be cloned and reassigned to libnotify. Do you have time to have a closer look at that? TIA, Sebastian