with bootnet.img from 4/07/2000 and update-disk from 4/07/2000 (per Bug Fix Advisory ID RHBA-2000:010-01), I get the following exception/traceback during a portion of a kickstart done as 'linux updates ks=floppy': ... File "/usr/lib/anaconda/mouse.py", line 93, in __init__ apply(self.set, mouseType) File "/usr/lib/anaconda/mouse.py", line 139, in set (gpm, x11, dev, em) = self.mice[mouse] KeyError: none If I go into 'Debug' and 'print mouse' it returns 'none' (not None). Note that RH6.2 kickstarts prior to these updated disks (that is, the images that came with RH62 on CD) did not throw this exception. For what it's worth, my kickstart directives related to X and mice are: # probe, find mouse # probe, find xconfig --card --monitor --startxonboot
Is anything ever going to happen with this? This bug is 15 days old and is blocking our entire automated rollout of RH62 via kickstart.
This bug has been assigned to the test lab to try to reproduce.
verified in test lab w/above mouse & xconfig lines ... setting explicit mouse avoids the error (ie mouse genericps2, or similar) ... this occurs both with original zoot boot disks and updates ...
this issue is fixed in the next release...
Please verify fix works.
verified w/generic 3 button ps2 mouse ...