Bug 186145 - No retry option when cdrom have hard-error
Summary: No retry option when cdrom have hard-error
Keywords:
Status: CLOSED DUPLICATE of bug 191301
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL: http://www.freedows.com
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-21 21:16 UTC by Felipe Pardal
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-15 18:37:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Felipe Pardal 2006-03-21 21:16:07 UTC
Description of problem:
When we have an error at a CD-rom at installation, the error dialog do not show
retry option, just restart system. This is ugly, man, sometimes we are at CD #5
and get an error and need to start the installation from begining.

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


How reproducible:


Steps to Reproduce:
1. Begin installation with CD
2. put a CD-ROM with problem (scratch)
3. the error dialog don't have a 'retry' button 
4. Then you need to restart ALL the installation
  
Actual results:
just restart button

Expected results:
we need a retry button too

Comment 1 Reg Clemens 2006-05-10 17:56:30 UTC
Me too.
I have never had a Fedora install go thru without some CD problem.  However
telling it to 'retry' has always fixed the problem (OK, sometimes Ive had
to take the CD out clean it and try again, but never a complete failure).

We need the 'retry' option back, the current code doesnt make any sense.
Why a reboot button when your only option is to reboot?

Till this gets fixed Ill be reading all 5 CDs in to disk then doing a DISK
or FTP install, it will save the few working neurons from self destructing.


Comment 2 Jeremy Katz 2006-05-15 18:37:10 UTC

*** This bug has been marked as a duplicate of 191301 ***


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