Bug 11637 – exception in mouse.py with 4/07 updated images

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 11637 - exception in mouse.py with 4/07 updated images

Summary:	exception in mouse.py with 4/07 updated images

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Brock Organ
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	11615
	Show dependency tree / graph

Reported:	2000-05-24 12:14 EDT by Jeff Blaine
Modified:	2007-04-18 12:27 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-06-23 11:22:27 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jeff Blaine 2000-05-24 12:14:53 EDT

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

Comment 1 Jeff Blaine 2000-06-07 13:48:08 EDT

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.

Comment 2 Michael Fulbright 2000-06-09 10:14:05 EDT

This bug has been assigned to the test lab to try to reproduce.

Comment 3 Brock Organ 2000-06-12 10:07:49 EDT

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 ...

Comment 4 Brock Organ 2000-06-12 11:17:35 EDT

this issue is fixed in the next release...

Comment 5 Michael Fulbright 2000-06-22 14:13:22 EDT

Please verify fix works.

Comment 6 Brock Organ 2000-06-23 11:22:25 EDT

verified w/generic 3 button ps2 mouse ...

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