Hi, Since https://bugs.freedesktop.org/show_bug.cgi?id=68559 the session bus will now cause launched services to be connected to the systemd journal (on systemd-based systems). Before this, output went to /dev/null.
As you might imagine, over time various components spewed (basically debugging) log messages that were just ignored except when developers invoked the binary by hand. Now, I read the journal *a lot*. I'd really appreciate it (and administrators will too) if we just were...quieter. When things are normal. Some example patches: libfprint: https://bugs.freedesktop.org/show_bug.cgi?id=71889 e-d-s: https://bugzilla.gnome.org/show_bug.cgi?id=712829 g-o-a: https://bugzilla.gnome.org/show_bug.cgi?id=712843 tracker: https://bugzilla.gnome.org/show_bug.cgi?id=712813 Do you maintain a DBus session service? If so, please just take a quick look at the output of "journalctl -b", and do your part to trim unnecessary log messages. Thanks! _______________________________________________ desktop-devel-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/desktop-devel-list
