Bug 210545 - unable to install FC6-pre
Summary: unable to install FC6-pre
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 6
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-12 19:51 UTC by Edwin Schepers
Modified: 2013-01-10 04:06 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-10-13 04:57:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Edwin Schepers 2006-10-12 19:51:23 UTC
Description of problem:
Hi, I thought I'd try FC6-pre. But I'm unable to install. I get this popup 
message that I probably ran into a bug and I should report a bug. I can get 
details and then I see a lot of info.
Unfortunately, I doesn't say how to transfer this info to some file.
I tried to install twice now, and two times I got this messages in different 
stages. First time was when I clicked the checkbox for some extra software. I 
clicked Office (or something). Another choice was Web Server I remember.
I think it has to do something with the network configuration.
I sincerely mean that if no bugfixes have been done on this part, It's better 
to first fix this. I am doing nothing special to get these errors. If someone 
could tell me how to get the backtrace, i'll attach it.

For example : I have two NIC's. In the configuration ipv4 and ipv6 are 
disabled by default. When I click on Change (or something similar), I cannot 
click OK because it gives an error (ipv4 and ipv6 are both unchecked). But if 
I do not press change, I can without any problem press Next.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jeremy Katz 2006-10-13 04:57:37 UTC
The updates.img that was referenced in the FC6Pre announcement has the fix for
this bug


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