headset microphone is not recognized in headset-jack

Bug #1623804 reported by brandon211
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I'm using Ubuntu 16.04 on a Lenovo ThinkPad T450s. This notebook has a combined headphones/mic "headset"-jack as used by pretty much every smartphone nowadays.

I have a Plantronics-Headset HW251/A - SupraPlus Monaural and a 4-pin 3,5mm jack cable, made for use with PCs.

When connecting the headset to the notebook, I get audio but the mic is not recognized.

In contrast, when I boot Windows 7 on the same machine, the headset (including mic) works fine.
Moreover, the headset works fine connected to an Apple MacBook Air.

In contrast, I also have an Apple Earphones-Headset which came with an iPhone, this also works with the ThinkPad under Ubuntu.

By saying "not recognized", I mean that in the audio settings of Ubuntu, when plugging in the Plantronics headset, no audio input "microphone" comes up and the internal mic of the notebook is still used.
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: buerger 2021 F.... pulseaudio
 /dev/snd/controlC1: buerger 2021 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=21eeaf61-c437-45dc-80e3-e581eb6f795c
InstallationDate: Installed on 2015-09-15 (366 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20BX000XGE
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-36-generic N/A
 linux-backports-modules-4.4.0-36-generic N/A
 linux-firmware 1.157.3
Tags: xenial
Uname: Linux 4.4.0-36-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-04-22 (146 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 05/25/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET60WW (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BX000XGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrJBET60WW(1.24):bd05/25/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BX000XGE
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1623804/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
tags: added: kernel-sound
Revision history for this message
Paul White (paulw2u) wrote :
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1623804

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc6

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : CRDA.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : CurrentDmesg.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : IwConfig.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : JournalErrors.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : Lspci.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : Lsusb.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : ProcEnviron.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : ProcInterrupts.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : ProcModules.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : PulseList.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : RfKill.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : UdevDb.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote : WifiSyslog.txt

apport information

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote :

Yes, the problem persists with the now recent rc8.
But I made the following discovery:
The headset consists (like this is usual for this kind of headsets) of the headset itself with a cord ending in a QD-plug (quick disconnect) and I can then choose the cable I need for my purpose; for example, I also own a cable for my PBX desk phone.

My ThinkPad detects the headset mic if i connect solely the cable, disconnected from the headset first and then connect the headset via the QD-plug afterwards.

Again, on the same machine running Windows (7) and the other tested devices this problem doesn't occur.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote :

OK, seems that I have mixed up things a bit or the behavior is not 100% reproducible. Actually, it looks like the following:

- the headset mic is recognized fine when connected to the docking station headset jack
- when connecting to the notebook's internal headset jack, I need to do the above trick (regardless if the notebook is docked or undocked)

Revision history for this message
brandon211 (brandon211-deactivatedaccount-deactivatedaccount) wrote :

This behaviour persists with kernel 4.8.1

tags: added: kernel-bug-exists-upstream
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.