Bug 655160 - [abrt] yumex-3.0.0-2.fc14: yumex-yum-backend:28:dispatcher:IOError: [Errno 5] Input/output error
Summary: [abrt] yumex-3.0.0-2.fc14: yumex-yum-backend:28:dispatcher:IOError: [Errno 5]...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: yumex
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Tim Lauridsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5bcf3270
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-19 18:39 UTC by Al Pantilimon
Modified: 2010-11-22 19:55 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-21 11:37:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (381 bytes, text/plain)
2010-11-19 18:39 UTC, Al Pantilimon
no flags Details

Description Al Pantilimon 2010-11-19 18:39:34 UTC
abrt version: 1.1.13
architecture: x86_64
cmdline: /usr/bin/python -E /usr/share/yumex/yumex-yum-backend 2 True False /etc/yum.conf skype;livna;google;fedora;rpmfusion-free-updates;rpmfusion-nonfree-updates;rpmfusion-free;adobe-linux-i386;updates;rpmfusion-nonfree
component: yumex
executable: /usr/share/yumex/yumex-yum-backend
kernel: 2.6.35.6-48.fc14.x86_64
package: yumex-3.0.0-2.fc14
reason: yumex-yum-backend:28:dispatcher:IOError: [Errno 5] Input/output error
release: Fedora release 14 (Laughlin)
time: 1290188140
uid: 0

backtrace
-----
yumex-yum-backend:28:dispatcher:IOError: [Errno 5] Input/output error

Traceback (most recent call last):
  File "/usr/share/yumex/yumex-yum-backend", line 50, in <module>
    rc = dispatcher()
  File "/usr/share/yumex/yumex-yum-backend", line 28, in dispatcher
    line = sys.stdin.readline().strip('\n')
IOError: [Errno 5] Input/output error

Local variables in innermost frame:

How to reproduce
-----
1. update yumex with yumex
2. launch yumex
3. crash yumex

Comment 1 Al Pantilimon 2010-11-19 18:39:37 UTC
Created attachment 461621 [details]
File: backtrace

Comment 2 Tim Lauridsen 2010-11-20 06:26:45 UTC
please try running 'yumex -d' and paste the output

Comment 3 Al Pantilimon 2010-11-20 23:49:19 UTC
/usr/bin/yumex -d --root &


00:45:12 : DEBUG - Current Yumex Settings:
00:45:12 : DEBUG -     autorefresh: True
00:45:12 : DEBUG -     branding_title: 'Yum Extender'
00:45:12 : DEBUG -     bugzilla_url: 'https://bugzilla.redhat.com/show_bug.cgi?id='
00:45:12 : DEBUG -     color_install: 'darkgreen'
00:45:12 : DEBUG -     color_normal: 'black'
00:45:12 : DEBUG -     color_obsolete: 'blue'
00:45:12 : DEBUG -     color_update: 'red'
00:45:12 : DEBUG -     debug: True
00:45:12 : DEBUG -     disable_netcheck: True
00:45:12 : DEBUG -     disable_repo_page: False
00:45:12 : DEBUG -     history_limit: 15
00:45:12 : DEBUG -     plugins: True
00:45:12 : DEBUG -     proxy: ''
00:45:12 : DEBUG -     recentdays: 14
00:45:12 : DEBUG -     repo_exclude: ['debug', 'source']
00:45:12 : DEBUG -     typeahead_search: True
00:45:12 : DEBUG -     use_sortable_view: True
00:45:12 : DEBUG -     win_height: 817
00:45:12 : DEBUG -     win_sep: 300
00:45:12 : DEBUG -     win_width: 1429
00:45:12 : DEBUG -     yum_conf: '/etc/yum.conf'
00:45:12 : DEBUG -     yumdebuglevel: 2
/usr/lib/python2.7/site-packages/guihelpers/__init__.py:257: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
  self.add_from_file(filename)
00:45:12 : INFO - network connection state check is disabled
00:45:12 : DEBUG - Getting package lists - BEGIN   <yumexgui.populate_package_cache>
00:45:12 : INFO - Starting yum child process
00:45:12 : DEBUG - Initialize yum backend - BEGIN   <yum_backend.setup>
00:45:12 : DEBUG - Setup START   <yum_backend.setup>
00:45:12 : INFO - Client is running in rootmode, starting backend launcher directly
00:45:12 : DEBUG - Command to run : /usr/share/yumex/yum_childtask.py 2 True False /etc/yum.conf   <yum_backend.setup>
00:45:12 : DEBUG - LAUNCHER: Ready for commands   <yum_backend._check_for_message>
00:45:12 : DEBUG - Sending: #run args: ['UycvdXNyL3NoYXJlL3l1bWV4L3l1bV9jaGlsZHRhc2sucHkgMiBUcnVlIEZhbHNlIC9ldGMveXVtLmNvbmYnCnAwCi4=']   <yum_backend._send_command>
00:45:12 : DEBUG - Setup END   <yum_backend.setup>
00:45:12 : DEBUG - LAUNCHER - Starting : /usr/share/yumex/yum_childtask.py 2 True False /etc/yum.conf   <yum_backend._check_for_message>
00:45:12 : DEBUG - Using yum debuglevel = 2   <yum_backend._check_for_message>
00:45:13 : INFO - YUM: Loaded plugins: fastestmirror, presto, remove-with-leaves, rpm-warm-cache
00:45:13 : DEBUG - Initialize yum backend - END   <yum_backend.setup>
00:45:13 : DEBUG - Getting package lists - END   <yumexgui.populate_package_cache>
00:45:13 : DEBUG - Sending: get-repos args: []   <yum_backend._send_command>
00:45:13 : DEBUG - START: Getting updates packages   <yumexgui.on_packageFilter_changed>
00:45:13 : DEBUG - get-repos Args: ['']  took 0.00 s to complete   <yumexbackend.yum_server>
00:45:13 : DEBUG - Sending: get-packages args: ['updates', 'False']   <yum_backend._send_command>
00:45:13 : INFO - Getting available updates
00:45:14 : INFO - YUM: Loading mirror speeds from cached hostfile
00:45:14 : INFO - YUM:  * fedora: ftp.halifax.rwth-aachen.de
00:45:14 : INFO - YUM:  * livna: rpm.livna.org
00:45:14 : INFO - YUM:  * rpmfusion-free: ftp-stud.hs-esslingen.de
00:45:14 : INFO - YUM:  * rpmfusion-free-updates: ftp-stud.hs-esslingen.de
00:45:14 : INFO - YUM:  * rpmfusion-nonfree: ftp-stud.hs-esslingen.de
00:45:14 : INFO - YUM:  * rpmfusion-nonfree-updates: ftp-stud.hs-esslingen.de
00:45:14 : INFO - YUM:  * updates: ftp.uni-siegen.de
00:45:15 : DEBUG - got 0 packages from yum backend   <yum_backend.get_packages>
00:45:15 : INFO - 0 packages returned
00:45:15 : DEBUG - get-packages Args: ['updates', 'False']  took 2.40 s to complete   <yumexbackend.yum_server>
00:45:15 : DEBUG - Sending: get-packages args: ['obsoletes', 'False']   <yum_backend._send_command>
00:45:16 : INFO - Getting available obsoletes
00:45:16 : DEBUG - got 0 packages from yum backend   <yum_backend.get_packages>
00:45:16 : INFO - 0 packages returned
00:45:16 : INFO - Adding Packages to view
00:45:16 : DEBUG - START: Adding updates & obsoletes packages to view   <yumexgui._add_packages>
00:45:16 : INFO - Added 0 Packages to view
00:45:16 : DEBUG - END: Getting updates packages   <yumexgui.on_packageFilter_changed>
00:45:24 : DEBUG - Quiting the program !!!   <yum_backend.quit>
00:45:24 : DEBUG - get-packages Args: ['obsoletes', 'False']  took 0.00 s to complete   <yumexbackend.yum_server>
00:45:24 : DEBUG - Sending: exit args: []   <yum_backend._send_command>
00:45:24 : INFO - Closing rpm db and releasing yum lock
00:45:24 : DEBUG - :end   <yum_backend.reset>
00:45:24 : INFO - yum backend process is ended
00:45:24 : DEBUG - LAUNCHER: Ready for commands   <yum_backend._check_for_message>
00:45:24 : DEBUG - Sending: #exit args: []   <yum_backend._send_command>
00:45:24 : DEBUG - LAUNCHER : Terminating   <yum_backend._check_for_message>
00:45:24 : DEBUG - &exit   <yum_backend._close>
00:45:26 : DEBUG - Forcing backend to close   <yum_backend._close>
00:45:26 : DEBUG - Backend reset completted   <yum_backend.quit>

If ran with -d it doesn't crash anymore.

Comment 4 Al Pantilimon 2010-11-21 00:56:11 UTC
Actually - I figured out what the issue is. I had a link to yumex on my desktop that reads
/usr/bin/yumex -d --root &
Somehow the link is passing the & sign to yumex as an argument (as opposed to detach the session).
And if the & sign is passed to yumex then yumex crashes. What is interesting though is that the previous version took the same line without crashing. So I am not sure whether this is just my fault or still a minor bug in parsing the yumex arguments. Please advise.

Many Thanks in advance!

Al.

Comment 5 Tim Lauridsen 2010-11-21 08:05:43 UTC
I did some testing, look like 

something like 'sudo /usr/bin/yumex --root' don't work in a launcher

I have added an '--sudo' option upstream, so you can do

'/usr/bin/yumex --sudo' in a launch to avoid the password prompt

You must have a working sudo config with NOPASSWD for your user for it will work

It is more secure than running the whole gui as root :)

Comment 6 Tim Lauridsen 2010-11-21 11:37:09 UTC
Read more here:
http://www.yum-extender.org/cms/node/21

Comment 7 Al Pantilimon 2010-11-22 19:55:53 UTC
:-)

True - it is safer to run with sudo. Thanks for having had a look at it!

Al


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