[Touch-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

2022-08-25 Thread hugh chao
got it, thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1981109

Title:
  server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
  every container

Status in fwupd package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  New
Status in fwupd source package in Jammy:
  Invalid
Status in livecd-rootfs source package in Jammy:
  Triaged
Status in modemmanager source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  Looking at memory utilization in a pristine Ubuntu lxd container (top
  -o RES), I see that ModemManager is running, which I was surprised to
  see is present at all in the stock image.

  Tracking this I find that fwupd depends on libmm-glib0, which in turn
  Recommends: modemmanager.

  Libraries in general should not recommend daemons, so it's possible
  this should be fixed by libmm-glib0 dropping this Recommends.  It
  certainly doesn't seem to be a deliberate decision by the Server Team
  to have modemmanager installed and running by default on all systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

2022-08-25 Thread hugh chao
Is this means fwupd will also be removed from stock server image?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1981109

Title:
  server image pulls in ModemManager via fwupd, consumes 25MiB RAM in
  every container

Status in fwupd package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  New
Status in fwupd source package in Jammy:
  Invalid
Status in livecd-rootfs source package in Jammy:
  Triaged
Status in modemmanager source package in Jammy:
  New
Status in ubuntu-meta source package in Jammy:
  New

Bug description:
  Looking at memory utilization in a pristine Ubuntu lxd container (top
  -o RES), I see that ModemManager is running, which I was surprised to
  see is present at all in the stock image.

  Tracking this I find that fwupd depends on libmm-glib0, which in turn
  Recommends: modemmanager.

  Libraries in general should not recommend daemons, so it's possible
  this should be fixed by libmm-glib0 dropping this Recommends.  It
  certainly doesn't seem to be a deliberate decision by the Server Team
  to have modemmanager installed and running by default on all systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1906653] Re: Backport systemd to make uevents "sticky"

2021-03-19 Thread hugh chao
@Dan

I see, thank you anyway :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1906653

Title:
  Backport systemd to make uevents "sticky"

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind"
  and "unbind" to the Linux device model which resulted in a number of
  software issues.

  So in this PR [1] which minimize issues resulting from this kernel
  change (but not avoid them entirely) by make uevent "sticky", meaning
  that once a tag is assigned to a device it will not be removed from
  the device again until the device itself is removed (i.e. unplugged).

  An example causing by this issue, I had a usb printer (non-ippusbxd)
  which connected to my laptop, but after unplugging it from my laptop,
  the .device unit were still present, if a different printer gets
  plugged to the same USB port then, it won't be configured correctly.

  [0] https://lwn.net/Articles/837033/
  [1] https://github.com/systemd/systemd/pull/16853/files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1906653] Re: Backport systemd to make uevents "sticky"

2020-12-03 Thread hugh chao
** Description changed:

  Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and
  "unbind" to the Linux device model which resulted in a number of
  software issues.
  
  So in this PR [1] which minimize issues resulting from this kernel
  change (but not avoid them entirely) by make uevent "sticky", meaning
  that once a tag is assigned to a device it will not be removed from the
  device again until the device itself is removed (i.e. unplugged).
  
+ An example causing by this issue, I had a usb printer (non-ippusbxd)
+ which connected to my laptop, but after unplugging it from my laptop,
+ the .device unit were still present, if a different printer gets plugged
+ to the same USB port then, it won't be configured correctly.
+ 
  [0] https://lwn.net/Articles/837033/
  [1] https://github.com/systemd/systemd/pull/16853/files

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1906653

Title:
  Backport systemd to make uevents "sticky"

Status in systemd package in Ubuntu:
  New

Bug description:
  Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind"
  and "unbind" to the Linux device model which resulted in a number of
  software issues.

  So in this PR [1] which minimize issues resulting from this kernel
  change (but not avoid them entirely) by make uevent "sticky", meaning
  that once a tag is assigned to a device it will not be removed from
  the device again until the device itself is removed (i.e. unplugged).

  An example causing by this issue, I had a usb printer (non-ippusbxd)
  which connected to my laptop, but after unplugging it from my laptop,
  the .device unit were still present, if a different printer gets
  plugged to the same USB port then, it won't be configured correctly.

  [0] https://lwn.net/Articles/837033/
  [1] https://github.com/systemd/systemd/pull/16853/files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1906653] [NEW] Backport systemd to make uevents "sticky"

2020-12-03 Thread hugh chao
Public bug reported:

Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and
"unbind" to the Linux device model which resulted in a number of
software issues.

So in this PR [1] which minimize issues resulting from this kernel
change (but not avoid them entirely) by make uevent "sticky", meaning
that once a tag is assigned to a device it will not be removed from the
device again until the device itself is removed (i.e. unplugged).

[0] https://lwn.net/Articles/837033/
[1] https://github.com/systemd/systemd/pull/16853/files

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind" and
  "unbind" to the Linux device model which resulted in a number of
  software issues.
  
- So in this PR [1] which minimize issues resulting from this kernel change 
(but not avoid them entirely) by make uevent "sticky", meaning that once a tag 
is assigned to a device it will not
- be removed from the device again until the device itself is removed (i.e. 
unplugged). 
- 
+ So in this PR [1] which minimize issues resulting from this kernel
+ change (but not avoid them entirely) by make uevent "sticky", meaning
+ that once a tag is assigned to a device it will not be removed from the
+ device again until the device itself is removed (i.e. unplugged).
  
  [0] https://lwn.net/Articles/837033/
  [1] https://github.com/systemd/systemd/pull/16853/files

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1906653

Title:
  Backport systemd to make uevents "sticky"

Status in systemd package in Ubuntu:
  New

Bug description:
  Base on lwn 837033 [0], Linux 4.12 introduced two new uevents "bind"
  and "unbind" to the Linux device model which resulted in a number of
  software issues.

  So in this PR [1] which minimize issues resulting from this kernel
  change (but not avoid them entirely) by make uevent "sticky", meaning
  that once a tag is assigned to a device it will not be removed from
  the device again until the device itself is removed (i.e. unplugged).

  [0] https://lwn.net/Articles/837033/
  [1] https://github.com/systemd/systemd/pull/16853/files

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1906653/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-23 Thread hugh chao
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1883846

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-23 Thread hugh chao
** Changed in: oem-priority
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1883846

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

2020-07-14 Thread hugh chao
current proposed version is 5.6.0.1020.17, let me wait for it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1883670

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883670/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-14 Thread hugh chao
** Tags removed: verification-needed verification-needed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1883846

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-14 Thread hugh chao
** Tags added: verification-needed-focal

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1883846

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-14 Thread hugh chao
** Changed in: oem-priority
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1883846

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

2020-07-04 Thread hugh chao
I will verify alsa-lib - 1.2.2-2.3ubuntu1 with oem 1019 kernel next
week.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1883670

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883670/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

2020-06-17 Thread hugh chao
** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => hugh chao (hugh712)

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1883670

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883670/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-06-02 Thread hugh chao
sorry, I shouldn't use such unclear word,
I did check the version with Danny yesterday,
pulseaudio version 1:11.1-1ubuntu7.8 works well at the same machine.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-06-02 Thread hugh chao
it's 1:11.1-1ubuntu7.8 in #40, I think it's a typo

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-05-05 Thread hugh chao
need to finish this one[0] first

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-05-05 Thread hugh chao
currently, @kai is working on the new patch..

** Changed in: pulseaudio (Ubuntu Bionic)
   Status: Fix Committed => In Progress

** Tags added: regression-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-05-01 Thread hugh chao
@Kai,

What do you think on #21, it's a regression or not?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-05-01 Thread hugh chao
For what I observed (both focal and bionic), I'm not sure (and I think
it's not) it's a regression, due the the bug it's already there before
this patch. And I tried one hp dm, one hp sff, one hp laptop and one
dell laptop, only can be reproduced in Dell laptop.

For what I observed:

[[[1:11.1-1ubuntu7.5]]]
Before I plugged headset there is only one device shown on input device, which 
is 

1. Internal Microphone - Built-in Audio

After I plugged headset into the jack, dialog shown up, I choice
"headset", then three input device shown up, which are:

1. Headset Microphone - Built-in Audio
2. Internal Microphone - Built-in Audio
3. Microphone - Built-in Audio

[[[1:11.1-1ubuntu7.6]]] 
Before I plugged headset there are two devices shown on input device, which are 

1. Headset Microphone - Built-in Audio
2. Internal Microphone - Built-in Audio

After I plugged headset into the jack, dialog shown up, I choice
"headset", then three input device shown up, which are:

1. Headset Microphone - Built-in Audio
2. Internal Microphone - Built-in Audio
3. Microphone - Built-in Audio

[[[result]]]
No matter which cases, once you choice (3. Microphone - Built-in Audio), then 
there is no headset output audio. Select others, the audio output came back.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-30 Thread hugh chao
@Kai,

Please help to take a look on #18,
then let's decide next step, thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-24 Thread hugh chao
verified pulseaudio version - 1:11.1-1ubuntu7.6 in a dell laptop[0]
which only has one headset jack, works well, didn't find any Regression
potential.

[0] https://www.dell.com/en-us/work/shop/dell-laptops-and-
notebooks/latitude-5501-business-laptop/spd/latitude-15-5501-laptop

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-24 Thread hugh chao
verified pulseaudio version - 1:11.1-1ubuntu7.6 in a hp dm[0] which has
dual front jacks, works well, didn't find any Regression potential.

[0]https://www8.hp.com/h20195/v2/GetPDF.aspx/4AA7-5436EEAP.pdf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-24 Thread hugh chao
verified pulseaudio version - 1:11.1-1ubuntu7.6 in a hp sff[0] which has
dual front jacks, works well, didn't find any Regression potential.


[0]https://www8.hp.com/h20195/v2/GetPDF.aspx/4AA7-5395EEAP.pdf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-10 Thread hugh chao
@Seb

Sorry for the inconvenience, I will be more careful next time,
thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-08 Thread hugh chao
here you go,
upload patch for bionic again in debian/patches

** Patch added: "dual-jacks.patch"
   
https://bugs.launchpad.net/oem-priority/+bug/1869819/+attachment/5350081/+files/dual-jacks.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-08 Thread hugh chao
upload patch for bionic

** Patch added: "dual-jacks-bionic.patch"
   
https://bugs.launchpad.net/oem-priority/+bug/1869819/+attachment/5349710/+files/dual-jacks-bionic.patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-08 Thread hugh chao
** Changed in: pulseaudio (Ubuntu Bionic)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-07 Thread hugh chao
upload patch for focal

** Patch added: "dual-jacks.patch"
   
https://bugs.launchpad.net/oem-priority/+bug/1869819/+attachment/5348635/+files/dual-jacks.patch

** Tags added: verification-needed

** Changed in: pulseaudio (Ubuntu Focal)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-04-01 Thread hugh chao
** Description changed:

  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.
  
  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output
  
  [Expected result]
  Can detect external headset
  
  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.
  
  [Regression Potential]
  Low.
  
  [Failure rate]
  100%
  
  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2
  
  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272
+ 
+ PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

** Description changed:

  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.
  
  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output
  
  [Expected result]
  Can detect external headset
  
  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.
  
  [Regression Potential]
  Low.
  
  [Failure rate]
  100%
  
  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2
  
  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272
  
+ Ubuntu-Focal-Source:
+ 
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819
+ 
  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-03-31 Thread hugh chao
I think 3 stripes = 4 rings, and we are talking the same thing, I will
make it more clear

** Description changed:

  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.
  
  [Test Case]
- 1. Insert 3-ring headset into front audio port (headset icon)
+ 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output
  
  [Expected result]
  Can detect external headset
  
  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.
  
  [Regression Potential]
  Low.
  
  [Failure rate]
  100%
  
  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2
  
  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] [NEW] System can't detect external headset in the codec of Conexant

2020-03-30 Thread hugh chao
Public bug reported:

[Impact]
In some hp's devices, there are two audio jacks(one headset and one headphone) 
in the audio interface which is using the codec of Conexant, and apparently 
it's not working, the system can't detect the headset in current codec.

[Test Case]
1. Insert 3-ring headset into front audio port (headset icon)
2. Check System Setting->Sound->Output

[Expected result]
Can detect external headset

[Actual result]
Only shows internal speaker.
External headset microphone was detected.
Another front audio port (earphone icon) works fine.

[Regression Potential]

[Failure rate]
100%

[Additional information]
system-product-name: HP EliteDesk 800 G5 SFF
CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
OS-version: 18.04
kernel-version: 4.15.0-1065-oem
pulseaudio-version: 1:11.1-1ubuntu7.2

Upstream Bug:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

** Affects: oem-priority
 Importance: Critical
     Assignee: hugh chao (hugh712)
 Status: Confirmed

** Affects: oem-priority/bionic
 Importance: Undecided
 Status: New

** Package changed: pulseaudio (Ubuntu) => oem-priority

** Changed in: oem-priority
 Assignee: (unassigned) => hugh chao (hugh712)

** Also affects: oem-priority/bionic
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1869819

Title:
  System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 3-ring headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream Bug:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined

2020-03-17 Thread hugh chao
even in building ubiquity it will fail in :

(run:75635): Gtk-WARNING **: 23:32:02.334: Could not load a pixbuf from icon 
theme.
This may indicate that pixbuf loaders or the mime database could not be found.
Exception in GTK frontend (invoking crash handler):
Traceback (most recent call last):
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__
self.view = NetworkManagerTreeView(self.state_changed)
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__
self.configure_icons()
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in 
configure_icons
ico = ico.load_icon()
gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
 (0)

Traceback (most recent call last):
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__
self.view = NetworkManagerTreeView(self.state_changed)
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__
self.configure_icons()
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in 
configure_icons
ico = ico.load_icon()
gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201 (3) 
in (null):40:466: Namespace prefix sodipodi on namedview is not defined
 (0)
xauth/Xrdb output:

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1867766

Title:
  Namespace prefix sodipodi on namedview is not defined

Status in librsvg package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  [Summary]
  Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 
to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log.

  [Steps to reproduce]
  1. Boot with OEM mode,
  2. Finish the 1st stage
  3. Reboot
  4. Boot into OOBE(oem-config)

  [Expected result]
  Should start oobe without any error.

  [Actual result]
  The error message 『The installer encountered an unrecoverable error. A 
desktop session will now be run so that you may investigate the problem or try 
installing again.』shown on the screen.

  [Failure rate]
  100%

  [Additional information]
  No idea why, but some "nm-signal-*-secure" images will fail in 
Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will 
show:

  "
  Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme.
  This may indicate that pixbuf loaders or the mime database could not be found.
  gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
  "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined

2020-03-17 Thread hugh chao
even in build ubiquity it will failed in :

(run:75635): Gtk-WARNING **: 23:32:02.334: Could not load a pixbuf from icon 
theme.
This may indicate that pixbuf loaders or the mime database could not be found.
Exception in GTK frontend (invoking crash handler):
Traceback (most recent call last):
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__
self.view = NetworkManagerTreeView(self.state_changed)
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__
self.configure_icons()
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in 
configure_icons
ico = ico.load_icon()
gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
 (0)

Traceback (most recent call last):
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 330, in __init__
self.view = NetworkManagerTreeView(self.state_changed)
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 96, in __init__
self.configure_icons()
  File "./ubiquity/frontend/gtk_components/nmwidgets.py", line 196, in 
configure_icons
ico = ico.load_icon()
gi.repository.GLib.Error: rsvg-error-quark: XML parse error: error code=201 (3) 
in (null):40:466: Namespace prefix sodipodi on namedview is not defined
 (0)
xauth/Xrdb output:

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1867766

Title:
  Namespace prefix sodipodi on namedview is not defined

Status in librsvg package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  [Summary]
  Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 
to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log.

  [Steps to reproduce]
  1. Boot with OEM mode,
  2. Finish the 1st stage
  3. Reboot
  4. Boot into OOBE(oem-config)

  [Expected result]
  Should start oobe without any error.

  [Actual result]
  The error message 『The installer encountered an unrecoverable error. A 
desktop session will now be run so that you may investigate the problem or try 
installing again.』shown on the screen.

  [Failure rate]
  100%

  [Additional information]
  No idea why, but some "nm-signal-*-secure" images will fail in 
Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will 
show:

  "
  Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme.
  This may indicate that pixbuf loaders or the mime database could not be found.
  gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
  "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined

2020-03-17 Thread hugh chao
" lsb_release -rd

Description:Ubuntu Focal Fossa (development branch)
Release:20.04

"apt-cache policy gir1.2-rsvg-2.0

gir1.2-rsvg-2.0:
  Installed: 2.48.0-1
  Candidate: 2.48.0-1
  Version table:
 *** 2.48.0-1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 file:  Packages
500 file:  Packages
500 file:  Packages
500 file:  Packages
500 file:  Packages
500 file:  Packages
500 file:  Packages
100 /var/lib/dpkg/status
 2.46.4-1ubuntu1 500
500 file:  Packages
500 file:  Packages
500 file:  Packages
500 file:  Packages
500 file:  Packages
500 file:  Packages
500 file:  Packages

** Tags added: oem-priority

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/1867766

Title:
  Namespace prefix sodipodi on namedview is not defined

Status in librsvg package in Ubuntu:
  New

Bug description:
  [Summary]
  Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 
to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log.

  [Steps to reproduce]
  1. Boot with OEM mode,
  2. Finish the 1st stage
  3. Reboot
  4. Boot into OOBE(oem-config)

  [Expected result]
  Should start oobe without any error.

  [Actual result]
  The error message 『The installer encountered an unrecoverable error. A 
desktop session will now be run so that you may investigate the problem or try 
installing again.』shown on the screen.

  [Failure rate]
  100%

  [Additional information]
  No idea why, but some "nm-signal-*-secure" images will fail in 
Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will 
show:

  "
  Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme.
  This may indicate that pixbuf loaders or the mime database could not be found.
  gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
  "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1867766] [NEW] Namespace prefix sodipodi on namedview is not defined

2020-03-17 Thread hugh chao
Public bug reported:

[Summary]
Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to 
2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log.

[Steps to reproduce]
1. Boot with OEM mode,
2. Finish the 1st stage
3. Reboot
4. Boot into OOBE(oem-config)

[Expected result]
Should start oobe without any error.

[Actual result]
The error message 『The installer encountered an unrecoverable error. A desktop 
session will now be run so that you may investigate the problem or try 
installing again.』shown on the screen.

[Failure rate]
100%

[Additional information]
No idea why, but some "nm-signal-*-secure" images will fail in 
Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will 
show:

"
Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
"

** Affects: librsvg (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "_usr_lib_ubiquity_bin_ubiquity.0.crash"
   
https://bugs.launchpad.net/bugs/1867766/+attachment/5337963/+files/_usr_lib_ubiquity_bin_ubiquity.0.crash

** Summary changed:

- gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
+ Namespace prefix sodipodi on namedview is not defined

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/1867766

Title:
  Namespace prefix sodipodi on namedview is not defined

Status in librsvg package in Ubuntu:
  New

Bug description:
  [Summary]
  Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 
to 2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log.

  [Steps to reproduce]
  1. Boot with OEM mode,
  2. Finish the 1st stage
  3. Reboot
  4. Boot into OOBE(oem-config)

  [Expected result]
  Should start oobe without any error.

  [Actual result]
  The error message 『The installer encountered an unrecoverable error. A 
desktop session will now be run so that you may investigate the problem or try 
installing again.』shown on the screen.

  [Failure rate]
  100%

  [Additional information]
  No idea why, but some "nm-signal-*-secure" images will fail in 
Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will 
show:

  "
  Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme.
  This may indicate that pixbuf loaders or the mime database could not be found.
  gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201 
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
  "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp