dbus-daemon[599]: [system] Activating via systemd: service name='net.reactivated.Fprint' dbus-daemon[599]: [system] Successfully activated service 'net.reactivated.Fprint' Note services like Fprint de-activate themselves after a few seconds being idle, as well as activating on-demand. There are too many of these messages to warrant being "highlighted" in high-intensity white in the system log (journalctl). Please reduce the loglevel to lower than NOTICE. E.g. systemd does not log a NOTICE for every single system service it starts, it uses the INFO level for these messages. The other highlighted messages I see journalctl are mainly warnings, and big events like the start of a system clock adjustment, initial kernel boot message, switching from initramfs to the root filesystem. Starting FPrintd does not count as a big event, when it will be stopped again 30 seconds later :). Version: dbus-1.11.16-1.fc26.x86_64
Commit 69ed32cbccbec9d613447cb64e9d7b1ffa11ce3c "Add syslog of security denials and configuration file reloads" added _dbus_log_info(), which inexplicably used LOG_NOTICE rather than LOG_INFO. NOTICE perhaps made sense for the original use-case (configuration file reloads) but I'm not sure why the mismatched name. Using LOG_INFO for DBUS_SYSTEM_LOG_INFO makes a lot of sense to me.
Created attachment 134442 [details] [review] unix: Reduce log level for DBUS_SYSTEM_LOG_INFO to LOG_INFO This is a better match for the way we use it in practice.
Comment on attachment 134442 [details] [review] unix: Reduce log level for DBUS_SYSTEM_LOG_INFO to LOG_INFO Review of attachment 134442 [details] [review]: ----------------------------------------------------------------- ++
Thanks, fixed in git for 1.11.18.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.