Bug 879325

Summary: [abrt] yumex-3.0.9-1.fc17: misc.py:1033:write:IOError: [Errno 5] Input/output error
Product: [Fedora] Fedora Reporter: mukubya habbert <mukubyaherbert7>
Component: yumexAssignee: Tim Lauridsen <tim.lauridsen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: awilliam, lucky0106, moez.roy, psummitt, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1d14de2bdef631e6fba11246fbc6ee33f51c8154
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 12:34:53 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: executable
none
File: environ
none
File: dso_list
none
File: smolt_data
none
File: core_backtrace none

Description mukubya habbert 2012-11-22 15:42:25 UTC 
Version-Release number of selected component:
yumex-3.0.9-1.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
cmdline:        /usr/bin/python -E /usr/share/yumex/yum_childtask.py 2 True False /etc/yum.conf
kernel:         3.6.6-1.fc17.x86_64

backtrace:
:misc.py:1033:write:IOError: [Errno 5] Input/output error
:
:Traceback (most recent call last):
:  File "/usr/share/yumex/yum_childtask.py", line 70, in <module>
:    print err, msg
:  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1033, in write
:    self.stream.write(s)
:IOError: [Errno 5] Input/output error
:
:Local variables in innermost frame:
:s: 'Existing lock /var/run/yum.pid: another copy is running as pid 1617.\n  The other application is: yum_childtask.p'
:self: <open file '<stdout>', mode 'w' at 0x7ff3316e41e0>
Comment 1 mukubya habbert 2012-11-22 15:42:31 UTC 
Created attachment 649887 [details]
File: executable
Comment 2 mukubya habbert 2012-11-22 15:42:34 UTC 
Created attachment 649888 [details]
File: environ
Comment 3 mukubya habbert 2012-11-22 15:42:41 UTC 
Created attachment 649891 [details]
File: dso_list
Comment 4 mukubya habbert 2012-11-22 15:42:47 UTC 
Created attachment 649892 [details]
File: smolt_data
Comment 5 mukubya habbert 2012-11-22 15:42:53 UTC 
Created attachment 649893 [details]
File: core_backtrace
Comment 6 Moez Roy 2013-01-08 16:11:52 UTC 
happened on Fedora 18 also
Comment 7 Moez Roy 2013-01-12 08:00:40 UTC 
Can some one please change this from F17 to F18.

Thanks.
Comment 8 Fedora End Of Life 2013-07-04 04:03:54 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 lucky0106 2013-07-08 15:12:00 UTC 
I have also experienced this bug (on Fedora 18).
Comment 10 Fedora End Of Life 2013-08-01 12:34:57 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 11 Paul M. Summitt 2013-11-26 16:54:32 UTC 
I, too, am running Fedora 18 and have experienced this bug several times.