Bug 179814 - Yumex hangs reading the local repository
Summary: Yumex hangs reading the local repository
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
(Show other bugs)
Version: 5
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-03 04:29 UTC by Wilbur Harvey
Modified: 2014-01-21 22:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-03 04:39:04 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Wilbur Harvey 2006-02-03 04:29:52 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060126 Fedora/1.5-5 Firefox/1.5

Description of problem:
When trying to initialize Yumex, it hangs when trying to initialize the local repository.

Component: yumex
Version: 0.99.3
Summary: TB24c7a3dd yumexmain.py:321:delete_event:RuntimeError: called outside of a mainloop

Traceback (most recent call last):
  File "/usr/share/yumex/yumexmain.py", line 321, in delete_event
    gtk.main_quit()
RuntimeError: called outside of a mainloop

Local variables in innermost frame:
widget: <gtk.Window object (GtkWindow) at 0xb794543c>
data: None
event: <GdkEvent at 0xa610910>
self: <__main__.MainApplication instance at 0xb79417cc>


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

How reproducible:
Always

Steps to Reproduce:
1.run yumex
2.
3.
  

Actual Results:  Hang

Expected Results:  Shows list of packages to update

Additional info:
Comment 1 Ignacio Vazquez-Abrams 2006-02-03 04:39:04 UTC 
If it's a bug in yumex then you should be filing against yumex, not yum.
Note You need to log in before you can comment on or make changes to this bug.