Kernel 2.6.27 Prevents Logitech G5 Mouse From Working

[nullack]

Binary package hint: linux-image-2.6.27-1-generic

Since Intrepid moved to kernel 2.6.27 I am unable to use the mouse in the GDM or gnome. I have a logitech G5 USB gaming mouse. Please note, it is not a Mac G5 mouse. I have conducted some diagnosis and can offer:

* The x logs mention that its trying to setup Mac mouse emulation:

(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Found mouse buttons
(II) Macintosh mouse button emulation: Configuring as mouse
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(II) Macintosh mouse button emulation: Close

* My xorg.conf was default with the standard mouse driver, option for corepointer and so forth. I tried a more explicit xorg.conf with the following entry:

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "evdev"
 Option "CorePointer"
 Option "Name" "Logitech USB Gaming Mouse"
 Option "Buttons" "8"
 Option "ZAxisMapping" "4 5 7 8"
EndSection

However this has no effect and the x logs still show that Mac emulation is trying to occur.

For people with this bug on the same hardware this results in a critically unusable desktop experience. Temporary workaround is to boot the older 2.6.26 revision.

[nullack (nullack)]

Doing some further comparisons between .26 and .27 it appears that X will always setup mac mouse button emulation. What is missing from .27 in the X setup is this:

(II) config/hal: Adding input device Logitech USB Gaming Mouse

Which then results in further log messages about configuring the device under .26,

So for some reason in .27 config/hal fails to setup the device all together.

[nullack (nullack)]

I retested this in helping provide better logs and now I cannot replicate the problem. What concerns me though is that another user on the Ubuntu forums also had the problem, rebooted, and it went away for him (http://ubuntuforums.org/showthread.php?p=5677589#post5677589). I did in fact reboot and still had the problem. Since I booted .26 to work on other areas, now .27 is working.

What I did notice is that on .26 my USB mouse was on event3 and on .27 my usb mouse has changed to event1. I do not know if switching event numbers is normal but I have seen some hardware guides for getting specific mouse buttons to work configuring the mouse via event numbers in xorg.conf.

I will try to replicate this issue and attach logs showing the issue if it occurs again.

[nullack (nullack)]

The other user who had this problem which he fixed by rebooting has clarified to me that there was in fact no updates between the reboot.

[Leann Ogasawara (leannogasawara)]

Hi nullack,

Thanks for trying to gather the logs. I guess it's better to have the issue fixed and be a little stumped as to why rather than having no fix. Regardless, please let us know if you are able to replicate this issue. I'm going to set this to "Incomplete" for the time being. Please set the status back to "New" if you are able to reproduce. Thanks.

[hal2k1 (quiet1)]

I have a Logitech Marble Mouse. Every time I install Linux, I have to modify xorg.conf to tell X all about it.

I use a standard "InputDevice" section that has always worked before for other distributions and even for Ubuntu up until and including Hardy.

For Interpid Ibex, suddenly it no longer works.

When I run xev, it sees the four mouse buttons and reports them as 1 (larger) and 8 (smaller) on the left hand side, and 3 and 9 repsectively on the right-hand side.

I try to configure it so that button 1 is left-click, button 3 is right-click, button 9 is middle-click and while button 8 is held down the trackball acts as a scroll wheel instead of moving the mouse cursor.

======================
From my xorg.conf:

Section "InputDevice"
    Identifier "Marble Mouse"
    Driver "mouse"
    Option "CorePointer"
    Option "Name" "Logitech USB Trackball"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "Buttons" "5"
    Option "EmulateWheel" "true"
    Option "EmulateWheelButton" "9"
    Option "YaxisMapping" "4 5"
    #Option "XaxisMapping" "6 7"
    Option "ButtonMapping" "1 8 3 9 2"
EndSection

and later:

Section "ServerLayout"
        Identifier "Default layout"
        Screen "Default Screen"
        InputDevice "Marble Mouse"
EndSection

=======================

From $ cat /var/log/Xorg.0.log | grep Adding
(II) XINPUT: Adding extended input device "Marble Mouse" (type: MOUSE)
(II) config/hal: Adding input device Logitech USB Trackball
(II) XINPUT: Adding extended input device "Logitech USB Trackball" (type: MOUSE)
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(II) config/hal: Adding input device Macintosh mouse button emulation
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)

=====================

Attached file has more detail.

So what gives?

Why doesn't it work for Interpid Ibex? All I get is left-click on button 1, right-click on button 3, and the normal mouse movement. To get a middle-click, I have to depress buttons 1 and 3 together.

That might be the "Macintosh mouse button emulation" over-riding the "Marble Mouse", might it not? Should I try to blacklist something? Perhaps edev?

More detail in the attached file.

[Ali Afshar (aafshar)]

Hal2k1 did you get this fixed? I have the identical issue.

[Ali Afshar (aafshar)]

For anyone trying to work this out:

There is a new thing in Intrepid that auto-detects this stuff, and will allow us to change settings at runtime, with one day a graphical UI (sounds great!), but for now it is not working, so you can either play with xinput (by reading manualks) or here is a work around to disable the auto stuff:

Edit /etc/X11/xorg.conf, and add:

Section "ServerFlags"
    Option "AutoAddDevices" "false"
EndSection

(you may have this section already, in which case add the option to your existing section)

PS Why is this bug marked incomplete? What information is missing? Perhaps I can help provide it?

[hal2k1 (quiet1)]

> Hal2k1 did you get this fixed? I have the identical issue.

Not yet, I got very frustrated with my crippled mouse functionality. I use a Logitech Marble Mouse for a medical reason, and it is not an option for me to use a standard mouse with scroll wheel. If this issue isn't fixed in Intrepid Ibex, then I simply won't be using Intrepid Ibex. It is a show-stopper issue for me.

I have currently gone back to Hardy (x86_64) running Kubuntu with KDE 4.1 from the ppa repositories.

Hardy works fine. It is only Interpid that has this issue.

>There is a new thing in Intrepid that auto-detects this stuff, and will allow us to change settings at runtime, with one day a graphical UI (sounds great!), but for now it is not working, so you can either play with xinput (by reading manualks) or here is a work around to disable the auto stuff:

>Edit /etc/X11/xorg.conf, and add:

Section "ServerFlags"
    Option "AutoAddDevices" "false"
EndSection

... So are you saying that if I edit xorg.conf, and I add the following pieces:

======================

Section "InputDevice"
    Identifier "Marble Mouse"
    Driver "mouse"
    Option "CorePointer"
    Option "Name" "Logitech USB Trackball"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "Buttons" "5"
    Option "EmulateWheel" "true"
    Option "EmulateWheelButton" "9"
    Option "YaxisMapping" "4 5"
    #Option "XaxisMapping" "6 7"
    Option "ButtonMapping" "1 8 3 9 2"
EndSection

and later:

Section "ServerFlags"
    Option "AutoAddDevices" "false"
EndSection

Section "ServerLayout"
        Identifier "Default layout"
        Screen "Default Screen"
        InputDevice "Marble Mouse"
EndSection

=======================

... that now with Interpid Ibex my Marble Mouse trackball should work properly once more, as it used to with Hardy Heron?

If that is the case then I will try it also (assuming I have understood you properly) and I will confirm if it works.

[hal2k1 (quiet1)]

This is a new bug for Intrepid Ibex. It was not present in Hardy Heron. It has now been reported by at least two people.

[Ali Afshar (aafshar)]

> ... that now with Interpid Ibex my Marble Mouse trackball should work properly once more, as it used to with Hardy Heron?

Yes, just adding that one option to my Hardy xorg.conf made it all back to normal in Intrpid.

[Ali Afshar (aafshar)]

From http://www.ubuntu.com/testing/intrepid/beta, re: xorg 7.4 "This release brings much better support for hot-pluggable input devices such as tablets, keyboards, and mice."

So I guess this is an xorg package bug in Ubuntu, and so I will try and add the correct packages to the report so the correct people get informed. I am pretty sure its not a kernel bug. Please change back if I am wrong.

[Ali Afshar (aafshar)]

This is a bug in a documented feature of Xorg I believe. Please change back to linux kernel package if I am wrong.

[jwinget (jwinget)]

Confirming both the Marble Mouse bug and the fix posted by Ali Afshar. I pasted the ServerFlags section into my Xorg.conf just above the ServerLayout, restarted X, and now the mouse works like it did in Hardy. No other changes/updates were required.

[hal2k1 (quiet1)]

jwinget wrote:
> Confirming both the Marble Mouse bug and the fix posted by Ali Afshar.
> I pasted the ServerFlags section into my Xorg.conf just above the
> ServerLayout, restarted X, and now the mouse works like it did in Hardy.
> No other changes/updates were required.
>
>
Also confirming the fix posted by Ali Afshar.

[spiralscratch (spiralscratch)]

Just an FYI:

I had an issue with Intrepid and my Logitech MX700 mouse. On X startup the cursor would shoot up to the top of the screen. Attempts to pull it down resulted in it going right back up.

Pasting the above-posted ServerFlags section into the xorg.conf file and restarting GDM appears to have worked around the issue.

[Ali Afshar (aafshar)]

Unfortunately, the "fix" outlined above is not an actual fix, I believe it just turns the buggy stuff off.

This bug seems to have no traction among developers/important people in Ubuntu. Not sure why. It will be a serious one come intrepid release.

[StormTrooperVII (stormtroopervii)]

>Edit /etc/X11/xorg.conf, and add:
>
>Section "ServerFlags"
> Option "AutoAddDevices" "false"
>EndSection

This change actually had no effect for me, I made it and then an hour later the problem manifested itself. However, in the InputDevice section, I had
    Option "Device" "/dev/psaux"

and noticed this line in the comments, so I changed it to this:
    Option "Device" "/dev/input/mice"

The problem hasn't happened yet today, but that doesn't mean that it won't. If you would like more information from me to help diagnose the problem, let me know. It really is a major issue, as I use Ubuntu on my work machine, and if it is rendered unusable I am not happy.

[StormTrooperVII (stormtroopervii)]

So I have played around with a few options and still am having no luck. It has happened more than once today. Really, I think the priority of this issue should be increased, as it is a complete showstopper. I am close to reinstalling with 8.04, so if you would like some debugging information for this problem, now would be the time to ask for it. Here is my xorg.conf, very similar to what I used in hardy, except for the two changes noted in my comments above

[Fabián Rodríguez (magicfab)]

Marking this as High, assigning to nobody (as opposed to Ali Afshar - correct me if wrong).

[Timo Aaltonen (tjaalton)]

attach the output of lshal with 2.6.27.

[Timo Aaltonen (tjaalton)]

oh and the full xorg logfile.

[Timo Aaltonen (tjaalton)]

scratch that, just try disabling the mouse emulation device by running

xinput set-int-prop "Macintosh mouse button emulation" "Device Enabled" 8 0

and see if it helps anything.

[Timo Aaltonen (tjaalton)]

I bet it changes nothing. You need to try out jaunty alpha2 livecd, and tell exactly what is wrong with the behaviour. Sounds like the button mappings are wrong?

[Timo Aaltonen (tjaalton)]

Looking at this messy bug closer (sigh), it appears as if the original submitter can't reproduce it, so I'll close it. If the others who have completely different hardware still have problems with jaunty alpha2, please open a new bug against -evdev, thanks.

[Ali Afshar (aafshar)]

Really bad bug closure (imo). I can still reproduce it on the current release of Ubuntu, with a similar mouse/trackball. The bug still stands, please don't be sidetracked by the O.P.'s impressions of what was causing it. Reopening.

[Timo Aaltonen (tjaalton)]

no, open a new bug as I requested. This is getting far too hard to follow.

[Ali Afshar (aafshar)]

Sorry, this is getting childish. If you decide to close this bug, it is clearly your responsibility to open a new bug. There, I have "requested" it too.

[Timo Aaltonen (tjaalton)]

there, bug 313148, you've been subscribed.