Hi, Thanks for the bug report. notify-osd will not start if another instance exists. The error (core) is managed in another bug report btw.
In the case of e17 or Xubuntu or other desktops where we know the message indicator may be absent, we're letting the old notification- daemon run, as a principle. When we'll know that another desktop supports the message indicator or other changes related to notify-osd, we'll consider turning it on by defaut. If your running a custom version of e17 + gnome, i suggest you look in the startup file in: /usr/share/dbus-1/services/org.freedesktop.Notifications.service -- notify-osd cannot currently be used in a non-gnome-session environment https://bugs.launchpad.net/bugs/334778 You received this bug notification because you are a member of Notify OSD Developers, which is subscribed to Notify OSD. Status in Notify OSD: New Bug description: I'm using e17 and some elements from gnome. No other notification daemon is running. When I try to start notify-osd however, I get this error: ** (notify-osd:10384): WARNING **: Another instance has already registered org.freedesktop.Notifications ** ERROR **: Could not register instance aborting... /bin/bash: line 1: 10384 Trace/breakpoint trap (core dumped) /usr/lib/notify-osd/notify-osd _______________________________________________ Mailing list: https://launchpad.net/~dx-team Post to : [email protected] Unsubscribe : https://launchpad.net/~dx-team More help : https://help.launchpad.net/ListHelp
