[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

[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

[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

[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)

[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

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

2020-07-24 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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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]

[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

[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

[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:

[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

[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:

[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

[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

[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

[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,

[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

[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

[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

[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

[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

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

2020-03-30 Thread hugh chao
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 Statu

[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):

[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):

[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

[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)