Bug 63830 - Install stops during update
Summary: Install stops during update
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 9
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-19 08:35 UTC by Joachim Backes
Modified: 2008-01-17 17:49 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:48:45 UTC
Embargoed:

Attachments (Terms of Use)

Description Joachim Backes 2002-04-19 08:35:35 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.18 i686)

Description of problem:
Wenn updating my RH 7.2 by skipjack beta, anaconda stops when installing
kdebase-3.0.0-3 and says that the install was broken by a reason which cannot be
identified, and tells that possibly the cd media is buggy. But when testing it
before install start (as offered), the test is OK.

The crash happens during text based install and during graphical install. 

After this broken, my OS is destroyed and must be recovered from backup media.

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


How reproducible:
Always

Steps to Reproduce:
See description
	

Actual Results:  See description.

Expected Results:  kdebase can be installed.

Additional info:

--
Comment 1 Joachim Backes 2002-04-22 08:42:21 UTC 
The bug only appears during a RH 7.2 update. When installing skipjack competely
new, the install runs without any problem.
Comment 2 Michael Fulbright 2002-04-24 16:40:55 UTC 
When you do a install do you pick to install KDE?
Comment 3 Michael Fulbright 2002-05-23 16:54:30 UTC 
Closing due to inactivity - please reopen if you have additional comments to add
to this bug.
Comment 4 Joachim Backes 2002-05-27 08:32:59 UTC 
Seems to be a duplicate of 64592?
Comment 5 Red Hat Bugzilla 2006-02-21 18:48:45 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.