Can't switch sound output to USB headset, is added as keyboard

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
User avatar
chrisra
Level 1
Level 1
Posts: 28
Joined: Wed Dec 30, 2015 1:39 pm

Can't switch sound output to USB headset, is added as keyboard

Post by chrisra » Thu Jan 26, 2017 11:22 am

Hi everybody,

right now I'm having a strange issue which I've never encountered before, and I'd appreciate it if someone has an idea how to troubleshoot this :-) My headset shows up in lsusb:

Code: Select all

Bus 001 Device 040: ID 046d:0a38 Logitech, Inc. Headset H340
as well as in the Cinnamon sound settings, but I can't switch to it anymore. To be precise, when I select it as an output, sound still comes through the speakers. I can't select it from the right-click menu of the Cinnamon sound applet, so if I could get log messages from that maybe I'd find out what's going on. Please note that this is a hardware issue, not a Cinnamon issue - it's similar if I use the hardware switch for my WiFi card, only the headset of course doesn't have a switch, and powercycling it (by unplugging, re-plugging) doesn't help.

I'm running Mint 17.3 with kernel 3.19.0-22, 64 bit. Additional information from inxi:

Code: Select all

System:    Host: simmel Kernel: 3.19.0-22-generic x86_64 (64 bit gcc: 4.8.2) Desktop: Cinnamon 2.8.8 (Gtk 3.10.8)
           Distro: Linux Mint 17.3 Rosa
Machine:   System: Dell product: XPS 13 9343
           Mobo: Dell model: 0310JH v: A00 Bios: Dell v: A05 date: 07/14/2015
CPU:       Dual core Intel Core i7-5500U (-HT-MCP-) cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9577
           clock speeds: max: 3000 MHz 1: 2985 MHz 2: 2957 MHz 3: 2992 MHz 4: 2969 MHz
Graphics:  Card: Intel Broadwell-U Integrated Graphics bus-ID: 00:02.0
           Display Server: X.Org 1.15.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1200@60.0hz
           GLX Renderer: Mesa DRI Intel Broadwell GLX Version: 3.0 Mesa 10.1.3 Direct Rendering: Yes
Audio:     Card-1 Intel Wildcat Point-LP High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 Intel Broadwell-U Audio Controller driver: snd_hda_intel bus-ID: 00:03.0
           Card-3 Logitech Headset H340 driver: USB Audio usb-ID: 001-040
           Sound: Advanced Linux Sound Architecture v: k3.19.0-22-generic
Network:   Card: Broadcom BCM4352 802.11ac Wireless Network Adapter driver: wl bus-ID: 02:00.0
           IF: wlan0 state: up mac: <filter>
Drives:    HDD Total Size: 2512.5GB (46.6% used) ID-1: /dev/sda model: SAMSUNG_SSD_PM85 size: 512.1GB
           ID-2: USB /dev/sdb model: RAID size: 2000.4GB
Partition: ID-1: / size: 46G used: 20G (46%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 424G used: 378G (94%) fs: ext4 dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Edit: There were no log messages while switching/trying to switch to the headset for sound output.
Last edited by chrisra on Fri Jan 27, 2017 12:35 pm, edited 1 time in total.

User avatar
chrisra
Level 1
Level 1
Posts: 28
Joined: Wed Dec 30, 2015 1:39 pm

USB headset is added as keyboard/mouse!

Post by chrisra » Fri Jan 27, 2017 11:53 am

I'm closer to a solution: when re-connecting the USB cable, there is some output in Xorg.0.log:

Code: Select all

[203100.864] (II) config/udev: removing device Logitech Inc. Logitech USB Headset H340
[203100.884] (II) evdev: Logitech Inc. Logitech USB Headset H340: Close
[203100.884] (II) UnloadModule: "evdev"
[203128.752] (II) config/udev: Adding input device Logitech Inc. Logitech USB Headset H340 (/dev/input/event6)
[203128.752] (**) Logitech Inc. Logitech USB Headset H340: Applying InputClass "evdev keyboard catchall"
[203128.752] (II) Using input driver 'evdev' for 'Logitech Inc. Logitech USB Headset H340'
[203128.752] (**) Logitech Inc. Logitech USB Headset H340: always reports core events
[203128.752] (**) evdev: Logitech Inc. Logitech USB Headset H340: Device: "/dev/input/event6"
[203128.752] (--) evdev: Logitech Inc. Logitech USB Headset H340: Vendor 0x46d Product 0xa38
[203128.752] (--) evdev: Logitech Inc. Logitech USB Headset H340: Found 3 mouse buttons
[203128.752] (--) evdev: Logitech Inc. Logitech USB Headset H340: Found keys
[203128.752] (II) evdev: Logitech Inc. Logitech USB Headset H340: Forcing relative x/y axes to exist.
[203128.752] (II) evdev: Logitech Inc. Logitech USB Headset H340: Configuring as mouse
[203128.752] (II) evdev: Logitech Inc. Logitech USB Headset H340: Configuring as keyboard
[203128.752] (**) evdev: Logitech Inc. Logitech USB Headset H340: YAxisMapping: buttons 4 and 5
[203128.752] (**) evdev: Logitech Inc. Logitech USB Headset H340: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[203128.752] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.3/0003:046D:0A38.0034/input/input92/event6"
[203128.752] (II) XINPUT: Adding extended input device "Logitech Inc. Logitech USB Headset H340" (type: KEYBOARD, id 11)
[203128.752] (**) Option "xkb_rules" "evdev"
[203128.752] (**) Option "xkb_model" "pc105"
[203128.752] (**) Option "xkb_layout" "us"
This is the same whether the headset is on a USB hub, as it used to be, or not, as it was for the experiment. The only difference, now when I connect it (both directly and via hub) it does actually mess with the mouse behaviour, e.g. it's like a mouse button was continually pressed.

Meanwhile the headset is in fact detected as a sound device, too:

Code: Select all

$ cat /proc/asound/cards 
 0 [HDMI           ]: HDA-Intel - HDA Intel HDMI
                      HDA Intel HDMI at 0xf741c000 irq 49
 1 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xf7418000 irq 48
 2 [H340           ]: USB-Audio - Logitech USB Headset H340
                      Logitech Inc. Logitech USB Headset H340 at usb-0000:00:14.0-1, full speed
But I guess the other thing interferes?

User avatar
chrisra
Level 1
Level 1
Posts: 28
Joined: Wed Dec 30, 2015 1:39 pm

Re: Can't switch sound output to USB headset

Post by chrisra » Fri Jan 27, 2017 12:35 pm

This seems to be similar to
Although the former is a thread from 2012 and the latter is a bug with a fix released already for Precise (12.04), whereas 17.3 is based on Trusty. Still, I tried the suggestion linked to from the thread https://bbs.archlinux.org/viewtopic.php?id=127699:
Run lsusb to find your USB device vendor and product IDs. [...] Open up /etc/X11/xorg.conf [...]

Section "InputClass"
Identifier "Sennheiser OfficeRunner"
MatchUSBID "1395:740a"
Option "Ignore" "on"
EndSection

The Identifier string can be anything you want, although since we're blacklisting it, you'll never reference it. Put your USB vendor and product string into the MatchUSBID string. Restart X and you're done.
And that workaround solves the problem!

What I'd be interested in now: Where does the problem actually come from?

I hope you'll understand that only once that question is answered I'll consider the topic [SOLVED] :-) Thanks, everybody!

User avatar
phd21
Level 17
Level 17
Posts: 7273
Joined: Thu Jan 09, 2014 9:42 pm
Location: Florida

Re: Can't switch sound output to USB headset, is added as keyboard

Post by phd21 » Mon Jan 30, 2017 2:25 pm

Hi "chrisra",

FYI: There are some really nice graphical (GUI) programs for sound that start with "Qas", like the fantastic "Qasmixer", in the Software Manager or Synaptic Package Manager (SPM) that you can install and use. Depending upon your sound hardware, that can include settings for headsets. Also, I have found that for some reason on certain computer hardware that have audio jacks in front and in back, that sometimes the jacks work better either i the front jacks or the back jacks; for instance my microphone works in the front jack, but not the audio jacks in the back?

Sound "Mixers" can be a little confusing if you are not familiar with them. If you bring up "Qasmixer" and make it full screen, on the right side you will have mixer devices where you can control your system sound. If you do not see the mixer devices, hit "F6". The mixer item "sysdefault" will show all installed sound card devices, and you will have various options to adjust various volume controls using "sliders" which you can turn off and on using the "dot" below the volume slider. There are also various other check boxes below that you can use, and depending upon your sound card(s) that sometimes includes headphone checkboxes and or sliders as well, like "Headphone Jack Sense".

The applications included are:
- qasconfig - browser for the alsa configuration tree
- qashctl - mixer for alsa's high level control interface
- qasmixer - desktop mixer with features similar to alsamixer

Qasmixer is a desktop mixer application for alsa's "simple mixer interface" and offers features similar to alsamixer. it also features a sytem tray icon with basic mixer functionality.

Install "libasound2-plugin-equal" which is another system wide equalizer that's in the Software Manager or Synaptic Package Manager (SPM) that shows up in "QasMixer".

Hope this helps ...
Phd21: Mint KDE 17.3 & 18.3, 64-bit Awesome OS, Ancient Dell OptiPlex 780 Core2Duo E8400 3GHz,4gb Ram,256gb SDD, Video: Intel 4 Graphics, DVD Lightscribe. Why I use KDE?:https://opensource.com/life/15/4/9-reasons-to-use-kde

Post Reply

Return to “Hardware Support”