Bug 895709
| Summary: | [abrt] fedmsg-notify-0.3.2-2.fc18: bus.py:122:__new__:DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, ... | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Duco van Amstel <for_i_am_root> | ||||||||||
| Component: | fedmsg-notify | Assignee: | Luke Macken <lmacken> | ||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 18 | CC: | lmacken, pfrields, rbean | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:16cb8bc07569ec9bc3d7c999b123b3866b707dab | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-02-19 13:23:28 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 679033 [details]
File: backtrace
Created attachment 679034 [details]
File: core_backtrace
Created attachment 679035 [details]
File: environ
Created attachment 679036 [details]
File: smolt_data
Can you please try fedmsg-notify-0.4.0-2.fc18 in updates-testing? https://admin.fedoraproject.org/updates/F18/FEDORA-2013-1261 Sorry for the late return to this bugreport. I had deinstalled the package since. But now after reinstalling it the bug is not reproductible. Closing the bug as it is not reproducible anymore. |
Description of problem: Trying to run fedmsg-notify-config from CLI as root. 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.7.2-201.fc18.x86_64 uid: 0 Truncated backtrace: bus.py:122:__new__:DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/fedmsg_notify/gui.py", line 156, in do_activate win = FedmsgNotifyConfigWindow(self) File "/usr/lib/python2.7/site-packages/fedmsg_notify/gui.py", line 44, in __init__ self.bus = dbus.SessionBus() File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 211, in __new__ mainloop=mainloop) File "/usr/lib/python2.7/site-packages/dbus/_dbus.py", line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Local variables in innermost frame: mainloop: None address_or_type: 0 cls: <class 'dbus._dbus.SessionBus'>