[Bug 1884251] Re: Support Audio Mute LED for two new HP laptops
Verified with kernel linux-image-unsigned-5.6.0-1013-oem in one of the hp laptops, works well and can't find any regression. ** Tags added: verification-done-foca ** Tags removed: verification-done-foca ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884251 Title: Support Audio Mute LED for two new HP laptops To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1884251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884251] Re: Support Audio Mute LED for two new HP laptops
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => hugh chao (hugh712) ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884251 Title: Support Audio Mute LED for two new HP laptops To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1884251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883670 Title: Disable IEC958 on HP Thunderbolt Dock To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882347] Re: [MIR] oem-stella.cmit-abra-meta
** Changed in: oem-priority Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882347 Title: [MIR] oem-stella.cmit-abra-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882347] Re: [MIR] oem-stella.cmit-abra-meta
@Dimitri 1. http://hp.archive.canonical.com/dists/focal/stella is ready 2. The -oem packaging branch already pushed to the repo 3. [oem-archive] oem-stella.cmit-abra-meta (20.04ubuntu3) is already on http://oem.archive.canonical.com/updates/dists/focal/stella.cmit/ [ubuntu-archive] oem-stella.cmit-abra-meta (20.04~ubuntu2) is on my ppa I have everything now, please help with next step, thanks :) ** Changed in: ubuntu Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882347 Title: [MIR] oem-stella.cmit-abra-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Verified this issue with two combinations 1. linux-oem-20.04(5.6.0-1011-oem) + alsa-ucm-conf 1.2.2-1ubuntu0.1 2. linux-generic (5.4.0.38.41)(still in proposed channel) + alsa-ucm-conf 1.2.2-1ubuntu0.1 didn't find any potential regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Verified this issue with two combinations 1. linux-oem-20.04(5.6.0-1011-oem) + alsa-ucm-conf 1.2.2-1ubuntu0.1 2. linux-generic (5.4.0.38.41)(still in proposed channel) + alsa-ucm-conf 1.2.2-1ubuntu0.1 can actually fix this issue, and I didn't find any regression. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal ** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
@Welly, please enable proposed channel first [0], then run below command, # sudo apt install linux-generic alsa-ucm-conf reboot and give it a try [0] https://wiki.ubuntu.com/Testing/EnableProposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
GA kernel 5.4.0.38.41 is in proposed channel now, I will verify it with alsa-ucm-conf 1.2.2-1ubuntu0.1 soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882347] Re: [MIR] oem-stella.cmit-abra-meta
@Dimitri 1. http://hp.archive.canonical.com/dists/focal/stella is ready 2. oem-stella.cmit-abra-meta (20.04ubuntu3) is already on http://oem.archive.canonical.com/updates/dists/focal/stella.cmit/ 3. oem-stella.cmit-abra-meta (20.04~ubuntu2) is on my ppa, I have everything now, please help with next step, thanks :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882347 Title: [MIR] oem-stella.cmit-abra-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
ok, let's wait until 5.4.0-38 in proposed and I will give it a try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
** Changed in: oem-priority Assignee: (unassigned) => hugh chao (hugh712) ** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
which GA kernel do I need to verify? I tried the combination of oem-linux-20.04(5.6.0-1010-oem) + alsa-ucm-conf 1.2.2-1ubuntu0.1, the result is passed, but GA kernel (5.4.0-37) + alsa-ucm-conf 1.2.2-1ubuntu0.1 failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
is it any chance to land alsa-ucm-conf into focal this week? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882347] [NEW] [MIR] oem-stella.cmit-abra-meta
Public bug reported: [Availability] This is a pilot running meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. oem-stella.cmit-abra-meta 20.04~ubuntu1 for focal in ppa:hugh712/+archive/ubuntu/staging-ubuntu-metapkg-ppa [Rationale] We want to improve the hardware support for HP 285 G3 Microtower PC on focal. [Security] No CVE/known security issue. [Quality assurance] I have used hugh712/+archive/ubuntu/staging-ubuntu-metapkg-ppa to check this package on HP 285 G3 Microtower PC and it works as expected. oem-stella.cmit-abra-meta will be upgraded to 20.04ubuntu1 from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. ** Affects: oem-priority Importance: High Assignee: hugh chao (hugh712) Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Information type changed from Proprietary to Public ** Changed in: oem-priority Assignee: (unassigned) => hugh chao (hugh712) ** Changed in: oem-priority Importance: Undecided => High ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882347 Title: [MIR] oem-stella.cmit-abra-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1882347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Tags added: sutton -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Tags added: oem-priority stella -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
** Tags added: stella -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864426] Re: [SRU][live-build] can not customize the mkisoimage option
** Changed in: oem-priority Status: Fix Committed => Fix Released ** Changed in: oem-priority/focal Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864426 Title: [SRU][live-build] can not customize the mkisoimage option To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864426] Re: [SRU][live-build] can not customize the mkisoimage option
tried to build the oem image with this version and below config ISOHYBRID_OPTIONS="--uefi" GENISOIMAGE_OPTIONS_EXTRA="-eltorito-alt-boot -efi-boot boot/grub/efi.img -no-emul-boot -joliet-long" there are two partitions in the images and can boot from the usb sticker correctly. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864426 Title: [SRU][live-build] can not customize the mkisoimage option To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864426] Re: [SRU][live-build] can not customize the mkisoimage option
** Description changed: [Impact] Although live build has been used in both oem and foundation team, but the main different is that: --Foundation-- - Only for squashfs, cd-image will be used after that, the image created by live build will not be used directly. + Only for squashfs, cd-image will be used after that, the iso image created by live build will not be used directly. --OEM-- Oem team uses live build in whole process which includes several binary hooks, and the final image created by live build will be used directly. - So the problem is that currently the image which created by live build doesn't support uefi boot, + So the problem is that currently the iso image which created by live build doesn't support uefi boot, so when we build a support uefi bootable image, the mkisoimage needs extra options. [Test Case] With below options in any live build config (oem team put it in /common), an uefi bootable image can be built. ISOHYBRID_OPTIONS="--uefi" GENISOIMAGE_OPTIONS_EXTRA="-eltorito-alt-boot -efi-boot boot/grub/efi.img -no-emul-boot -joliet-long" [Regression Potential] Low, oem team has been using this patch for years (since from 2012), we haven't found any potential regression. ** Description changed: [Impact] Although live build has been used in both oem and foundation team, but the main different is that: --Foundation-- Only for squashfs, cd-image will be used after that, the iso image created by live build will not be used directly. --OEM-- Oem team uses live build in whole process which includes several binary hooks, and the final image created by live build will be used directly. So the problem is that currently the iso image which created by live build doesn't support uefi boot, so when we build a support uefi bootable image, the mkisoimage needs extra options. [Test Case] With below options in any live build config (oem team put it in /common), an uefi bootable image can be built. ISOHYBRID_OPTIONS="--uefi" GENISOIMAGE_OPTIONS_EXTRA="-eltorito-alt-boot -efi-boot boot/grub/efi.img -no-emul-boot -joliet-long" [Regression Potential] - Low, oem team has been using this patch for years (since from 2012), + Low, oem team has been using this patch for years (from 2012), we haven't found any potential regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864426 Title: [SRU][live-build] can not customize the mkisoimage option To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864426] Re: [SRU][live-build] can not customize the mkisoimage option
** Description changed: + [Impact] + Although live build has been used in both oem and foundation team, but the main different is that: - [Foundation] + --Foundation-- Only for squashfs, cd-image will be used after that, the image created by live build will not be used directly. - [OEM] + --OEM-- Oem team uses live build in whole process which includes several binary hooks, and the final image created by live build will be used directly. So the problem is that currently the image which created by live build doesn't support uefi boot, so when we build a support uefi bootable image, the mkisoimage needs extra options. + + [Test Case] + With below options in any live build config (oem team put it in /common), a. uefi bootable image can be built. + + ISOHYBRID_OPTIONS="--uefi" + GENISOIMAGE_OPTIONS_EXTRA="-eltorito-alt-boot -efi-boot boot/grub/efi.img -no-emul-boot -joliet-long" + + [Regression Potential] + Low, oem team has been using this patch for years (since from 2012), + we haven't found any potential regression. ** Description changed: [Impact] Although live build has been used in both oem and foundation team, but the main different is that: --Foundation-- Only for squashfs, cd-image will be used after that, the image created by live build will not be used directly. --OEM-- Oem team uses live build in whole process which includes several binary hooks, and the final image created by live build will be used directly. So the problem is that currently the image which created by live build doesn't support uefi boot, so when we build a support uefi bootable image, the mkisoimage needs extra options. [Test Case] - With below options in any live build config (oem team put it in /common), a. uefi bootable image can be built. + With below options in any live build config (oem team put it in /common), an uefi bootable image can be built. ISOHYBRID_OPTIONS="--uefi" GENISOIMAGE_OPTIONS_EXTRA="-eltorito-alt-boot -efi-boot boot/grub/efi.img -no-emul-boot -joliet-long" [Regression Potential] Low, oem team has been using this patch for years (since from 2012), we haven't found any potential regression. ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864426 Title: [SRU][live-build] can not customize the mkisoimage option To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864426] Re: [SRU][live-build] can not customize the mkisoimage option
upload debdiff for focal ** Summary changed: - [live-build] can not customize the mkisoimage option + [SRU][live-build] can not customize the mkisoimage option ** Patch added: "3.0~a57-1ubuntu39.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1864426/+attachment/5373472/+files/3.0~a57-1ubuntu39.debdiff ** Changed in: oem-priority Status: Confirmed => In Progress ** Changed in: oem-priority/focal Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864426 Title: [SRU][live-build] can not customize the mkisoimage option To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864426] Re: [live-build] can not customize the mkisoimage option
** Description changed: - When we build a support uefi bootable image, the mkisoimage needs extra options. - But, in live-build 3, the option of mkisoimage is fixed and can not be customized. + Although live build has been used in both oem and foundation team, but + the main different is that: + + [Foundation] + Only for squashfs, cd-image will be used after that, the image created by live build will not be used directly. + + [OEM] + Oem team uses live build in whole process which includes several binary hooks, and the final image created by live build will be used directly. + + So the problem is that currently the image which created by live build doesn't support uefi boot, + so when we build a support uefi bootable image, the mkisoimage needs extra options. ** Also affects: oem-priority/focal Importance: Undecided Status: New ** Changed in: oem-priority/focal Assignee: (unassigned) => hugh chao (hugh712) ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority/focal Status: New => Confirmed ** Changed in: oem-priority/focal Importance: Undecided => High ** Information type changed from Proprietary to Public ** Also affects: live-build (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864426 Title: [live-build] can not customize the mkisoimage option To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
@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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
** Changed in: pulseaudio (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868701] Re: need to implement a reboot mechanism before oobe
Verified with newest ubiquity 20.04.7, system actually rebooted after OOBE and works well. ** Changed in: oem-priority Status: Triaged => Fix Committed ** Changed in: ubiquity (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868701 Title: need to implement a reboot mechanism before oobe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869819] [NEW] System can't detect external headset in the codec of Conexant
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869819 Title: System can't detect external headset in the codec of Conexant To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868701] Re: need to implement a reboot mechanism before oobe
** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868701 Title: need to implement a reboot mechanism before oobe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865161] Re: Written "press return to shutdown the computer" does not appear.
seems after the installation, still can't use "plymouth dispaly-message" to send the text in desktop environment, maybe we can just debug in desktop enviroment... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865161 Title: Written "press return to shutdown the computer" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865161] Re: Written "press return to shutdown the computer" does not appear.
upload casper-stop log ** Attachment added: "casper-stop.log" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+attachment/5342111/+files/casper-stop.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865161 Title: Written "press return to shutdown the computer" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865161] Re: Written "press return to shutdown the computer" does not appear.
plymouthd is in interruptible sleep state as: @sbin/plymouthd --mode=reboot --attach-to-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865161 Title: Written "press return to shutdown the computer" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] UbiquitySyslog.txt
apport information ** Attachment added: "UbiquitySyslog.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342072/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342070/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342069/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342071/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] Re: The background is black in whole ubiquity session
apport information ** Tags added: apport-collected focal ubuntu ** Description changed: [Summary] Since focal daily build - 3/25, the background in ubiquity become black + vendor+Ubuntu icons(same as plymouth spinner theme), and also I can reproduce this issue in 3/26 daily build. [Steps to reproduce] 1. Boot the installer with USB sticker 2. Select Install Ubuntu 3. Waiting for the interactive page shown up. [Expected result] The background with focal theme. [Actual result] The background is whole black. [Failure rate] 100% [Additional information] " lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu21 + Architecture: amd64 + CasperVersion: 1.441 + DistroRelease: Ubuntu 20.04 + InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash --- + LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200325) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: ubiquity 20.04.6 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 + Tags: focal ubuntu + Uname: Linux 5.4.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Casper.txt" https://bugs.launchpad.net/bugs/1869331/+attachment/5342068/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] Re: The background is black in whole ubiquity session
unexpected theme (since from 3/25 daily build) ** Attachment added: "Screenshot from 2020-03-27 17-00-03.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+attachment/5342066/+files/Screenshot%20from%202020-03-27%2017-00-03.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] Re: The background is black in whole ubiquity session
expected theme (3/24 daily build) ** Attachment added: "Screenshot from 2020-03-27 16-57-27.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+attachment/5342065/+files/Screenshot%20from%202020-03-27%2016-57-27.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869331] [NEW] The background is black in whole ubiquity session
Public bug reported: [Summary] Since focal daily build - 3/25, the background in ubiquity become black + vendor+Ubuntu icons(same as plymouth spinner theme), and also I can reproduce this issue in 3/26 daily build. [Steps to reproduce] 1. Boot the installer with USB sticker 2. Select Install Ubuntu 3. Waiting for the interactive page shown up. [Expected result] The background with focal theme. [Actual result] The background is whole black. [Failure rate] 100% [Additional information] " lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869331 Title: The background is black in whole ubiquity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865161] Re: Written "press return to shutdown the computer" does not appear.
I tried to add systemd.debug-shell=1, and switched to tty9 when the installation was done and switched back to tty1, then the message "Please remove the installation medium,then reboot" shown up. Next step, I tried to send message via "plymouth message --text= ", but the messages didn't be updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865161 Title: Written "press return to shutdown the computer" does not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1865161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868260] Re: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement
** Changed in: oem-priority Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868260 Title: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868260] Re: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement
Ok, I will override the setting in oem base image, thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868260 Title: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Re: plymouth spinner can not show the messages after installation.
*** This bug is a duplicate of bug 1865161 *** https://bugs.launchpad.net/bugs/1865161 @Danial Yes it's with logos, I just update the bug description for #16, and it seems the same issue as #18, even I keep waiting for 5 mins, the message still not shows up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymouth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Re: plymouth spinner can not show the messages after installation.
*** This bug is a duplicate of bug 1865161 *** https://bugs.launchpad.net/bugs/1865161 ** Description changed: [Summary] Before 20.04, when user finished the 1st stage of installation, the message 『please remove the installation medium then reboot』or 『please remove installation medium then press enter』 will be shown on the screen. But since 20.04, due to the using of plymouth-themes-spinner, the system will still waiting for user to press Enter but without any message, so the system will be likely hanged there. [Steps to reproduce] 1. Boot the installer with USB sticker 2. Finish the installation. 3. Click the button on the diagram to reboot. [Expected result] System reboot and boot to login page. [Actual result] - Black screen and need to press "Enter" to reboot. + Black screen (With vendor and ubuntu logo) and need to press "Enter" to reboot. [Failure rate] 100% [Additional information] " lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 "apt-cache policy plymouth-theme-spinner plymouth-theme-spinner: Installed: 0.9.4git20200109-0ubuntu8 Candidate: 0.9.4git20200109-0ubuntu8 Version table: *** 0.9.4git20200109-0ubuntu8 100 100 /var/lib/dpkg/status - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: Dell Inc. Latitude 5501 Package: plymouth 0.9.4git20200109-0ubuntu8 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ed9c1d0b-cfe3-4860-b83e-d2a80d0c0223 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ed9c1d0b-cfe3-4860-b83e-d2a80d0c0223 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Tags: focal TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 018CA2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn018CA2:rvrX02:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5501 dmi.product.sku: 0919 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymouth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868701] Re: need to implement a reboot mechanism before oobe
https://code.launchpad.net/~hugh712/ubiquity/+git/ubiquity/+merge/380808 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868701 Title: need to implement a reboot mechanism before oobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1868701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868701] [NEW] need to implement a reboot mechanism before oobe
Public bug reported: Some oem projects preload workaround(configuration/dkms/firmware) in the image, and it need a reboot to take effect in OOBE(oem-config) stage, but current ubiquity doesn't support this feature.. https://code.launchpad.net/~hugh712/ubiquity/+git/ubiquity/+merge/380808 [test case] 1. Boot to "OEM install (for manufactures)" with usb sticker. 2. Finish the 1st configuration(default settings) and start to install the system. 3. Finish the installation and reboot. 4. Login to the desktpop. 5. CLick "Prepare for shipping to en..." on the desktop. 6. Reboot after the dialog "oem-config will run the next time the system boots" be shown. 7. Reboot. 8. Finish the 2nd configuration(oem-config), just use default settings. 9. Let the system finish the configuration and apply changes. 10. With this patch system will reboot after (9) or it will just go to login page. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868701 Title: need to implement a reboot mechanism before oobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1868701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338363/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338364/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338367/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338366/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338371/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338362/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338368/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338370/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338360/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338369/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338365/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] EtcDefaultGrub.txt
apport information ** Attachment added: "EtcDefaultGrub.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338361/+files/EtcDefaultGrub.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Re: plymoth spinner can not show the messages after installation.
apport information ** Tags added: apport-collected focal ** Description changed: [Summary] Before 20.04, when user finished the 1st stage of installation, the message 『please remove the installation medium then reboot』or 『please remove installation medium then press enter』 will be shown on the screen. But since 20.04, due to the using of plymouth-themes-spinner, the system will still waiting for user to press Enter but without any message, so the system will be likely hanged there. [Steps to reproduce] 1. Boot the installer with USB sticker 2. Finish the installation. 3. Click the button on the diagram to reboot. [Expected result] System reboot and boot to login page. [Actual result] Black screen and need to press "Enter" to reboot. [Failure rate] 100% [Additional information] " lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 "apt-cache policy plymouth-theme-spinner plymouth-theme-spinner: Installed: 0.9.4git20200109-0ubuntu8 Candidate: 0.9.4git20200109-0ubuntu8 Version table: *** 0.9.4git20200109-0ubuntu8 100 100 /var/lib/dpkg/status + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu20 + Architecture: amd64 + BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' + DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-03-18 (0 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) + MachineType: Dell Inc. Latitude 5501 + Package: plymouth 0.9.4git20200109-0ubuntu8 + PackageArchitecture: amd64 + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ed9c1d0b-cfe3-4860-b83e-d2a80d0c0223 ro quiet splash vt.handoff=7 + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ed9c1d0b-cfe3-4860-b83e-d2a80d0c0223 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 + Tags: focal + TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth + Uname: Linux 5.4.0-14-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/21/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.5.1 + dmi.board.name: 018CA2 + dmi.board.vendor: Dell Inc. + dmi.board.version: X02 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn018CA2:rvrX02:cvnDellInc.:ct10:cvr: + dmi.product.family: Latitude + dmi.product.name: Latitude 5501 + dmi.product.sku: 0919 + dmi.sys.vendor: Dell Inc. ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1867909/+attachment/5338359/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Re: plymoth spinner can not show the messages after installation.
** Description changed: [Summary] Before 20.04, when user finished the 1st stage of installation, the message 『please remove the installation medium then reboot』or 『please remove installation medium then press enter』 will be shown on the screen. But since 20.04, due to the using of plymouth-themes-spinner, the system will still waiting for user to press Enter but without any message, so the system will be likely hanged there. [Steps to reproduce] 1. Boot the installer with USB sticker 2. Finish the installation. 3. Click the button on the diagram to reboot. [Expected result] System reboot and boot to login page. [Actual result] Black screen and need to press "Enter" to reboot. [Failure rate] 100% [Additional information] " lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 "apt-cache policy plymouth-theme-spinner plymouth-theme-spinner: - Installed: 0.9.4git20200109-0ubuntu8 - Candidate: 0.9.4git20200109-0ubuntu8 - Version table: - *** 0.9.4git20200109-0ubuntu8 100 - 100 /var/lib/dpkg/status + Installed: 0.9.4git20200109-0ubuntu8 + Candidate: 0.9.4git20200109-0ubuntu8 + Version table: + *** 0.9.4git20200109-0ubuntu8 100 + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] Re: plymoth spinner can not show the messages after installation.
** Description changed: [Summary] Before 20.04, when user finished the 1st stage of installation, the message 『please remove the installation medium then reboot』or 『please remove installation medium then press enter』 will be shown on the screen. But since 20.04, due to the using of plymouth-themes-spinner, the system will still waiting for user to press Enter but without any message, so the system will be likely hanged there. - [Steps to reproduce] - 1. Boot the installer with USB sticker + 1. Boot the installer with USB sticker 2. Finish the installation. 3. Click the button on the diagram to reboot. [Expected result] System reboot and boot to login page. [Actual result] Black screen and need to press "Enter" to reboot. [Failure rate] 100% [Additional information] " lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 + + "apt-cache policy plymouth-theme-spinner + plymouth-theme-spinner: + Installed: 0.9.4git20200109-0ubuntu8 + Candidate: 0.9.4git20200109-0ubuntu8 + Version table: + *** 0.9.4git20200109-0ubuntu8 100 + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867909] [NEW] plymoth spinner can not show the messages after installation.
Public bug reported: [Summary] Before 20.04, when user finished the 1st stage of installation, the message 『please remove the installation medium then reboot』or 『please remove installation medium then press enter』 will be shown on the screen. But since 20.04, due to the using of plymouth-themes-spinner, the system will still waiting for user to press Enter but without any message, so the system will be likely hanged there. [Steps to reproduce] 1. Boot the installer with USB sticker 2. Finish the installation. 3. Click the button on the diagram to reboot. [Expected result] System reboot and boot to login page. [Actual result] Black screen and need to press "Enter" to reboot. [Failure rate] 100% [Additional information] " lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 "apt-cache policy plymouth-theme-spinner plymouth-theme-spinner: Installed: 0.9.4git20200109-0ubuntu8 Candidate: 0.9.4git20200109-0ubuntu8 Version table: *** 0.9.4git20200109-0ubuntu8 100 100 /var/lib/dpkg/status ** Affects: plymouth (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867909 Title: plymoth spinner can not show the messages after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867766] Re: Namespace prefix sodipodi on namedview is not defined
" 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867766] [NEW] Namespace prefix sodipodi on namedview is not defined
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867766 Title: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Changed in: oem-priority Status: Triaged => Fix Released ** Changed in: oem-priority/bionic Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a LG Thin Client[0], can fix this issue [0] https://www.lg.com/global/business/monitor/monitor-products/lg- CK500W -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a hp Small Form Factor PC[0], can fix this issue [0] https://www8.hp.com/us/en/desktops/product-details/21353680 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a hp desktop mini machine[0], can fix this issue [0] http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=c06339658 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a built-in speaker/microphone laptop[0], still works well, didn't find any Regression potential. [0] https://support.hp.com/ro-en/document/c05994943 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] - Low. + Low. change is the workaround to active/deactivate some bugs which + didn't report things in the right order. It will just have extra + active/deactiveate actions in normal situation(which the machines don't + have this issue). + + Verified on built-in and non built-in input device machines , no + regression found yet. Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Triaged ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Changed in: oem-priority/bionic Importance: Undecided => Critical ** Changed in: oem-priority/bionic Status: New => Triaged ** Changed in: oem-priority/bionic Assignee: (unassigned) => hugh chao (hugh712) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] - Low, The first part of the patch is a workaround for a bug elsewhere - which is reporting things in the wrong order. The second part is a fix - for a case that wasn't being handled correctly. + Low. - - Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages + Package in this PPA: + https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] + + Low, The first part of the patch is a workaround for a bug elsewhere + which is reporting things in the wrong order. The second part is a fix + for a case that wasn't being handled correctly. Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851773] Re: [SRU] Need rtl8821ce in Bionic
** Tags added: oem-priority stella -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851773 Title: [SRU] Need rtl8821ce in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1851773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** Patch added: "check_input_treeview.patch" https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+attachment/5315268/+files/check_input_treeview.patch ** Summary changed: - [18.04]Not able to adjust Audio input UI volume after connecting headset + [SRU]Not able to adjust Audio input UI volume after connecting headset -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] + + + Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851773] Re: [SRU] Need rtl8821ce in Bionic
tried "HP ProOne 400 G5 All-in-One Business PC"[0] with this 8821ce dkms, works well, there isn't any issue on this machine [0] https://support.hp.com/in-en/document/c06409794#AbT11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851773 Title: [SRU] Need rtl8821ce in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1851773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [18.04]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] - 1. Boot ubuntu without any external microphone connected. + 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] - Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [18.04]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853584] Re: [18.04]Not able to adjust Audio input UI volume after connecting headset
** Description changed: + [ Impact ] + + Not able to adjust Audio input UI volume if this device doesn't have a + internal mic, the volume bar will be gray. + + [ Test Case ] + + 1. Boot ubuntu without any external microphone connected. + 2. Launch gnome-control-center and switch to Sound->Input tab. + 3. Connect external headset, then you will find the input show up but can not adjust the volume. + + [ Regression potential ] + + + + Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 - Note:20.04, 19.10, 19.04 are immune on the bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [18.04]Not able to adjust Audio input UI volume after connecting headset To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
