Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 597194 - [abrt] crash in yumex-2.9.7-1.fc13: bus.py:125:__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
Summary: [abrt] crash in yumex-2.9.7-1.fc13: bus.py:125:__new__:DBusException: org.fre...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3e72b2d7
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-28 10:43 UTC by atgf0127
Modified: 2010-06-06 10:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-06 10:14:43 UTC


Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-28 10:43 UTC, atgf0127
no flags Details

Description atgf0127 2010-05-28 10:43:19 UTC
abrt 1.1.0 detected a crash.

architecture: i686
cmdline: /usr/bin/python /usr/share/yumex/yumex.pyc
component: yumex
executable: /usr/share/yumex/yumex.pyc
kernel: 2.6.33.3-85.fc13.i686.PAE
package: yumex-2.9.7-1.fc13
reason: bus.py:125:__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.
release: Fedora release 13 (Goddard)

backtrace
-----
bus.py:125:__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/share/yumex/yumex.py", line 25, in <module>
    from yumexgui import YumexApplication
  File "/usr/lib/python2.6/site-packages/yumexgui/__init__.py", line 34, in <module>
    from yumexgui.gui import Notebook, PackageCache, PackageInfo
  File "/usr/lib/python2.6/site-packages/yumexgui/gui.py", line 28, in <module>
    from yumexbackend.yum_backend import YumexPackageYum
  File "/usr/lib/python2.6/site-packages/yumexbackend/yum_backend.py", line 32, in <module>
    from yumexbackend.yumMediaManagerDeviceKit import MediaManagerDeviceKit as MediaManager
  File "/usr/lib/python2.6/site-packages/yumexbackend/yumMediaManagerDeviceKit.py", line 60, in <module>
    bus = dbus.SystemBus()
  File "/usr/lib/python2.6/site-packages/dbus/_dbus.py", line 202, in __new__
    private=private)
  File "/usr/lib/python2.6/site-packages/dbus/_dbus.py", line 108, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 125, 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: 1
cls: <class 'dbus._dbus.SystemBus'>

Comment 1 atgf0127 2010-05-28 10:43:21 UTC
Created attachment 417565 [details]
File: backtrace

Comment 2 Tim Lauridsen 2010-06-06 10:14:43 UTC
should be fixed in yumex-2.9.8, will hit updates test soon

https://admin.fedoraproject.org/updates/yumex-2.9.8-1.fc13


Note You need to log in before you can comment on or make changes to this bug.