After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 610880 - lazily initialize the daemon
lazily initialize the daemon
Status: RESOLVED FIXED
Product: libnotify
Classification: Platform
Component: general
git master
Other Linux
: Low enhancement
: ---
Assigned To: William Jon McCann
Depends on:
Blocks:
 
 
Reported: 2010-02-23 21:27 UTC by Martin Pitt
Modified: 2010-07-01 12:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
lazily start the daemon (4.89 KB, patch)
2010-02-23 21:28 UTC, Martin Pitt 		none Details | Review

Description Martin Pitt 2010-02-23 21:27:32 UTC 
Right now, notify_init() causes the daemon to be D-Bus activated already, even if the program that calls it doesn't send an actual notification for a long time (or potentially not at all). In order to optimize startup speed, and avoid needlessly running programs it would be nice if the daemon would be launched on demand, instead of right away.

Thanks for considering!
Comment 1 Martin Pitt 2010-02-23 21:28:45 UTC 
Created attachment 154544 [details] [review]
lazily start the daemon
Comment 2 William Jon McCann 2010-04-02 23:50:41 UTC 
Looks good.  Pushed to master.  Thanks!
Comment 3 Martin Pitt 2010-07-01 12:35:59 UTC 
Sorry, this caused an assertion to be thrown when a process never sends any notification and then uninits. Simple fix, I committed directly:

http://git.gnome.org/browse/libnotify/commit/?id=1a103f1eee373882a7ed5e2225fcd23bb10ecbc8