Description of Problem:
i386/German/CDROM/Gui/LAPTOP - PCMCIA USED
Crashes after selecting "Do not create boot disk" option and hitting OK.
Every time Laptop default install is used. Minimal avoids this problem.
Steps to Reproduce:
1. Do a german Laptop CDROM install, with PCMCIA drivers
2. At Bootdisk screen, select the do not make boot disk option
3. Hit OK
No bootdisk made and on to next screen
Traceback (innermost last):
File "/usr/bin/anaconda", line 608, in ?
intf.run (id, dispatch, configFileData)
File "/usr/lib/anaconda/gui.py", line 348, in run
self.icw.run (self.runres, configFileData)
File "/usr/lib/anaconda/gui.py", line 776, in run
File "/usr/lib/python1.5/site-packages/gtk.py", line 2608, in mainloop
File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in __call__
ret = apply (self.func, a)
File "/usr/lib/anaconda/gui.py", line 400, in nextClicked
File "/usr/lib/anaconda/gui.py", line 524, in setScreen
new_screen = apply (self.currentWindow.getScreen, args)
File "/usr/lib/anaconda/iw/xconfig_gui.py", line 268, in getScreen
location = available[self.selectedDepth].index(self.selectedRes)
Value Error: list.index(x): x not in list
We (Red Hat) really need to fix this defect before next release.
Could we get the entire traceback attached? Looks like a duplicate of 51273 and
others, but without the rest of the information, it's hard to know for sure
I can't save the traceback to disk (and not for lack of trying). The same error
message keeps popping up (in german, so I have no idea what it says) every time
I try to write out. The floppy *does* write, but it only nukes the disk and
ends up not actually writing the dumpfile. I end up with a blank disk, no dump,
and a german error message.
This looks like some problem with the X configuration. What kind of graphics
chip does this laptop have?
It's a NeoMagic MagicMedia 256AV (NM2200).
Looks very similar to bug #49178, which was supposedly fixed after beta 1...
Unable to reproduce on a laptop here.
We have fixed some issues with X configuration overall, it may very well fix
Did it look like you were running in the old 640x480 16 color mode during the
install (everything was dithered and generally ugly looking)?
Yep, I believe it was.
I believe this is now fixed.