Bug 1199242
| Summary: | [abrt] fros: bus.py:122:__new__:dbus.exceptions.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 ... | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||||
| Component: | fros | Assignee: | Jakub Filak <jfilak> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 22 | CC: | awilliam, jberan, jfilak, jfrieben, lnie | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/f90b75126002ecff600c5831fb48967bdbdc063a | ||||||||
| Whiteboard: | abrt_hash:1d83cf9c05fb48a6c01c14bed6b86017f06cc0d9 | ||||||||
| Fixed In Version: | 1.1-2.fc22 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-09-24 08:27:11 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 998495 [details]
File: backtrace
Created attachment 998496 [details]
File: environ
confirmed this.I ran into this bug when I'm trying to report another crash bug using gnome-abrt Patch submitted for review to upstream: https://github.com/jfilak/fros/commit/727d4e349409d5b45903faa169662cdeff381903 fros-1.1-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-14188 fros-1.1-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update fros'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14188 fros-1.1-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Testing anaconda crash report submission from a live image. Version-Release number of selected component: fros-1.1-1.fc22 Additional info: reporter: libreport-2.4.0 cmdline: /usr/bin/python3 /usr/bin/fros --is-available executable: /usr/bin/fros kernel: 4.0.0-0.rc1.git0.1.fc22.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: bus.py:122:__new__:dbus.exceptions.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/bin/fros", line 81, in <module> available_plugins = load_plugins() File "/usr/bin/fros", line 61, in load_plugins plugin_instance = value.getScreencastPluginInstance() File "/usr/lib/python3.4/site-packages/pyfros/plugins/screencastgnome.py", line 115, in getScreencastPluginInstance return ScreencastGnome() File "/usr/lib/python3.4/site-packages/pyfros/plugins/screencastgnome.py", line 123, in __init__ bus = dbus.SessionBus() File "/usr/lib64/python3.4/site-packages/dbus/_dbus.py", line 211, in __new__ mainloop=mainloop) File "/usr/lib64/python3.4/site-packages/dbus/_dbus.py", line 100, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib64/python3.4/site-packages/dbus/bus.py", line 122, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.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'>