[ale] weird mouse problem

Brian Pitts brian at polibyte.com
Fri Sep 3 09:55:42 EDT 2010


On 09/02/2010 07:48 PM, Jim Philips wrote:
> The issue with ondemand governor is a known kernel bug that affects older
> processors, like mine. But I can't say that it directly affects mouse
> operations. I did manager to get to the Xorg log and saw something
> interesting:
> 
[snip]
> (II) config/udev: Adding input device Macintosh mouse button emulation
> (/dev/input/event2)
> (**) Macintosh mouse button emulation: Applying InputClass "evdev pointer
> catchall"
> (**) Macintosh mouse button emulation: always reports core events
> (**) Macintosh mouse button emulation: Device: "/dev/input/event2"
> (II) Macintosh mouse button emulation: Found 3 mouse buttons
> (II) Macintosh mouse button emulation: Found relative axes
> (II) Macintosh mouse button emulation: Found x and y relative axes
> (II) Macintosh mouse button emulation: Configuring as mouse
> (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
> (**) Macintosh mouse button emulation: EmulateWheelButton: 4,
> EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> (II) XINPUT: Adding extended input device "Macintosh mouse button emulation"
> (type: MOUSE)
> 
> 
> The Logitech mouse is the one I have. I have no idea how the Macintosh
> entries got there. I have never owned such a mouse nor configured for that
> button emulation.

Those messages are normal. I see them on my personal and work computers.

-- 
All the best,
Brian Pitts


More information about the Ale mailing list