Bug 10007

Summary: Xorg -configure should check for alternate mouse devices locations
Product: xorg Reporter: Olav Sandstå <olav>
Component: Server/GeneralAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: 7.1 (2006.05)   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Olav Sandstå 2007-02-17 06:00:01 UTC
The is a proposal for an improvement to "Xorg -configure" with regards to mouse configuration

When running this command it produces a xorg.conf.new file with the following for the mouse:

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "auto"
        Option      "Device" "/dev/mouse"
        Option      "ZAxisMapping" "4 5 6 7"
EndSection

The "Device" "/dev/mouse" entry is created even when /dev/mouse does not exists on the machine. The proposal is that Xorg -configure should try if some other likely device locations exists before using this as a fallback. E.g., I would like to see that it check if /dev/input/mice existed and used that instead in the config file if /dev/mouse did not exists.
Comment 1 Daniel Stone 2007-02-27 01:36:27 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 2 Chris Wilson 2017-08-25 11:14:44 UTC
*** Bug 102405 has been marked as a duplicate of this bug. ***
Comment 3 Martin Peres 2017-08-25 11:19:55 UTC
Chris forgot a couple of 0s in the bug ID. Sorry for the noise!
Comment 4 GitLab Migration User 2018-12-13 22:17:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/351.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.