The fedmsg extension (at least, I think it's the Shell extension) seems extremely chatty in the journald logs. My journalctl output is stuffed with this:
Jun 14 00:33:01 adam.localdomain /etc/gdm/Xsession: [moksha.hub] DEBUG 2013-06-14 00:33:01,309 Message to org.fedoraproject.prod.buildsys.repo.init didn't match filters
Jun 14 00:34:14 adam.localdomain /etc/gdm/Xsession: [moksha.hub] DEBUG 2013-06-14 00:34:14,349 Message to org.fedoraproject.prod.buildsys.build.state.change didn't match filters
i.e. every time a message is emitted by fedmsg that doesn't match the filters for the extension to notify me of it, the fact is logged to the journal. That seems...unnecessary.
The extension only listens to the dbus, and does not handle the moksha hub connection, this is fedmsg itself.
The log message originates from here, making it a part of fedmsg-notify.
Fixed upstream: https://github.com/fedora-infra/fedmsg-notify/commit/dac7abcd45f04fb8d6f31c3312271d7b749e49a8
fedmsg-notify-0.5.1-1.fc19 has been submitted as an update for Fedora 19.
Luke, looks like you accidentally pasted the wrong commit. It is fixed upstream, but in this one: https://github.com/fedora-infra/fedmsg-notify/commit/095adbdaff0d899150cf9e3d4800331c9bfbe4b1
Thanks for fixing!
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fedmsg-notify-0.5.1-1.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
fedmsg-notify-0.5.1-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.