Bug 123653 - mouse not configured properly for gpm
Summary: mouse not configured properly for gpm
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kudzu
Version: 2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-19 20:39 UTC by Florin Andrei
Modified: 2007-11-30 22:10 UTC (History)
4 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2005-09-21 19:11:24 UTC


Attachments (Terms of Use)

Description Florin Andrei 2004-05-19 20:39:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116

Description of problem:
I installed FC2 on an old Dell Latitude CPi laptop. The laptop has a
touchpad with two mouse buttons next to it. Essentially it's like it
has a two-button PS/2 mouse.
The installer configured the mouse properly for X Windows. However,
when trying to run gpm, it exits with:

(no mouse configured)

All previous FC and RH distributions configured the mouse properly on
this system.

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

How reproducible:
Always

Steps to Reproduce:
1.install FC2 on Dell Latitude CPi
2.
3.
    

Actual Results:  built-in mouse (the touchpad buttons) is not
configured properly for gpm

Expected Results:  mouse should be configured properly

Additional info:

Comment 1 Jeremy Katz 2004-05-20 02:38:58 UTC
Didn't kudzu get changed to run mouseconfig again?

Comment 2 Florin Andrei 2004-05-20 03:52:01 UTC
I don't think i understand the question?
You mean if kudzu was run again when the system booted up for the
first time? Yeah, it did, but it only said something about my network
card, no mention about the mouse.

Comment 3 Matthew Miller 2005-04-26 15:23:27 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 4 Jeremy Katz 2005-09-21 19:11:24 UTC
Closing as resolved in later releases 


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