Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1336102 - [abrt] yumex-dnf: __init__.py:1100:on_history_undo:AttributeError: 'Window' object has no attribute 'process_actions'
Summary: [abrt] yumex-dnf: __init__.py:1100:on_history_undo:AttributeError: 'Window' o...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex-dnf
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Björn 'besser82' Esser
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:31f2bee70d8b6932ae4846d9b9a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-14 08:36 UTC by seeker_moc
Modified: 2017-08-08 14:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 14:31:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (583 bytes, text/plain)
2016-05-14 08:36 UTC, seeker_moc
no flags Details
File: environ (1.49 KB, text/plain)
2016-05-14 08:36 UTC, seeker_moc
no flags Details

Description seeker_moc 2016-05-14 08:36:21 UTC
Description of problem:
Tried to undo package install from history

Version-Release number of selected component:
yumex-dnf-4.3.3-1.fc24

Additional info:
reporter:       libreport-2.7.0
cmdline:        /usr/bin/python3 /usr/bin/yumex-dnf
executable:     /usr/bin/yumex-dnf
kernel:         4.5.4-300.local.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor:     Fedora Project
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
__init__.py:1100:on_history_undo:AttributeError: 'Window' object has no attribute 'process_actions'

Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/yumex/__init__.py", line 1100, in on_history_undo
    self.process_actions(from_queue=False)
AttributeError: 'Window' object has no attribute 'process_actions'

Local variables in innermost frame:
messages: ['Undoing transaction 45']
widget: <Gtk.Button object at 0x7f9a7c729b40 (GtkButton at 0x55f326f5b1b0)>
self: <yumex.Window object at 0x7f9a6a3c7c18 (yumex+Window at 0x55f32695e350)>
rc: True
tid: 45

Comment 1 seeker_moc 2016-05-14 08:36:25 UTC
Created attachment 1157462 [details]
File: backtrace

Comment 2 seeker_moc 2016-05-14 08:36:26 UTC
Created attachment 1157463 [details]
File: environ

Comment 3 Christian Stadelmann 2016-05-23 11:45:01 UTC
Fixed by this commit: https://github.com/timlau/yumex-dnf/commit/d86a89f02bcc74f56ac1f6fe93bb4a1d260d2d4c

Comment 4 Christian Stadelmann 2016-05-23 18:13:14 UTC
Similar problem has been detected:

Steps to reproduce:
1. open yumex-dnf
2. select any package for installation, e.g. python3-pylint-gui
3. press "run" button
4. confirm transaction
5. enter your password and confirm

What happens:
Crash on backend, error dialog shows up, transaction is aborted.

What should happen:
No crash. Transaction should be run.

Additional info:
Error message from yumex-dnf error dialog:

20:10:46: EXCEPTION : g-io-error-quark: GDBus.Error:org.freedesktop.DBus.Python.AttributeError: Traceback (most recent call last):
  File "/usr/lib64/python3.5/site-packages/dbus/service.py", line 707, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/python3.5/site-packages/dnfdaemon/server/__init__.py", line 83, in newFunc
    rc = func(*args, **kwargs)
  File "/usr/share/dnfdaemon/dnfdaemon-system", line 537, in RunTransaction
    result = self.run_transaction()
  File "/usr/lib/python3.5/site-packages/dnfdaemon/server/__init__.py", line 550, in run_transaction
    self._check_gpg_signatures(to_dnl)
  File "/usr/lib/python3.5/site-packages/dnfdaemon/server/__init__.py", line 699, in _check_gpg_signatures
    result, errmsg = self.base.sigCheckPkg(po)
  File "/usr/lib/python3.5/site-packages/dnf/util.py", line 79, in __getattr__
    % (C.__name__, name))
AttributeError: 'Base' object has no attribute 'sigCheckPkg'
 (36)

reporter:       libreport-2.7.0
cmdline:        /usr/bin/python3 /usr/bin/yumex-dnf
event_log:      2016-05-23-20:09:22> (»report_uReport« erfolgreich abgeschlossen)
executable:     /usr/bin/yumex-dnf
kernel:         4.5.4-300.fc24.x86_64
package:        yumex-dnf-4.3.3-1.fc24
pkg_fingerprint: 3D03 BDC6 DD82 F6A5
pkg_vendor:     Fedora Project COPR (timlau/yumex-dnf)
reason:         __init__.py:1100:on_history_undo:AttributeError: 'Window' object has no attribute 'process_actions'
reproducible:   Not sure how to reproduce the problem
runlevel:       N 5
type:           Python3

Comment 5 Christian Stadelmann 2016-05-23 18:18:00 UTC
Please ignore my previous comment (comment #4), it is unrelated. Both issues have the same backtrace in yumex-dnf but different causes. Have a look at bug #1338564 for that.

Comment 6 seeker_moc 2016-05-26 15:29:56 UTC
The original bug was reported through abrt, and occurred when I tried to undo a package install through Yumex-dnf. However, I also receive the same (or at least a very similar) error when trying to install any package through Yumex. I can list, search, and even remove packages, but any attempt to install new packages fails with a (python?) error.

Comment 7 seeker_moc 2016-05-27 20:19:20 UTC
I can confirm that today's update to 4.3.3-1 fixed the package install issue. I'm now able to install new packages through Yumex as expected. However, I'm still unable to undo changes from the history list.

Comment 8 seeker_moc 2016-05-27 20:22:34 UTC
Sorry, my mistake. The update was to the dnfdaemon, not yumex (I just saw something with dnf in the name and wanted to test). However, whether or not it's related, I can install packages using yumex again.

Comment 9 Peter Andreasen 2016-07-14 16:25:59 UTC
*** Bug 1356674 has been marked as a duplicate of this bug. ***

Comment 10 Fedora Admin XMLRPC Client 2017-03-22 10:08:38 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 11 Fedora Admin XMLRPC Client 2017-03-23 18:01:30 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Fedora End Of Life 2017-07-25 20:46:03 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2017-08-08 14:31:04 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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