Bug 231651 - Package lists inoperative under "customize now"
Summary: Package lists inoperative under "customize now"
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Cantrell
QA Contact:
Keywords: Reopened
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-09 20:05 UTC by G.Wolfe Woodbury
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2007-03-27 21:51:18 UTC

Attachments (Terms of Use)
Traceback (69.21 KB, text/plain)
2007-03-14 17:59 UTC, Ronald Warsow
no flags Details

Description G.Wolfe Woodbury 2007-03-09 20:05:45 UTC
Description of problem:
Selecting customize now produces package lists that are *empty* and inoperative
during the install process.

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

How reproducible:
every time

Steps to Reproduce:
1. boot rawhide boot.iso
2. select "customize now" from software selector
Actual results:
the package lists are all unselected, and selecting packages still produces a
"no optional packages selected" indication on the screen.

Expected results:
ability to adjust package selections

Additional info:
system work2.private:
    Pentium (Dechutes) @400MHz   512MB   ATI Rage128 video
    Intel PIIX chipset (pata-piix)  CD-ROM    40GiB maxtor

Comment 1 David Cantrell 2007-03-09 20:11:30 UTC
This is fixed in rawhide (anaconda >=  Thanks.

Comment 2 G.Wolfe Woodbury 2007-03-13 06:43:59 UTC
This is *not* fixed in rawhide.
Today's rawhide with anaconda- is still exhibiting the same behaviours.

Comment 3 Ronald Warsow 2007-03-14 17:52:53 UTC
same here and backtraces with yesterdays/todays rawhide.

Comment 4 Ronald Warsow 2007-03-14 17:59:28 UTC
Created attachment 150071 [details]

- i tried with diff. mirrors

Comment 5 G.Wolfe Woodbury 2007-03-17 08:37:39 UTC
rawhide of 2007-03-16 (anaconda- still exhibits the behaviour.

Comment 6 David Cantrell 2007-03-27 21:51:18 UTC
I'm not seeing this is rawhide as of today.

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