Bug 1071568

Summary: [abrt] Yumex: misc.py:1018:write:IOError: [Errno 5] Eingabe-/Ausgabefehler
Product: [Fedora] Fedora Reporter: Raphael Groner <projects.rg>
Component: yumexAssignee: Tim Lauridsen <tim.lauridsen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: tim.lauridsen
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-09 04:44:11 UTC Type: Bug
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
backtrace
none
analyzer
none
cmdline
none
environ
none
event_log none

Description Raphael Groner 2014-03-01 19:14:28 UTC 
Description of problem:
Yumex crashed immediately after logged into KDE. The crash was detected by abrt.

Version-Release number of selected component (if applicable):
3.0.14-1

How reproducible:
unsure

Steps to Reproduce:
1. log into KDE
2.
3.

Actual results:
crash

Expected results:
no crash

Additional info:
Comment 1 Raphael Groner 2014-03-01 19:15:54 UTC 
Created attachment 869477 [details]
backtrace
Comment 2 Raphael Groner 2014-03-01 19:17:07 UTC 
Created attachment 869478 [details]
analyzer
Comment 3 Raphael Groner 2014-03-01 19:18:13 UTC 
Created attachment 869479 [details]
cmdline
Comment 4 Raphael Groner 2014-03-01 19:21:30 UTC 
Created attachment 869480 [details]
environ
Comment 5 Raphael Groner 2014-03-01 19:21:51 UTC 
Created attachment 869481 [details]
event_log
Comment 6 Raphael Groner 2014-03-01 19:24:14 UTC 
abrt 2.1.12
kernel 3.13.4-200.fc20.x86_64
yum 3.4.3-137.fc20.noarch
Comment 7 Tim Lauridsen 2014-03-03 05:40:03 UTC 
Does it happen every time or just this time ?
Comment 8 Raphael Groner 2014-03-03 11:48:10 UTC 
I don't know how to reproduce and will watch it for some time cause I do not login newly and often due to suspending and locking only.
Comment 9 Tim Lauridsen 2014-03-03 19:15:37 UTC 
OK, this is an issues seen many times before, and there is many ways it can occours.
It happens when the pipe the yumex gui uses to exchange infomation with the root yumex backend there is doing the package actions.
Sometimes the pipe dies and communication is lost and python makes an IOError 5 when the gui tries to read/write to the pipe.

It is solved in yumex-nextgen there is using a DBus service instead, there is much easier to handle.
Comment 10 Tim Lauridsen 2014-10-04 06:33:50 UTC 

*** This bug has been marked as a duplicate of bug 801860 ***
Comment 11 Tim Lauridsen 2014-10-04 06:34:23 UTC 

*** This bug has been marked as a duplicate of bug 881860 ***
Comment 12 Raphael Groner 2014-10-08 17:30:38 UTC 
(In reply to Tim Lauridsen from comment #11)
> 
> *** This bug has been marked as a duplicate of bug 881860 ***

Was has Yumex to do with JBOSS on RHEL???
Comment 13 Tim Lauridsen 2014-10-09 04:44:11 UTC 
(In reply to Raphael Groner from comment #12)
> (In reply to Tim Lauridsen from comment #11)
> > 
> > *** This bug has been marked as a duplicate of bug 881860 ***
> 
> Was has Yumex to do with JBOSS on RHEL???

Nothing, just a typo, 881860 is the right one, 801860 was the typo

*** This bug has been marked as a duplicate of bug 881860 ***