Plugging in Logitech G930 USB headset breaks mouse click behaviour

[MattW]

lsb_release -rd: (Note: I get the same behaviour in kubuntu 12.04 and kubuntu 12.10)
Description: Ubuntu Raring Ringtail (development branch) <- running kubuntu 13.04
Release: 13.04

To reproduce:
1) Plug in the USB dongle
2) Wait for the headset to connect

As soon as the headset connects (e.g. after connecting the USB dongle) the application which currently has focus will be the only one which receives left mouse click events. This happens in both GNOME3 and KDE4.

Alt+(Left,Right)Click + Drag stops moving/resizing windows.
Left click does affect keyboard focus.
Scrolling the volume wheel on the headset down acts like a middle click and scrolling up like a left click.
Synergy also stops being able to move the mouse outside the current screen as soon as you click inside the host screen.
The window decorations (including the window which has focus) stop recieving mouse events.

(Expected behaviour is unaffected mouse behaviour and headset volume wheel functionality)

It is possible to move a window around by doing:
1) Connect the headset with the window active
2) Left click and drag outside of that window
3) The window will be moved as if you were Alt+Left click dragging from inside the window.
4) A second left click will move mouse focus to the window below but will not move that window above the one which previously had focus

This person seems to have had a possibly related issue: http://forums.gentoo.org/viewtopic-t-926996-start-0.html

dmesg output from unplugging/replugging USB dongle:
[ 6848.345037] usb 1-1.1: USB disconnect, device number 25
[ 6851.865274] usb 1-1.1: new full-speed USB device number 26 using ehci-pci
[ 6852.580624] usb 1-1.1: New USB device found, idVendor=046d, idProduct=0a1f
[ 6852.580629] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6852.580632] usb 1-1.1: Product: Logitech G930 Headset
[ 6852.580634] usb 1-1.1: Manufacturer: Logitech
[ 6852.589251] input: Logitech Logitech G930 Headset as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.3/input/input101
[ 6852.589453] hid-generic 0003:046D:0A1F.0055: input,hiddev0,hidraw3: USB HID v1.01 Device [Logitech Logitech G930 Headset] on usb-0000:00:1a.0-1.1/input3

Mouse click behaviour breaks as soon as the headset reconnects.

Workaround:

Running: modprobe -r usbhid; modprobe usbhid; temporarily fixes mouse click behaviour (but not the volume wheel clicking).

The mouse click problem comes back when moving an audio stream to the headset via kmix.

dmesg output from reloading usbhid kernel module:
[ 6915.812979] usbcore: deregistering interface driver usbhid
[ 6915.888438] input: Microsoft Wired Keyboard 600 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input103
[ 6915.888671] hid-generic 0003:045E:0750.0057: input,hidraw0: USB HID v1.11 Keyboard [Microsoft Wired Keyboard 600] on usb-0000:00:1a.0-1.4/input0
[ 6915.894333] input: Microsoft Wired Keyboard 600 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/input/input104
[ 6915.894576] hid-generic 0003:045E:0750.0058: input,hidraw1: USB HID v1.11 Device [Microsoft Wired Keyboard 600] on usb-0000:00:1a.0-1.4/input1
[ 6915.897121] input: USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input105
[ 6915.897760] hid-generic 0003:093A:2521.0059: input,hidraw2: USB HID v1.11 Mouse [USB OPTICAL MOUSE] on usb-0000:00:1a.0-1.2/input0
[ 6915.900782] input: Logitech Logitech G930 Headset as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.3/input/input106
[ 6915.901949] hid-generic 0003:046D:0A1F.005A: input,hiddev0,hidraw3: USB HID v1.01 Device [Logitech Logitech G930 Headset] on usb-0000:00:1a.0-1.1/input3
[ 6915.902002] usbcore: registered new interface driver usbhid
[ 6915.902005] usbhid: USB HID core driver

Mouse click behaviour returns to normal immediately.

Occasionally the headset will start working as expected (volume wheel affects system volume, mouse behaviour is normal) but unfortunately I have not been able to work out how to reproduce this.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Groen (martyla)]

Do you dual boot into Windows?
This seems to be the cause of the problem for myself, at least - in Ubuntu 64bit (12.04.2LTS Precise and 12.10 Quantal), dual booting from Windows 7.

After having this same bug I have found a way to reproduce the problem:
-Boot into Windows, turn headset on, restart into Ubuntu and try adjust the volume with the volume wheel

In this case it almost always will cause similar GUI unresponsiveness to what you described.

Possible workaround:
-When in Windows or before booting into Ubuntu, turn off the headset -> boot into Ubuntu -> turn on then headset

Note: Restarting Ubuntu once the headphones were previously turned on in Ubuntu does not cause it to become unresponsive (only when restarting from windows). Disconnecting the wireless receiver does not count as turning off the headset

[sblatt (stefan-blatter)]

Hey, I just had the same problem and could trace it back to the g930 and reboot from windows 7 too. I fixed it without restart by pulling out the dongle and restarting the headset, then putting in the dongle.

[Tomas Sandven (codemonkey1991)]

This affects me as well. I can second that disconnecting the dongle, restarting the headset and reconnecting the dongle appears to fix the issue. I'm using Logitech G930 with Ubuntu 12.04 LTS, freshly installed, dual-booting with Windows 8.1.

[penalvch (penalvch)]

MattW, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-input-evdev REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[DiegoRivera (diego-rivera)]

The problem has been narrowed down to when the headset is actually charging - either through to the computer's USB ports or via a wall-socket charger (any micro-USB charger with 0.5A output will suffice).

When the headset is unplugged (i.e. fully wireless), everything works fine. But when the headset is plugged in, the symptoms emerge. I will provide further information later today after I make some time to investigate more fully.

[Mark Riedesel (mriedesel)]

Building upon DiegoRivera's post. I'm looking at output from xinput query-state "Logitech Logitech G930 Headset" and it appears as though things work fine as long as all the ButtonClass items (button[10] through button[14]) all report as "up".

I can't seem to reproduce getting the device into a state where one of the buttons is reported "down", but as soon as one of them is "down" then mouse input starts acting very odd.

It seems like disconnecting the USB dongle for the headset, turning the headset off, reinserting the USB dongle, and then turning the headset on resets the state of all the buttons to "up".

[penalvch (penalvch)]

DiegoRivera / Mark Riedesel, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Pat Litke (litke-p)]

3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Will confirm having similar issues. Appears to only occur when going from an unplugged state to a plugged state for charging, though only intermittently. I have yet to observe a reliable set of actions to prompt the symptoms.

Will submit a bug report when it occurs again.

[penalvch (penalvch)]

Pat Litke, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-input-evdev (Ubuntu) because there has been no activity for 60 days.]

[Tilman Krummeck (tilman-h)]

So from my understanding this bugs needs some additional information, correct? Has someone opened a new report yet?

[mpw (matthiaspeterw)]

I can confirm that this bug still exists. What kind of information do you need?

Unplugging the dungle and restarting changes the keycodes back to standard.

I think there's a mechanism to change the keycodes send be the headset. We have to find it and reset the headset when the kernel modul is loaded.

[Jan Groenewald (jan-aims)]

We've just come across this on Trusty using both vivid 3.19 and utopic 3.16 kernels.
Willing to gather information.

[penalvch (penalvch)]

Jan Groenewald, one may be helpful in gathering information by filing a new report via a terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

Also, please feel free to subscribe me to it.

[Jan Groenewald (jan-aims)]

We fixed this with:

root@lynne-laptop:/etc/modprobe.d# cat usbhid.conf
# Fix for USB logitech headset messing with mouse behaviour via usbhid
module
#
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1155819
# https://forums.gentoo.org/viewtopic-t-926996-start-0.html
options usbhid quirks=0x046D:0x0A38:0x0004
root@lynne-laptop:/etc/modprobe.d#

On 17 September 2015 at 03:10, Christopher M. Penalver <
<email address hidden>> wrote:

> Jan Groenewald, one may be helpful in gathering information by filing a
> new report via a terminal:
> ubuntu-bug xorg
>
> Please ensure you have xdiagnose installed, and that you click the Yes
> button for attaching additional debugging information.
>
> Also, please feel free to subscribe me to it.
>
> --
> You received this bug notification because you are a member of AIMS,
> which is subscribed to the bug report.
> https://bugs.launchpad.net/bugs/1155819
>
> Title:
> Plugging in Logitech G930 USB headset breaks mouse click behaviour
>
> Status in xserver-xorg-input-evdev package in Ubuntu:
> Expired
>
> Bug description:
> lsb_release -rd: (Note: I get the same behaviour in kubuntu 12.04 and
> kubuntu 12.10)
> Description: Ubuntu Raring Ringtail (development branch) <- running
> kubuntu 13.04
> Release: 13.04
>
> To reproduce:
> 1) Plug in the USB dongle
> 2) Wait for the headset to connect
>
> As soon as the headset connects (e.g. after connecting the USB dongle)
> the application which currently has focus will be the only one which
> receives left mouse click events. This happens in both GNOME3 and
> KDE4.
>
> Alt+(Left,Right)Click + Drag stops moving/resizing windows.
> Left click does affect keyboard focus.
> Scrolling the volume wheel on the headset down acts like a middle click
> and scrolling up like a left click.
> Synergy also stops being able to move the mouse outside the current
> screen as soon as you click inside the host screen.
> The window decorations (including the window which has focus) stop
> recieving mouse events.
>
> (Expected behaviour is unaffected mouse behaviour and headset volume
> wheel functionality)
>
> It is possible to move a window around by doing:
> 1) Connect the headset with the window active
> 2) Left click and drag outside of that window
> 3) The window will be moved as if you were Alt+Left click dragging from
> inside the window.
> 4) A second left click will move mouse focus to the window below but
> will not move that window above the one which previously had focus
>
> This person seems to have had a possibly related issue:
> http://forums.gentoo.org/viewtopic-t-926996-start-0.html
>
> dmesg output from unplugging/replugging USB dongle:
> [ 6848.345037] usb 1-1.1: USB disconnect, device number 25
> [ 6851.865274] usb 1-1.1: new full-speed USB device number 26 using
> ehci-pci
> [ 6852.580624] usb 1-1.1: New USB device found, idVendor=046d,
> idProduct=0a1f
> [ 6852.580629] usb 1-1.1: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [ 6852.580632] usb 1-1.1: Product: Logitech G930 Headset
> [ 6852.580634] usb 1-1.1: Manufacturer: Logitech
> [ 6852...