Version-Release number of selected component: fedmsg-notify-0.3.2-2.fc18 Additional info: cmdline: /usr/bin/python /usr/bin/fedmsg-notify-config dso_list: dbus-python-1.1.1-1.fc18.x86_64 executable: /usr/bin/fedmsg-notify-config kernel: 3.6.10-4.fc18.x86_64 uid: 1001 Truncated backtrace: connection.py:651:call_blocking:DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.218 was not provided by any .service files Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/fedmsg_notify/gui.py", line 107, in activate_cb self.toggle_service(button.get_active()) File "/usr/lib/python2.7/site-packages/fedmsg_notify/gui.py", line 125, in toggle_service notify_iface.Enable() File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking message, timeout) DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.218 was not provided by any .service files Local variables in innermost frame: byte_arrays: False self: <dbus._dbus.SessionBus (session) at 0x7fe8a51f2230> args: () object_path: '/org/fedoraproject/fedmsg/notify' signature: None bus_name: dbus.UTF8String(':1.218') get_args_opts: {'byte_arrays': False, 'utf8_strings': False} timeout: -1.0 kwargs: {} dbus_interface: 'org.fedoraproject.fedmsg.notify' message: <dbus.lowlevel.MethodCallMessage path: /org/fedoraproject/fedmsg/notify, iface: org.fedoraproject.fedmsg.notify, member: Enable dest: :1.218> method: 'Enable'
Created attachment 680091 [details] File: backtrace
Created attachment 680092 [details] File: core_backtrace
Created attachment 680093 [details] File: environ
Can you please try fedmsg-notify-0.4.0-2.fc18 in updates-testing? https://admin.fedoraproject.org/updates/F18/FEDORA-2013-1261
I installed it. So far no problems. How long should I test it?
Can we close this one?
It should be all good now, thanks for testing. Re-open if you hit the problem again, but if it seems to be working now then it should be fine.