Red Hat Bugzilla – Bug 1312851
[abrt] yumex-dnf: status.py:139:handle_dbus_signals:AttributeError: 'NoneType' object has no attribute 'on_status_icon_clicked'
Last modified: 2016-03-22 08:59:24 EDT
Description of problem:
I launched yumex-dnf and it did not show any updates available. I know there should be some updates available because I'd seen them the other day. I closed the window and launched yumex-dnf again. It presented me a message dialog telling that yumex-dnf is already running and whether I want to quit. I chose "Yes" and it quit, nothing more happened. I lanuched it again and when asked whether I want to quit I chose "No" this time. It reported a crash, that's all.
Now when I was writing this comment I saw another message dialog telling that yumex-dnf could not refresh the cache. The only option was to close that dialog box and when I closed it it crashed again. So I have another crash report waiting in a queue, although I don't yet know if I would report it.
Version-Release number of selected component:
cmdline: /usr/bin/python3 -tt /usr/bin/yumex-dnf
runlevel: N 5
status.py:139:handle_dbus_signals:AttributeError: 'NoneType' object has no attribute 'on_status_icon_clicked'
Traceback (most recent call last):
File "/usr/lib/python3.4/site-packages/yumex/status.py", line 73, in __call__
return getattr(self.proxy, self.method)(*args)
File "/usr/lib/python3.4/site-packages/yumex/status.py", line 127, in _on_g_signal
self.handle_dbus_signals(proxy, sender, signal, args)
File "/usr/lib/python3.4/site-packages/yumex/status.py", line 139, in handle_dbus_signals
AttributeError: 'NoneType' object has no attribute 'on_status_icon_clicked'
Local variables in innermost frame:
proxy: <DBusProxy object at 0x7f03ebbba558 (GDBusProxy at 0x25481c0)>
self: <yumex.status.StatusIcon object at 0x7f03ebbb96a0>
Potential duplicate: bug 1277714
Created attachment 1131510 [details]
Created attachment 1131511 [details]
Indeed, it looks like a duplicate of bug 1277714 which is a duplicate of bug 1269400. In bug 1269400 comment 12 you said that an update has been pushed to the Fedora 22 testing repository: https://bodhi.fedoraproject.org/updates/FEDORA-2015-8054ed53d3 but it has been residing in testing for 3 months already and has not been pushed to stable so this is the reason why it still could happen to me. I have not tested this update but I guess it's OK to push it to stable.
Closing as yumex-dnf-4.1.5-1.fc22 from https://bodhi.fedoraproject.org/updates/FEDORA-2015-8054ed53d3 has been pushed to stable.
*** This bug has been marked as a duplicate of bug 1269400 ***