Bug 59945 - up2date GUI doesn't start anymore after upgrade to skunkwork's version 2.7.24-7.x.2
Summary: up2date GUI doesn't start anymore after upgrade to skunkwork's version 2.7.24...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 7.2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-15 13:52 UTC by Manfred Hollstein
Modified: 2015-01-07 23:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-02-15 13:52:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Manfred Hollstein 2002-02-15 13:52:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020205

Description of problem:
Running up2date without the --nox flag doesn't fire up the GUI anymore;
strace attached to the python process shows that it's trying to read
16777216 bytes in an endless loop from file descriptor 4 which is file
/usr/share/rhn/up2date_client/gui.glade

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


How reproducible:
Always

Steps to Reproduce:
1.Log in as root
2.Start up2date
3.wait crossing fingers...
	

Actual Results:  No GUI pops up

Expected Results:  The graphical dialog window should appear.

Additional info:

This is with the latest update -2.7.24-7.x.2 from the skunkworks
channel in RHN

Comment 1 Manfred Hollstein 2002-02-21 17:23:52 UTC
As of the latest update from today, up2date-2.7.29-7.x.2.i386.rpm and
up2date-gnome-2.7.29-7.x.2.i386.rpm, this appears to be fixed. I'm
closing the report.



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