Switching to USB sound device stops USB mouse clicks from registering

Bug #1581626 reported by Ronald McCollam on 2016-05-13
56
This bug affects 10 people
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Low
Unassigned

Bug Description

When I switch the primary sound device to a USB headset connected to my laptop, mouse click events no longer work except in the Sound Settings window. This does not seem to occur when the device is connected, only when it is made the default audio device.

Once this occurs, the mouse events do not work until the device is disconnected. Clicks inside the Sound Settings window are registered (including buttons and other tabs inside the System Settings window, but not the titlebar or close/minimize/maximize buttons.) Focus can be given to other windows via alt-tab and keyboard input continues to function, but mouse events do not register on windows focused in this way.

This is *deeply* weird, BTW.

Hardware:
Jabra EVOLVE 80 headset
lsusb reports: Bus 002 Device 022: ID 0b0e:0305 GN Netcom

Steps to reproduce:
1. Connect the device to a USB port.
2. Open Sound Settings window.
3. Select the Jabra USB device as the primary sound device.
4. Observe that mouse clicks no longer register outside of the System Settings window.

dmesg shows the following during this process:

[130169.130542] usb 2-2.1.1: new full-speed USB device number 22 using xhci_hcd
[130169.223026] usb 2-2.1.1: New USB device found, idVendor=0b0e, idProduct=0305
[130169.223031] usb 2-2.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[130169.223034] usb 2-2.1.1: Product: Jabra EVOLVE LINK MS
[130169.223036] usb 2-2.1.1: Manufacturer: GN Netcom A/S
[130169.223038] usb 2-2.1.1: SerialNumber: 000051E7669007
[130169.225586] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
[130169.227472] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
[130169.248162] input: GN Netcom A/S Jabra EVOLVE LINK MS as /devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.1/2-2.1.1/2-2.1.1:1.3/0003:0B0E:0305.0013/input/input34
[130169.302858] hid-generic 0003:0B0E:0305.0013: input,hiddev0,hidraw5: USB HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK MS] on usb-0000:00:14.0-2.1.1/input3
[130169.351940] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
[130169.352187] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
[130169.358162] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
[130169.358439] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
[130169.361073] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
[130169.361323] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
[130169.373535] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
[130169.373904] usb 2-2.1.1: 2:1: cannot get freq at ep 0x4
[130169.380322] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
[130169.380645] usb 2-2.1.1: 1:1: cannot get freq at ep 0x83
[130177.637403] usb 2-2.1.1: USB disconnect, device number 22

This appears to possibly be related to bug #1371853.

I'm happy to provide more information, try custom kernels, etc. as needed. Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri May 13 13:00:25 2016
DistUpgraded: 2016-04-25 16:22:59,827 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.2.0-35-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
 i915-4.3.3-4.2.0, 2, 4.2.0-35-generic, x86_64: installed
 virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
 virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
InstallationDate: Installed on 2015-10-03 (222 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. XPS 13 9343
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=21920f07-2445-42e9-82fe-5d6b209d8688 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-25 (17 days ago)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0TM99H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May 11 10:39:32 2016
xserver.configfile: default
xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 5153
 vendor SHP
xserver.version: 2:1.18.3-1ubuntu2

Ronald McCollam (fader) wrote :
Ronald McCollam (fader) wrote :

Just to add, the device does have a set of buttons as well, so it might be some sort of USB HID conflict? Only two of them show anything when run under xev, XF86VolumeUp and XF86VolumeDown.

Ronald McCollam (fader) wrote :

A little more info:

'xinput list' provides the following when the device is plugged in:

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ELAN Touchscreen id=12 [slave pointer (2)]
⎜ ↳ DLL0665:01 06CB:76AD Touchpad id=14 [slave pointer (2)]
⎜ ↳ Logitech K520 id=10 [slave pointer (2)]
⎜ ↳ Logitech Wireless Mouse id=11 [slave pointer (2)]
⎜ ↳ GN Netcom A/S Jabra EVOLVE LINK MS id=18 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ Integrated_Webcam_HD id=13 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
    ↳ Dell WMI hotkeys id=17 [slave keyboard (3)]
    ↳ UVC Camera (046d:081b) id=16 [slave keyboard (3)]

"GN Netcom A/S Jabra EVOLVE LINK MS" shows up as a core pointer(!) so this is very likely related to the issue.

I put the following into /usr/share/X11/xorg.conf.d/50-jabra.conf:

Section "InputClass"
 Identifier "Jabra"
        MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS"
 Option "Ignore" "on"
EndSection

This prevents the pointer issue described in the bug at the cost of breaking the volume control buttons. I tried using

    Option "ButtonMapping" "0"

but this had no effect; only "Ignore" seems to work.

Ronald McCollam (fader) wrote :
Download full text (3.8 KiB)

Yet more info and a better fix:

xinput list --long provides this for the device:

⎜ ↳ GN Netcom A/S Jabra EVOLVE LINK MS id=15 [slave pointer (2)]
 Reporting 16 classes:
  Class originated from: 15. Type: XIButtonClass
  Buttons supported: 12
  Button labels: "Button 0" "Button 1" "Button 2" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button 3" "Button 4" "Button 5" "Button 6" "Button 7"
  Button state:
  Class originated from: 15. Type: XIKeyClass
  Keycodes supported: 248
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 0:
    Label: Abs X
    Range: 0.000000 - 1000.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 1600.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 1:
    Label: Abs Y
    Range: 0.000000 - 1000.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 900.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 2:
    Label: Abs Misc
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 3:
    Label: Abs Misc
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 4:
    Label: Abs Misc
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 5:
    Label: Abs Misc
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 6:
    Label: Abs Misc
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 7:
    Label: Abs Misc
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 8:
    Label: Abs Misc
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 9:
    Label: Abs MT Touch Major
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 10:
    Label: Abs MT Touch Minor
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 11:
    Label: Abs MT Width Major
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  Class originated from: 15. Type: XIValuatorClass
  Detail for Valuator 12:
    Label: Abs MT Width Minor
    Range: 0.000000 - 12.000000
    Resolution: 0 units/m
    Mode: absolute
    Current value: 0.000000
  C...

Read more...

Ronald McCollam, thank you for reporting this and helping make Ubuntu better.

As per http://www.dell.com/support/home/us/en/19/product-support/product/xps-13-9343-laptop/drivers?os=biosa an update to your computer's buggy, insecure, and outdated BIOS is available (A07). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status New.

If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

tags: added: bios-outdated-a07
Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (Ubuntu):
status: Incomplete → Expired
kringalf (spam-cpp-tools) wrote :

I have the same problem with a DELL LATITUDE E6530 and up2date BIOS:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date && sudo dmidecode -s system-product-name
A17
08/19/2015
Latitude E6530

Changed in xorg (Ubuntu):
status: Expired → Confirmed

kringalf, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Changed in xorg (Ubuntu):
status: Confirmed → Incomplete
maxadamo (massimilianoadamo) wrote :

you should be able to fix this issue, creating a file as following:
$ cat /etc/X11/xorg.conf.d/jabra.conf
Section "InputClass"
    Identifier "Jabra Audio docking station"
    MatchDevicePath "/dev/input/event*"
    MatchProduct "Netcom"
    MatchVendor "GN_Netcom_A_S"
    Option "Ignore" "true"
EndSection

Michael Rauch (michael-rauch) wrote :

Solution from post #10 worked for me.

Michael Rauch, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

jth (jth) wrote :

Hi

I have added #1640456 hopefully with the requested information with xdiagnose installed to continue.

--
Johan Thelmén

zomp (jan-molnar) on 2016-12-19
Changed in xorg (Ubuntu):
status: Incomplete → Confirmed
zomp (jan-molnar) wrote :

Hm, I have just found out bug 1619307 was intentionally created as a fork of this one. I have no idea why – the bugs really are the same. Feel free to revert my changes and link the issues somehow.
Best,
Jan
P.S. The issue seems to be BIOS independent – I experience it on ThinkPad X230.

zomp, to track your hardware, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Changed in xorg (Ubuntu):
status: Confirmed → Incomplete

This bug also affect me as well. I have a similar model, Jabra EVOLVE 40. If the device is connected during startup I have no issue, but if its connected once logged in or subsequently disconnected/connected, I have a similar issue to the OP, though it's regardless if I set the device as the default.

lsusb:

Bus 002 Device 008: ID 0b0e:0306 GN Netcom

dmesg:

[ +0.018675] input: GN Netcom A/S Jabra EVOLVE LINK as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.1/2-1.6.1:1.3/0003:0B0E:0306.0007/input/input24
[ +0.052471] hid-generic 0003:0B0E:0306.0007: input,hiddev0,hidraw4: USB HID v1.00 Device [GN Netcom A/S Jabra EVOLVE LINK] on usb-0000:00:1d.0-1.6.1/input3
[ +0.025352] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[ +0.000515] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[ +0.003624] usb 2-1.6.1: 2:1: cannot get freq at ep 0x4
[ +0.000626] usb 2-1.6.1: 2:1: cannot get freq at ep 0x4
[ +0.001736] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[ +0.000497] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[ +0.019249] usb 2-1.6.1: 2:1: cannot get freq at ep 0x4
[ +0.000646] usb 2-1.6.1: 2:1: cannot get freq at ep 0x4
[ +0.003870] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[ +0.000623] usb 2-1.6.1: 1:1: cannot get freq at ep 0x83
[ +0.374731] retire_capture_urb: 915 callbacks suppressed
[ +22.492209] usb 2-1.6.1: USB disconnect, device number 9

I'm not using an xorg config file, so not sure how to apply the fix from post 10.

Post 10 did work with directory by creating the jabra.conf in /usr/share/X11/xorg.conf.d/

Andrew La Russa, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Launchpad Janitor (janitor) wrote :

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

Changed in xorg (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.