Bug 1573030

Summary: [abrt] yumex-dnf: module(): __init__.py:192:<module>:GLib.GError: g-io-error-quark: La conexión está cerrada (18)
Product: [Fedora] Fedora Reporter: Yonatan <yonatan.el.amigo>
Component: yumex-dnfAssignee: Björn 'besser82' Esser <besser82>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: besser82
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e63827251d2b836308066f96b2ad10c090a4a992
Whiteboard: abrt_hash:da7c49ef81b94927d7f381231493ab601d37c612;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:19:09 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:
Description Flags
File: backtrace
none
File: cgroup
none
File: cpuinfo
none
File: environ
none
File: mountinfo
none
File: namespaces
none
File: open_fds none

Description Yonatan 2018-04-29 22:32:05 UTC
Version-Release number of selected component:
yumex-dnf-4.3.3-4.1.fc26

Additional info:
reporter:       libreport-2.9.3
cmdline:        /usr/bin/python3 /usr/bin/yumex-dnf
crash_function: module
exception_type: GLib.GError
executable:     /usr/bin/yumex-dnf
kernel:         4.13.11-200.fc26.i686+PAE
runlevel:       N 5
type:           Python3
uid:            0

Truncated backtrace:
#1 <module> in /usr/lib/python3.6/site-packages/dnfdaemon/client/__init__.py:192
#2 <module> in /usr/lib/python3.6/site-packages/yumex/misc.py:27
#3 <module> in /usr/lib/python3.6/site-packages/yumex/__init__.py:24
#4 <module> in /usr/bin/yumex-dnf:37

Comment 1 Yonatan 2018-04-29 22:32:10 UTC
Created attachment 1428600 [details]
File: backtrace

Comment 2 Yonatan 2018-04-29 22:32:11 UTC
Created attachment 1428601 [details]
File: cgroup

Comment 3 Yonatan 2018-04-29 22:32:12 UTC
Created attachment 1428602 [details]
File: cpuinfo

Comment 4 Yonatan 2018-04-29 22:32:13 UTC
Created attachment 1428603 [details]
File: environ

Comment 5 Yonatan 2018-04-29 22:32:14 UTC
Created attachment 1428604 [details]
File: mountinfo

Comment 6 Yonatan 2018-04-29 22:32:16 UTC
Created attachment 1428605 [details]
File: namespaces

Comment 7 Yonatan 2018-04-29 22:32:17 UTC
Created attachment 1428606 [details]
File: open_fds

Comment 8 Fedora End Of Life 2018-05-03 07:50:20 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 9 Fedora End Of Life 2018-05-29 11:19:09 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.