Bug 15949 – Installer gets /etc/sysconfig/mouse wrong

Bug 15949 - Installer gets /etc/sysconfig/mouse wrong

Summary:	Installer gets /etc/sysconfig/mouse wrong

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Matt Wilson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-08-10 16:43 EDT by Joshua Jensen
Modified:	2008-05-01 11:37 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-08-10 18:07:19 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 Joshua Jensen 2000-08-10 16:43:26 EDT

In the installer, I select Microsoft IntelliMouse PS/2.

The FULLNAME variable in /etc/sysconfig/mouse says:
"Microsoft - IntelliMouse (PS/2)"

This really breaks gpm and X mouse functionality.
Running mouseconfig corrects things, as detailed below:

The FULLNAME line should be:
"Microsoft - IntelliMouse (PS/2)"

Looks like /etc/X11/XF86Config was broken by the installer using
Emulate3Buttons (which I *unchecked* because I didn't want it), and Device
/dev/psaux (instead of /dev/mouse... this part isn't really a bug, but why
not set up correctly like mouseconfig does?).

I have orignal and fixed config files, should you want to look at them.

Thanks

Joshua Jensen
joshua@iwsp.com
joshua@redhat.com

Comment 1 Joshua Jensen 2000-08-10 16:54:39 EDT

Sorry, I got the "fix" to /etc/sysconfig/mouse wrong before... here it is now:
The FULLNAME line should be:
"Microsoft IntelliMouse (PS/2)"

Comment 2 Matt Wilson 2000-08-10 18:07:12 EDT

fixed internally

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