it seems that the trend in notification daemons is to start using freedesktop.org autostart (/etc/xdg/autostart and .config/autostart) so people can more easily chose which notification daemon should be started, and by default use what the environment wants (right now there's a race at dbus activation time if multiple daemons are installed).
I was asked to change the way xfce4-notifyd starts (http://bugs.debian.org/640082) but it's really your call, so reporting :)
I'm personnaly opposed to this. It means the daemon has to be running all the time : the main advantage of dbus activation was that you don't keep useless things running and that you can load them on-demand.
I don't see what benefit we would gain from this. I don't really care about people who want to have several notification services installed if I need to damage the overall experience for that.
I'm ready to discuss this though but you'll have to convince me.
(In reply to comment #1)
> I'm personnaly opposed to this. It means the daemon has to be running all the
> time : the main advantage of dbus activation was that you don't keep useless
> things running and that you can load them on-demand.
> I don't see what benefit we would gain from this. I don't really care about
> people who want to have several notification services installed if I need to
> damage the overall experience for that.
Afaiui it's a trend leaded by GNOME 3 and KDE.
> I'm ready to discuss this though but you'll have to convince me.
In fact the easiest might be to join the mail conversation from the Debian bug (you can just mail email@example.com with me and Michael Biebl on CC: (and you can even get an mbox with all the messages to the bug if you want an easy reply).
I'd argue DBus is broken -- there's no way to arbitrate between different services that register to provide the same bus name.
Agreed with Jerome that it's nice to be able to allow the notifications daemon to gracefully quit when it hasn't seen a notification in a while, and automatically get started up again on demand. You also speed up desktop startup doing it this way, since you don't have to start it immediately on login.
Now, you could certainly argue that a notifications daemon is pretty lightweight, so running it all the time shouldn't be a big deal... but then you start making that argument for every other transient daemon too, and it adds up.
It looks like xfce4-notifyd has a resident size of almost 10MB, which isn't bad, but it's just one more thing the system has to reason about when it's considering swapping things in and out.
I dunno. I've considered the lack of a true 'registration mechanism' for handling conflicts between bus names to be a really poor design decision in DBus-land. I'd rather see this fixed at a lower level, sorta how you have file associations in a file manager. You may have 4 apps installed that claim to handle PDF files, but the user can usually set a preference. For DBus stuff, obviously most of these choices should be hidden from the user, but the mechanism should at least exist!
I'm closing this as "won't fix", I don't see any advantage for Xfce users.
The "advantage" is that if another desktop is installed on the same system (e.g. multiple users with different preferred desktops), then each desktop will get its own Notifications daemon. Otherwise, a race condition can result with undefined results.
Most other desktops have come to this realization, and use autostart for this reason. Instead of distributors having to carry this patch, we would prefer to see it upstream.
I'm attaching patches for git master as of today which implements this change.
Created attachment 6334
Launch with autostart instead of D-Bus activation
Created attachment 6335
Do not exit on idle