[Bug 1882248] [NEW] plug headset won't proper reconfig ouput to it on machine with default output

Launchpad Bug Tracker 1882248 at bugs.launchpad.net
Thu Jul 9 07:47:21 UTC 2020


You have been subscribed to a public bug by Hui Wang (hui.wang):

For linux kernel (oem-b):

[Impact]
On a Dell machine without internal spk and internal mic, after freshly
install the bionic on it, and users plug a headset, the sound couldn't
output from headset.

[Fix]
reverse the order of headset mic and headphone mic

[Test Case]
freshly install the bionic with this patch on that dell machine,
plug headset and play sound, we could hear the sound from headset.

[Regression Risk]
Low, this patch only affects the machine without internal mic and
internal spk, and I already tested this patch on the machine without
internal mic and internal spk, it worked well.



target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA)

As first boot, there will be a "dummy output" in g-c-c.

After plug-in headset, there will be a headset appear in g-c-c, but it
won't be automatically selected even it's chosen in the pop-up window.

** Affects: hwe-next
     Importance: Undecided
         Status: New

** Affects: oem-priority
     Importance: Critical
     Assignee: Yuan-Chen Cheng (ycheng-twn)
         Status: Confirmed

** Affects: linux-oem (Ubuntu)
     Importance: Undecided
     Assignee: Hui Wang (hui.wang)
         Status: New

** Affects: pulseaudio (Ubuntu)
     Importance: Undecided
     Assignee: Hui Wang (hui.wang)
         Status: New

** Affects: linux-oem (Ubuntu Bionic)
     Importance: Undecided
         Status: Fix Committed

** Affects: pulseaudio (Ubuntu Bionic)
     Importance: Critical
     Assignee: Hui Wang (hui.wang)
         Status: New


** Tags: bionic oem-priority originate-1881842 originate-from-1881842 somerville
-- 
plug headset won't proper reconfig ouput to it on machine with default output
https://bugs.launchpad.net/bugs/1882248
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list