Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15571 - [xorg] Microsoft Natural Wireless Laser Mouse 6000 doesn't works

Attached to Project: Arch Linux
Opened by Maxwell Draven (Ravenman) - Sunday, 19 July 2009, 05:36 GMT
Last edited by Jan de Groot (JGC) - Saturday, 14 November 2009, 15:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I have installed in my computer one Microsoft Natural Wireless Laser Mouse 6000, but at this moment, it doesn't works.

Additional info:
* package version(s)

xorg-server 1.6.1.901-3

* config and/or log files etc.

Attached

Steps to reproduce:
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 14 November 2009, 15:18 GMT
Reason for closing:  Fixed
Comment by Roman Kyrylych (Romashka) - Sunday, 19 July 2009, 09:36 GMT
what did you expect? microsoft products working in linux? :-P
seriously though, I see this in the log:
(II) config/hal: Adding input device Microsoft Microsoft Wireless Optical Mouse? 1.00
(**) Microsoft Microsoft Wireless Optical Mouse? 1.00: always reports core events
(**) Microsoft Microsoft Wireless Optical Mouse? 1.00: Device: "/dev/input/event8"
(WW) Microsoft Microsoft Wireless Optical Mouse? 1.00: device file already in use. Ignoring.
(II) UnloadModule: "evdev"
(EE) PreInit returned NULL for "Microsoft Microsoft Wireless Optical Mouse? 1.00"
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Genius Optical Mouse

"device file already in use. Ignoring." is because of this above:

(**) Option "SendCoreEvents" "True"
(**) Option "CorePointer"
(**) Mouse0: always reports core events
(**) Mouse0: Device: "/dev/input/event8"
(II) Mouse0: Found 5 mouse buttons
(II) Mouse0: Found x and y relative axes
(II) Mouse0: Found scroll wheel(s)
(II) Mouse0: Configuring as mouse
(**) Mouse0: YAxisMapping: buttons 4 and 5
(**) Mouse0: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Mouse0: (accel) keeping acceleration scheme 1
(**) Mouse0: (accel) filter chain progression: 2.00
(**) Mouse0: (accel) filter stage 0: 20.00 ms
(**) Mouse0: (accel) set acceleration profile 0

Not sure how to fix it.
Jan, any ideas?
Comment by Jan de Groot (JGC) - Sunday, 19 July 2009, 12:36 GMT
Seems you have two devices configured as /dev/input/event10, which is weird. Any idea why this happens? udev issue?
Comment by Maxwell Draven (Ravenman) - Saturday, 05 September 2009, 14:27 GMT
The issue continues ... I'm attaching my xorg-server 1.6.3.901-1 configuration and log files.
Comment by Jan de Groot (JGC) - Friday, 23 October 2009, 09:49 GMT
I don't see any issues in your last attached log file. The mouse is added and configured if I'm reading the logfile correctly.

Do you also have problems with xorg from testing?
Comment by Maxwell Draven (Ravenman) - Saturday, 31 October 2009, 20:42 GMT
Yes, I do. The mouse pointer moves very well, but I can only click on the K menu button, nothing more. I'm attaching my xorg-server 1.7.1-1 log file.
Comment by Maxwell Draven (Ravenman) - Saturday, 14 November 2009, 14:58 GMT
I upgraded to xorg-server 1.7.1.901-2 and my mouse has returned to work as before. I don't know if the packages xf86-input-* have been the solution, but the important thing is that everything is back to normal.

A lot of thanks by your help, patience, hard and excellent work. Until the next.

Loading...