Bug 827148 - [abrt] yumex-3.0.5-2.fc17: codecs.py:352:write:IOError: [Errno 5] Erreur d'entrée/sortie
Summary: [abrt] yumex-3.0.5-2.fc17: codecs.py:352:write:IOError: [Errno 5] Erreur d'en...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f6524d3e1482bd0f96746026f4c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-31 18:06 UTC by Raphos
Modified: 2012-06-06 12:34 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-06-06 12:34:59 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Raphos 2012-05-31 18:06:26 UTC 
libreport version: 2.0.10
abrt_version:   2.0.10
cmdline:        /usr/bin/python -E /usr/share/yumex/yum_childtask.py 2 True False /etc/yum.conf
executable:     /usr/share/yumex/yum_childtask.py
kernel:         3.3.7-1.fc17.x86_64
time:           jeu. 31 mai 2012 19:42:12 CEST
uid:            0
username:       root

backtrace:
:codecs.py:352:write:IOError: [Errno 5] Erreur d'entrée/sortie
:
:Traceback (most recent call last):
:  File "/usr/share/yumex/yum_childtask.py", line 70, in <module>
:    print err, msg
:  File "/usr/lib64/python2.7/codecs.py", line 352, in write
:    self.stream.write(data)
:IOError: [Errno 5] Erreur d'entrée/sortie
:
:Local variables in innermost frame:
:consumed: 116
:object: u"Verrou /var/run/yum.pid existant\xa0: une autre copie est lanc\xe9e avec le pid 3012.\nL'autre application est : PackageKit"
:data: "Verrou /var/run/yum.pid existant\xc2\xa0: une autre copie est lanc\xc3\xa9e avec le pid 3012.\nL'autre application est : PackageKit"
:self: <open file '<stdout>', mode 'w' at 0x7f90cd28c1e0>

comment:
:Try to use Yumex.
:Idon't know.
Comment 1 Tim Lauridsen 2012-06-06 12:34:59 UTC 
this happens sometimes in python, that your are not able to write to stdout.

This is not something is can fix in yumex :(

I have not been able to reproduce it, but other user have reported the same issue.
Note You need to log in before you can comment on or make changes to this bug.