[Touch-packages] [Bug 2023745] [NEW] apt, dpkg: dependency problems prevent configuration of grub-pc
Public bug reported: #sudo apt update output: Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease Hit:2 http://in.archive.ubuntu.com/ubuntu jammy InRelease Hit:3 http://in.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:5 http://in.archive.ubuntu.com/ubuntu jammy-backports InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 7 packages can be upgraded. Run 'apt list --upgradable' to see them. # sudo apt list --upgradable output: Listing... Done fwupd-signed/jammy-updates 1.51.1~22.04.1+1.4-0ubuntu0.1 amd64 [upgradable from: 1.51~22.04.1+1.2-3ubuntu0.2] fwupd/jammy-updates 1.7.9-1~22.04.3 amd64 [upgradable from: 1.7.9-1~22.04.1] gnome-shell-extension-ubuntu-dock/jammy-updates,jammy-updates 72~ubuntu5.22.04.2.1 all [upgradable from: 72~ubuntu5.22.04.1] google-chrome-stable/stable 114.0.5735.133-1 amd64 [upgradable from: 114.0.5735.106-1] libfwupd2/jammy-updates 1.7.9-1~22.04.3 amd64 [upgradable from: 1.7.9-1~22.04.1] libfwupdplugin5/jammy-updates 1.7.9-1~22.04.3 amd64 [upgradable from: 1.7.9-1~22.04.1] ubuntu-drivers-common/jammy-updates 1:0.9.6.2~0.22.04.3 amd64 [upgradable from: 1:0.9.6.1] #sudo apt upgrade -y output: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Get more security updates through Ubuntu Pro with 'esm-apps' enabled: imagemagick libopenexr25 libpostproc55 libmagickcore-6.q16-6-extra libavcodec58 libmagickwand-6.q16-6 libavutil56 imagemagick-6.q16 libswscale5 libmagickcore-6.q16-6 libswresample3 imagemagick-6-common libavformat58 libavfilter7 Learn more about Ubuntu Pro at https://ubuntu.com/pro The following packages have been kept back: gnome-shell-extension-ubuntu-dock ubuntu-drivers-common The following packages will be upgraded: fwupd fwupd-signed google-chrome-stable libfwupd2 libfwupdplugin5 5 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 4 not fully installed or removed. Need to get 97.2 MB of archives. After this operation, 7,070 kB of additional disk space will be used. Get:1 https://dl.google.com/linux/chrome/deb stable/main amd64 google-chrome-stable amd64 114.0.5735.133-1 [94.4 MB] Get:2 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 fwupd amd64 1.7.9-1~22.04.3 [2,562 kB] Get:3 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libfwupdplugin5 amd64 1.7.9-1~22.04.3 [191 kB] Get:4 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libfwupd2 amd64 1.7.9-1~22.04.3 [106 kB] Get:5 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 fwupd-signed amd64 1.51.1~22.04.1+1.4-0ubuntu0.1 [30.3 kB] Fetched 97.2 MB in 16s (6,117 kB/s) (Reading database ... 203257 files and directories currently installed.) Preparing to unpack .../google-chrome-stable_114.0.5735.133-1_amd64.deb ... Unpacking google-chrome-stable (114.0.5735.133-1) over (114.0.5735.106-1) ... Preparing to unpack .../fwupd_1.7.9-1~22.04.3_amd64.deb ... Unpacking fwupd (1.7.9-1~22.04.3) over (1.7.9-1~22.04.1) ... Preparing to unpack .../libfwupdplugin5_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupdplugin5:amd64 (1.7.9-1~22.04.3) over (1.7.9-1~22.04.1) ... Preparing to unpack .../libfwupd2_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupd2:amd64 (1.7.9-1~22.04.3) over (1.7.9-1~22.04.1) ... Preparing to unpack .../fwupd-signed_1.51.1~22.04.1+1.4-0ubuntu0.1_amd64.deb ... Unpacking fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) over (1.51~22.04.1+1.2-3u buntu0.2) ... Setting up google-chrome-stable (114.0.5735.133-1) ... Setting up libfwupd2:amd64 (1.7.9-1~22.04.3) ... Setting up fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) ... Setting up grub-common (2.06-2ubuntu7.2) ... Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. update-rc.d: warning: start and stop actions are no longer supported; falling ba ck to defaults Job for grub-common.service failed because the control process exited with error code. See "systemctl status grub-common.service" and "journalctl -xeu grub-common.serv ice" for details. invoke-rc.d: initscript grub-common, action "restart" failed. × grub-common.service - Record successful boot for GRUB Loaded: loaded (/lib/systemd/system/grub-common.service; enabled; vendor pr eset: enabled) Active: failed (Result: exit-code) since Wed 2023-06-14 12:43:46 IST; 11ms ago Process: 5081 ExecStartPre=/bin/sh -c [ -s /boot/grub/grubenv ] || rm -f /bo ot/grub/grubenv; mkdir -p /boot/grub (code=exited, status=0/SUCCESS) Process: 5086 ExecStart=grub-editenv /boot/grub/grubenv unset recordfail (co de=exited, status=1/FAILURE) Main PID: 5086 (code=exited, status=1/FAILURE) CPU: 8ms Jun 14 12:43:46 c1 systemd[1]: Starting Record successful boot for GRUB... Jun 14 12:43:46 c1 grub-editenv[5086]: grub-editenv: error: invalid environment block. Jun 14 12:43:46 c1 systemd[1]: grub-common.service:
[Touch-packages] [Bug 1983359] Re: hwrng drivers missing in initrd.img
** Description changed: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. - [Test case] When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. - Best regards + [Test case] - Heinrich + * Update the initramfs-tools package. + * Run update-initramfs with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs-tools/conf.d/*.conf) + * Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' + * Check that main/lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. + + [Where problems could occur] + + Adding more drivers increases the size of the initrd. The larger initrd + might not fit onto the boot partition. The total size of hw_random + drivers on amd64 is less than 150 KiB so this seem improbable. + + [Other Info] + + n/a -- 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/1983359 Title: hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: Incomplete Status in initramfs-tools source package in Kinetic: Fix Released Bug description: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] * Update the initramfs-tools package. * Run update-initramfs with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs-tools/conf.d/*.conf) * Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' * Check that main/lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. [Where problems could occur] Adding more drivers increases the size of the initrd. The larger initrd might not fit onto the boot partition. The total size of hw_random drivers on amd64 is less than 150 KiB so this seem improbable. [Other Info] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+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 2023746] [NEW] [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
Public bug reported: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. [ Other Info ] N/A ** Affects: oem-priority Importance: Undecided Assignee: Laider Lai (laiderlai) Status: New ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2019555 ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Laider Lai (laiderlai) ** Changed in: oem-priority Assignee: Laider Lai (laiderlai) => (unassigned) ** Changed in: oem-priority Assignee: (unassigned) => Laider Lai (laiderlai) ** Tags added: oem-priority ** Tags added: originate-from-2019555 ** Description changed: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. - Might need more test cases to achieve more test coverage. [ Other Info ] N/A -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
** Description changed: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. + The change parts just only add VID/PIDs for Quectel's new modems under + the Quectel plugin. + [ Other Info ] N/A -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Jammy: New Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 1983359] Re: hwrng drivers missing in initrd.img
** Description changed: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] * Update the initramfs-tools package. - * Run update-initramfs with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs-tools/conf.d/*.conf) + * Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs-tools/conf.d/*.conf) * Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' - * Check that main/lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. + * Check that [main/]lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. [Where problems could occur] Adding more drivers increases the size of the initrd. The larger initrd might not fit onto the boot partition. The total size of hw_random drivers on amd64 is less than 150 KiB so this seem improbable. [Other Info] n/a ** Summary changed: - hwrng drivers missing in initrd.img + [SRU] hwrng drivers missing in initrd.img ** Patch added: "Debdiff for Jammy" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+attachment/5679603/+files/initramfs-tools-0.140ubuntu13.1..0.140ubuntu13.2.debdiff ** Changed in: initramfs-tools (Ubuntu Jammy) Assignee: (unassigned) => Heinrich Schuchardt (xypron) ** Changed in: initramfs-tools (Ubuntu Jammy) Status: Incomplete => Confirmed ** Changed in: initramfs-tools (Ubuntu Jammy) Assignee: Heinrich Schuchardt (xypron) => (unassigned) ** Changed in: initramfs-tools (Ubuntu Jammy) Assignee: (unassigned) => Heinrich Schuchardt (xypron) -- 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/1983359 Title: [SRU] hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: Confirmed Status in initramfs-tools source package in Kinetic: Fix Released Bug description: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] * Update the initramfs-tools package. * Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs-tools/conf.d/*.conf) * Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' * Check that [main/]lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. [Where problems could occur] Adding more drivers increases the size of the initrd. The larger initrd might not fit onto the boot partition. The total size of hw_random drivers on amd64 is less than 150 KiB so this seem improbable. [Other Info] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
** Also affects: modemmanager (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Jammy: New Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Jammy: New Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 1983359] Re: [SRU] hwrng drivers missing in initrd.img
** Description changed: [Impact] - The initialization of the entropy buffer of the urandom device is critical for security. + + The initialization of the entropy buffer of the urandom device is + critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] - * Update the initramfs-tools package. - * Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs-tools/conf.d/*.conf) - * Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' - * Check that [main/]lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. + To reproduce the issue: + + Download https://old- + releases.ubuntu.com/releases/22.04.1/ubuntu-22.04.1-preinstalled-server- + riscv64+unmatched.img.xz. + + Decompress it with + xz -d ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img.xz + + Run it in QEMU with + + qemu-system-riscv64 \ + -machine virt -nographic -m 2048 -smp 4 \ + -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin \ + -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \ + -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \ + -device virtio-rng-pci \ + -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio + + You can log into the system with user ubuntu, password ubuntu after + seeing the message "Cloud-init v. 22.2-0ubuntu1~22.04.3 finished" + + Run 'sudo dmesg | grep 'uninitialized urandom' + + To test the fix: + + Update the initramfs-tools package. + + Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in + /etc/initramfs-tools/initramfs.conf or in /etc/initramfs- + tools/conf.d/*.conf) + + Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' + + Check that [main/]lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ + exists and contains kernel modules. When running on QEMU the relevant + module is virtio-rng.ko. + + Reboot and check the kernel log by running 'sudo dmesg | grep + 'uninitialized urandom'. [Where problems could occur] Adding more drivers increases the size of the initrd. The larger initrd might not fit onto the boot partition. The total size of hw_random drivers on amd64 is less than 150 KiB so this seem improbable. [Other Info] n/a ** Description changed: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] To reproduce the issue: + + Install the prerequisites: + sudo apt-get update + sudo apt-get install opensbi qemu-system-misc u-boot-qemu Download https://old- releases.ubuntu.com/releases/22.04.1/ubuntu-22.04.1-preinstalled-server- riscv64+unmatched.img.xz. Decompress it with xz -d ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img.xz Run it in QEMU with qemu-system-riscv64 \ -machine virt -nographic -m 2048 -smp 4 \ -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin \ -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \ -device virtio-rng-pci \ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio You can log into the system with user ubuntu, password ubuntu after seeing the message "Cloud-init v. 22.2-0ubuntu1~22.04.3 finished" Run 'sudo dmesg | grep 'uninitialized urandom' To test the fix: Update the initramfs-tools package. Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs- tools/conf.d/*.conf) Unpack the initrd wit
[Touch-packages] [Bug 1983359] Re: [SRU] hwrng drivers missing in initrd.img
** Changed in: initramfs-tools (Ubuntu Jammy) Assignee: Heinrich Schuchardt (xypron) => (unassigned) -- 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/1983359 Title: [SRU] hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: Confirmed Status in initramfs-tools source package in Kinetic: Fix Released Bug description: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] To reproduce the issue: Install the prerequisites: sudo apt-get update sudo apt-get install opensbi qemu-system-misc u-boot-qemu Download https://old- releases.ubuntu.com/releases/22.04.1/ubuntu-22.04.1-preinstalled- server-riscv64+unmatched.img.xz. Decompress it with xz -d ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img.xz Run it in QEMU with qemu-system-riscv64 \ -machine virt -nographic -m 2048 -smp 4 \ -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin \ -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \ -device virtio-rng-pci \ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio You can log into the system with user ubuntu, password ubuntu after seeing the message "Cloud-init v. 22.2-0ubuntu1~22.04.3 finished" Run 'sudo dmesg | grep 'uninitialized urandom' To test the fix: Update the initramfs-tools package. Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs- tools/conf.d/*.conf) Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' Check that [main/]lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. When running on QEMU the relevant module is virtio-rng.ko. Reboot and check the kernel log by running 'sudo dmesg | grep 'uninitialized urandom'. [Where problems could occur] Adding more drivers increases the size of the initrd. The larger initrd might not fit onto the boot partition. The total size of hw_random drivers on amd64 is less than 150 KiB so this seem improbable. [Other Info] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+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 2023745] Re: apt, dpkg: dependency problems prevent configuration of grub-pc
As you can see in the output grub-common failed to install because the service failed to restart which edits the /boot/grub/grubenv file. This indicates the file is corrupted either due to a bug in grub we don't know about, a hard reset during grub running which corrupted the disk cache or something like that, or the drive is failing. My suggestion is to perform a drive check and delete the file to solve the issue. ** Changed in: apt (Ubuntu) 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/2023745 Title: apt, dpkg: dependency problems prevent configuration of grub-pc Status in apt package in Ubuntu: Invalid Bug description: #sudo apt update output: Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease Hit:2 http://in.archive.ubuntu.com/ubuntu jammy InRelease Hit:3 http://in.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:5 http://in.archive.ubuntu.com/ubuntu jammy-backports InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 7 packages can be upgraded. Run 'apt list --upgradable' to see them. # sudo apt list --upgradable output: Listing... Done fwupd-signed/jammy-updates 1.51.1~22.04.1+1.4-0ubuntu0.1 amd64 [upgradable from: 1.51~22.04.1+1.2-3ubuntu0.2] fwupd/jammy-updates 1.7.9-1~22.04.3 amd64 [upgradable from: 1.7.9-1~22.04.1] gnome-shell-extension-ubuntu-dock/jammy-updates,jammy-updates 72~ubuntu5.22.04.2.1 all [upgradable from: 72~ubuntu5.22.04.1] google-chrome-stable/stable 114.0.5735.133-1 amd64 [upgradable from: 114.0.5735.106-1] libfwupd2/jammy-updates 1.7.9-1~22.04.3 amd64 [upgradable from: 1.7.9-1~22.04.1] libfwupdplugin5/jammy-updates 1.7.9-1~22.04.3 amd64 [upgradable from: 1.7.9-1~22.04.1] ubuntu-drivers-common/jammy-updates 1:0.9.6.2~0.22.04.3 amd64 [upgradable from: 1:0.9.6.1] #sudo apt upgrade -y output: Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done Get more security updates through Ubuntu Pro with 'esm-apps' enabled: imagemagick libopenexr25 libpostproc55 libmagickcore-6.q16-6-extra libavcodec58 libmagickwand-6.q16-6 libavutil56 imagemagick-6.q16 libswscale5 libmagickcore-6.q16-6 libswresample3 imagemagick-6-common libavformat58 libavfilter7 Learn more about Ubuntu Pro at https://ubuntu.com/pro The following packages have been kept back: gnome-shell-extension-ubuntu-dock ubuntu-drivers-common The following packages will be upgraded: fwupd fwupd-signed google-chrome-stable libfwupd2 libfwupdplugin5 5 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 4 not fully installed or removed. Need to get 97.2 MB of archives. After this operation, 7,070 kB of additional disk space will be used. Get:1 https://dl.google.com/linux/chrome/deb stable/main amd64 google-chrome-stable amd64 114.0.5735.133-1 [94.4 MB] Get:2 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 fwupd amd64 1.7.9-1~22.04.3 [2,562 kB] Get:3 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libfwupdplugin5 amd64 1.7.9-1~22.04.3 [191 kB] Get:4 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libfwupd2 amd64 1.7.9-1~22.04.3 [106 kB] Get:5 http://in.archive.ubuntu.com/ubuntu jammy-updates/main amd64 fwupd-signed amd64 1.51.1~22.04.1+1.4-0ubuntu0.1 [30.3 kB] Fetched 97.2 MB in 16s (6,117 kB/s) (Reading database ... 203257 files and directories currently installed.) Preparing to unpack .../google-chrome-stable_114.0.5735.133-1_amd64.deb ... Unpacking google-chrome-stable (114.0.5735.133-1) over (114.0.5735.106-1) ... Preparing to unpack .../fwupd_1.7.9-1~22.04.3_amd64.deb ... Unpacking fwupd (1.7.9-1~22.04.3) over (1.7.9-1~22.04.1) ... Preparing to unpack .../libfwupdplugin5_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupdplugin5:amd64 (1.7.9-1~22.04.3) over (1.7.9-1~22.04.1) ... Preparing to unpack .../libfwupd2_1.7.9-1~22.04.3_amd64.deb ... Unpacking libfwupd2:amd64 (1.7.9-1~22.04.3) over (1.7.9-1~22.04.1) ... Preparing to unpack .../fwupd-signed_1.51.1~22.04.1+1.4-0ubuntu0.1_amd64.deb ... Unpacking fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) over (1.51~22.04.1+1.2-3u buntu0.2) ... Setting up google-chrome-stable (114.0.5735.133-1) ... Setting up libfwupd2:amd64 (1.7.9-1~22.04.3) ... Setting up fwupd-signed (1.51.1~22.04.1+1.4-0ubuntu0.1) ... Setting up grub-common (2.06-2ubuntu7.2) ... Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. update-rc.d: warning: start and stop actions are no longer supported; falling ba ck to defaults Job for grub-common.service failed because the control process exited with error code. See "systemctl status grub-common
[Touch-packages] [Bug 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
For Jammy (22.04), the modemmanager_1.20.0-1~ubuntu22.04.2-jammy.debdiff is attached. ** Patch added: "modemmanager_1.20.0-1~ubuntu22.04.2-jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2023746/+attachment/5679628/+files/modemmanager_1.20.0-1~ubuntu22.04.2-jammy.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Jammy: New Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
A verification log from modemmanager_1.20.0-1~ubuntu22.04.1 to modemmanager_1.20.0-1~ubuntu22.04.2 is attached ** Attachment added: "modemmanager_1.20.0-1~ubuntu22.04.2_verifried.log" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2023746/+attachment/5679629/+files/modemmanager_1.20.0-1~ubuntu22.04.2_verifried.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Jammy: New Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
The fix is in the current version ** Changed in: modemmanager (Ubuntu Jammy) Assignee: (unassigned) => Laider Lai (laiderlai) ** Changed in: modemmanager (Ubuntu) Importance: Undecided => High ** Changed in: modemmanager (Ubuntu) Status: New => Fix Released ** Changed in: modemmanager (Ubuntu Jammy) Importance: Undecided => High ** Changed in: modemmanager (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
Thanks for the work there, I've uploaded to jammy SRU to the review queue now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 1980991] Re: /usr/sbin/on_ac_power incorrectly reporting ac power status
It's worth adding that in #1973359 (was closed as duplicate of this bug; I was the author), the computer is plugged in with a barrel power plug, not via USB-C PD. I'm not sure how it still ends up being routed as a USB power source in /sys/class/power_supply. Specifically, it's this computer: https://imgur.com/a/0nUFAFH ... so it's very much in "has consistent power" range. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1980991 Title: /usr/sbin/on_ac_power incorrectly reporting ac power status Status in powermgmt-base package in Ubuntu: Triaged Status in powermgmt-base source package in Kinetic: Triaged Bug description: Good afternoon, folks. I believe I discovered a bug in the /usr/sbin/on_ac_power script. I have a Dell OptiPlex 5090 host that has an entry in /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe this is the USB-C power delivery port on the front of the chassis. The issue I'm encountering is that /usr/sbin/on_ac_power is exiting with code 1 which states: (1 (false) if not on AC power) when that isn't the case. This looks to be because of the ucsi-source-psy-USBC000:001 entry reporting the "online" status as 0, presumably because nothing is currently connected to that USB-C port. This causes /usr/sbin/on_ac_power to incorrectly report that the machine isn't connected to AC power and causes other utilities like unattended-upgrades to quit when using the default configuration since it believes the machine isn't connected to AC power. There is a workaround with unattended-upgrades where you can specify it to run regardless of if AC power is connected, but as more and more chassis implement power-delivery USB-C ports I foresee this becoming more of an issue. I'm not sure if it's anything to look into, but I figured I would share my findings. Please let me know if you have any questions or if I can provide any additional information, troubleshooting, or testing. Thanks! -Kevin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 2017076] Re: default Chinese font in snap apps is ugly
This seems to be fixed in Firefox latest/stable/ubuntu-23.04 114.0.1. @Sebastien: But that doesn't fix the 23.04 installer, does it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 1943441] Re: lxc: lxc-test-parse-config-file failure (expected value and retrieved value do not match)
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/440756 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1943441 Title: lxc: lxc-test-parse-config-file failure (expected value and retrieved value do not match) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Focal: New Status in lxc source package in Impish: Confirmed Bug description: I'm getting the following error with the lxc kernel autotest on impish: 08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match 08:46:04 DEBUG| 08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context 08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 08 08:46:06Command failed, rc=1, Command returned non-zero exit status * Command: /tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file Exit status: 1 Duration: 0.0550210475922 stderr: parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match parse_config_file.c: 382: main: lxc.selinux.context I haven't investigated very much, but it looks like a (mis)configuration change / issue. Does it ring any bell? Otherwise I'll investigate more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943441/+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 2023746] Re: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS
** Description changed: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. - The Lenovo SE10 platform WWAN LVFS function works well on Lunar and Mantic. + The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2023746 Title: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Committed Bug description: [SRU] Add Quectel EM05-G/EM05-CN PID information to support WWAN LVFS [ Impact ] The modemmanager v1.20.0 doesn't have Quectel EM05-G/EM05-CN PID (0x311/0x312) information. Fwupd can't base on modemmanager to identify the modem for supporting WWAN LVFS on a x86-based platform with Intel EHL, which is working with Jammy. (lp: #2019555) [ Test Plan ] Under Jammy environment, check fwupd (snap version) can identify EM05-G/EM05-CN modems to support WWAN LVFS on the target platform $ fwupdmgr refresh --force $ sudo fwupdmgr install # Select EM05-G/EM05-CN [ Where problems could occur ] The EM05-G/EM05-CN PID information is upstreamed to modemmanager v1.20.4 1. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b43cae70b078ee1af5b454cfd2b452e8dc711453 2. https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/e30b3a07a8d0f2bf5676cdcaf74da76f4af98b63 The Lunar and Mantic already working with modemmanager v1.20.4. The target platform WWAN LVFS function works well on Lunar and Mantic. The change parts just only add VID/PIDs for Quectel's new modems under the Quectel plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023746/+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 2017076] Re: default Chinese font in snap apps is ugly
@Gunnar, what's the issue with the installer? it's the first time the installer is mentioned on that report so I'm not sure to understand the question -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2017076] Re: default Chinese font in snap apps is ugly
The installer is mentioned in the first sentence in the bug description. :) I was thinking that the installer still ships the old snap without the fix. Then, if the user opens FF before refreshing the snaps, they would still have the wrong default in FF. Maybe I'm wrong. I haven't done any tests. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 1983359] Re: [SRU] hwrng drivers missing in initrd.img
** Changed in: initramfs-tools (Ubuntu Jammy) Status: Confirmed => In Progress -- 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/1983359 Title: [SRU] hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: In Progress Status in initramfs-tools source package in Kinetic: Fix Released Bug description: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] To reproduce the issue: Install the prerequisites: sudo apt-get update sudo apt-get install opensbi qemu-system-misc u-boot-qemu Download https://old- releases.ubuntu.com/releases/22.04.1/ubuntu-22.04.1-preinstalled- server-riscv64+unmatched.img.xz. Decompress it with xz -d ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img.xz Run it in QEMU with qemu-system-riscv64 \ -machine virt -nographic -m 2048 -smp 4 \ -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin \ -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \ -device virtio-rng-pci \ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio You can log into the system with user ubuntu, password ubuntu after seeing the message "Cloud-init v. 22.2-0ubuntu1~22.04.3 finished" Run 'sudo dmesg | grep 'uninitialized urandom' To test the fix: Update the initramfs-tools package. Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs- tools/conf.d/*.conf) Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' Check that [main/]lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. When running on QEMU the relevant module is virtio-rng.ko. Reboot and check the kernel log by running 'sudo dmesg | grep 'uninitialized urandom'. [Where problems could occur] Adding more drivers increases the size of the initrd. The larger initrd might not fit onto the boot partition. The total size of hw_random drivers on amd64 is less than 150 KiB so this seem improbable. [Other Info] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+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 2023437]
When I build clang-16 from your object files (plus my system libraries and startup files) for powerpc64le using gold 2.40.50.20230614 I get exactly the same binary as when using gold 2.39.0.20230101. That's comparing gold from the tip of master and binutils-2_39-branch in sourceware.org/git/binutils-gdb.git. The latter does not have the commit you identify as causing a problem. Very likely the reason why I don't see a problem is that my libz.so.1, libtinfo.so.5, libstdc++.so.6, libm.so.6, libgcc_s.so.1, libc.so.6, ld64.so.2, or startup files are different to yours. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: In Progress Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powe
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
> The installer is mentioned in the first sentence in the bug description. :) No it isn't? The description states 'After installs Ubuntu 23.04 with Chinese language' which refers to the installed system and not the installer? (just to be clear to me 'installer' is ubuntu-desktop- installer in lunar which is a flutter UI distributed as a snap that let you install Ubuntu) The first screenshot after the description is one from firefox showing an issue, reading the comments my understanding is that the report was about the firefox issue which has been resolved now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2023437]
Confirmed also on 2.40.50.20230611-2ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: In Progress Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powerpc64le-linux-gnu/libz.so /usr/lib/powerpc64le-linux-gnu/libtinfo.so root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-re
[Touch-packages] [Bug 1983359] Re: [SRU] hwrng drivers missing in initrd.img
Hi, Thanks for adressing Steve's comments, I uploaded the Jammy debdiff, it's now in the SRU queue. I also unsubscribe ubuntu-sponsors, so if by any chance there's a need to revisit this upload do remember to subscribe it again :) -- 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/1983359 Title: [SRU] hwrng drivers missing in initrd.img Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: In Progress Status in initramfs-tools source package in Kinetic: Fix Released Bug description: [Impact] The initialization of the entropy buffer of the urandom device is critical for security. When booting Jammy 22.04.1 on QEMU riscv64 I see the following warnings: [ 14.654546] random: lvm: uninitialized urandom read (4 bytes read) [ 15.247995] random: lvm: uninitialized urandom read (2 bytes read) [ 22.484719] random: lvm: uninitialized urandom read (4 bytes read) [ 43.161846] random: lvmconfig: uninitialized urandom read (4 bytes read) [ 48.862281] random: lvm: uninitialized urandom read (4 bytes read) Module virtio-rng.ko is missing in initrd.img. Adding virtio_rng to /etc/initramfs-tools/modules avoids the warnings. Hardware RNG drivers should generally be included in the initrd to provide early entropy. [Test case] To reproduce the issue: Install the prerequisites: sudo apt-get update sudo apt-get install opensbi qemu-system-misc u-boot-qemu Download https://old- releases.ubuntu.com/releases/22.04.1/ubuntu-22.04.1-preinstalled- server-riscv64+unmatched.img.xz. Decompress it with xz -d ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img.xz Run it in QEMU with qemu-system-riscv64 \ -machine virt -nographic -m 2048 -smp 4 \ -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin \ -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf \ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0 \ -device virtio-rng-pci \ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio You can log into the system with user ubuntu, password ubuntu after seeing the message "Cloud-init v. 22.2-0ubuntu1~22.04.3 finished" Run 'sudo dmesg | grep 'uninitialized urandom' To test the fix: Update the initramfs-tools package. Run 'update-initramfs -k $(uname -r) -u' with MODULES=most (defined in /etc/initramfs-tools/initramfs.conf or in /etc/initramfs- tools/conf.d/*.conf) Unpack the initrd with 'unmkinitramfs /boot/initrd.img-$(uname -r)' Check that [main/]lib/modules/$(uname -r)/kernel/drivers/char/hw_random/ exists and contains kernel modules. When running on QEMU the relevant module is virtio-rng.ko. Reboot and check the kernel log by running 'sudo dmesg | grep 'uninitialized urandom'. [Where problems could occur] Adding more drivers increases the size of the initrd. The larger initrd might not fit onto the boot partition. The total size of hw_random drivers on amd64 is less than 150 KiB so this seem improbable. [Other Info] n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1983359/+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 2023437] Re: ppc64el gold linker produces unusable clang-16 binary
** Changed in: binutils Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/2023437 Title: ppc64el gold linker produces unusable clang-16 binary Status in binutils: In Progress Status in binutils package in Ubuntu: New Bug description: root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment -Wno-misleading-indentation -Wctad-maybe-unsupported -fdiagnostics-color -ffunction-sections -fdata-sections -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -fdebug-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -ffile-prefix-map=/llvm-toolchain-16-16.0.5/build-llvm=build-llvm -ffile-prefix-map=/llvm-toolchain-16-16.0.5/= -no-canonical-prefixes -fno-common -Woverloaded-virtual -fno-strict-aliasi ng -O3 -DNDEBUG -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--build-id -fuse-ld=bfd-Wl,--gc-sections tools/clang/tools/driver/CMakeFiles/clang.dir/driver.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1as_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/cc1gen_reproducer_main.cpp.o tools/clang/tools/driver/CMakeFiles/clang.dir/clang-driver.cpp.o -o bin/clang-16-bfd -Wl,-rpath,"\$ORIGIN/../lib:" lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMAnalysis.a lib/libLLVMCodeGen.a lib/libLLVMCore.a lib/libLLVMipo.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMInstrumentation.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMObjCARCOpts.a lib/libLLVMOption.a lib/libLLVMScalarOpts.a lib/libLLVMSupport.a lib/libLLVMTargetParser.a lib/libLLVMTransformUtils.a lib/libLL VMVectorize.a lib/libclangBasic.a lib/libclangCodeGen.a lib/libclangDriver.a lib/libclangFrontend.a lib/libclangFrontendTool.a lib/libclangSerialization.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMMCDisassembler.a lib/libclangCodeGen.a lib/libLLVMCoverage.a lib/libLLVMLTO.a lib/libLLVMExtensions.a lib/libPolly.a lib/libPollyISL.a lib/libLLVMPasses.a lib/libLLVMCodeGen.a lib/libLLVMObjCARCOpts.a lib/libLLVMTarget.a lib/libLLVMCoroutines.a lib/libLLVMipo.a lib/libLLVMInstrumentation.a lib/libLLVMVectorize.a lib/libLLVMBitWriter.a lib/libLLVMLinker.a lib/libLLVMIRPrinter.a lib/libclangExtractAPI.a lib/libclangRewriteFrontend.a lib/libclangARCMigrate.a lib/libclangStaticAnalyzerFrontend.a lib/libclangStaticAnalyzerCheckers.a lib/libclangStaticAnalyzerCore.a lib/libclangCrossTU.a lib/libclangIndex.a lib/libclangFrontend.a lib/libclangDriver.a lib/libLLVMWindowsDriver.a lib/libLLVMOption.a lib/libclangParse .a lib/libclangSerialization.a lib/libclangSema.a lib/libclangAnalysis.a lib/libclangASTMatchers.a lib/libLLVMFrontendHLSL.a lib/libclangEdit.a lib/libclangSupport.a lib/libclangAST.a lib/libLLVMFrontendOpenMP.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMTransformUtils.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMSymbolize.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMIRReader.a lib/libLLVMBitReader.a lib/libLLVMAsmParser.a lib/libLLVMTextAPI.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMRemarks.a lib/libLLVMBitstreamReader.a lib/libclangFormat.a lib/libclangToolingInclusions.a lib/libclangToolingCore.a lib/libclangRewrite.a lib/libclangLex.a lib/libclangBasic.a lib/libLLVMTargetParser.a lib/libLLVMSupport.a lib/libLLVMDemangle.a -l rt -ldl -lm /usr/lib/powerpc64le-linux-gnu/libz.so /usr/lib/powerpc64le-linux-gnu/libtinfo.so root@Unimatrix08-Jammy:/clang# /usr/bin/g++-12 -O3 -fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-command-line-argument -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-mem
[Touch-packages] [Bug 2023772] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned er
*** This bug is a duplicate of bug 2023771 *** https://bugs.launchpad.net/bugs/2023771 Public bug reported: Unable to upgrade my pc due to this any others bugs. E: /usr/share/initramfs-tools/hooks/zz-busybox-initramfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.19.0-32-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abi1571 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jun 14 17:31:44 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 5570 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=9279cb9d-233d-4c02-84d4-2c665027abca ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0GHXK4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0GHXK4:rvrA00:cvnDellInc.:ct10:cvr:sku0810: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2023772 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Unable to upgrade my pc due to this any others bugs. E: /usr/share/initramfs-tools/hooks/zz-busybox-initramfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.19.0-32-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abi1571 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jun 14 17:31:44 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 5570 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=9279cb9d-233d-4c02-84d4-2c665027abca ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No up
[Touch-packages] [Bug 2023771] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
** Tags removed: need-duplicate-check -- 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/2023771 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Unable to upgrade my pc due to this any others bugs. E: /usr/share/initramfs-tools/hooks/zz-busybox-initramfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.19.0-32-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abi1571 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jun 14 17:31:44 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 5570 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=9279cb9d-233d-4c02-84d4-2c665027abca ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0GHXK4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0GHXK4:rvrA00:cvnDellInc.:ct10:cvr:sku0810: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2023771/+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 2023771] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned er
Public bug reported: Unable to upgrade my pc due to this any others bugs. E: /usr/share/initramfs-tools/hooks/zz-busybox-initramfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.19.0-32-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abi1571 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jun 14 17:31:44 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 5570 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=9279cb9d-233d-4c02-84d4-2c665027abca ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0GHXK4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0GHXK4:rvrA00:cvnDellInc.:ct10:cvr:sku0810: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2023771 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Unable to upgrade my pc due to this any others bugs. E: /usr/share/initramfs-tools/hooks/zz-busybox-initramfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.19.0-32-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abi1571 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jun 14 17:31:44 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 5570 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=9279cb9d-233d-4c02-84d4-2c665027abca ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1
[Touch-packages] [Bug 2017076] Re: default Chinese font in snap apps is ugly
> The first screenshot after the description is one from firefox showing an issue, reading the comments my understanding is that the report was about the firefox issue which has been resolved now Yes :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2017076 Title: default Chinese font in snap apps is ugly Status in Snappy: Confirmed Status in fontconfig package in Ubuntu: Invalid Status in language-selector package in Ubuntu: Invalid Bug description: After installs Ubuntu 23.04 with Chinese language selected, the default font is chosen to AR PL UMing CN, which is very ugly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: fontconfig 2.14.1-3ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 20 14:18:45 2023 InstallationDate: Installed on 2023-04-20 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=zh_CN.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2017076/+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 2023772] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
*** This bug is a duplicate of bug 2023771 *** https://bugs.launchpad.net/bugs/2023771 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2023771, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 2023771 package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 -- 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/2023772 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Unable to upgrade my pc due to this any others bugs. E: /usr/share/initramfs-tools/hooks/zz-busybox-initramfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.19.0-32-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.13 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abi1571 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Wed Jun 14 17:31:44 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 5570 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=9279cb9d-233d-4c02-84d4-2c665027abca ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2023 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0GHXK4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/06/2023:br1.14:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0GHXK4:rvrA00:cvnDellInc.:ct10:cvr:sku0810: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2023772/+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 1971242] Re: printing PDF appears always grey, no color
** Also affects: okular (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: atril (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: cups (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color Status in CUPS: Fix Released Status in atril package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Status in okular package in Ubuntu: Confirmed Status in atril source package in Lunar: New Status in cups source package in Lunar: New Status in okular source package in Lunar: New Bug description: After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF document. The print appears always b/w regardless color printing was enabled or not. Printing from LibreOffice produces a color print. This behavior (bug) is reproducible on three upgraded machines. It would be nice to have color print back again. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+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 2022155] Re: File selection dialog does not allow selecting multiple files using Ctrl
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2022155 Title: File selection dialog does not allow selecting multiple files using Ctrl Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Bug description: I have no idea if I have filed this against the right package. It happens in both Firefox and Chrome, whatever provides their file selection dialog for uploads is apparently the problem, I don't know if that's gnome shell or something else. When I want to upload multiple files in a web browser, I can do that if I hit shift, and then click another file. But, that selects not just the two files that I clicked on, but every file in between them in the dialog (which is the expected behaviour when shift clicking in a file selection dialog). When I just want to select two files that are not displayed next to each other, I expect to be able to Ctrl+click on the files, and for them and only them to be selected. But, this doesn't happen, the second file does not get selected when I do that. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 10:08:32 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-08-04 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2022155/+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 2022155] Re: File selection dialog does not allow selecting multiple files using Ctrl
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2022155 Title: File selection dialog does not allow selecting multiple files using Ctrl Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Bug description: I have no idea if I have filed this against the right package. It happens in both Firefox and Chrome, whatever provides their file selection dialog for uploads is apparently the problem, I don't know if that's gnome shell or something else. When I want to upload multiple files in a web browser, I can do that if I hit shift, and then click another file. But, that selects not just the two files that I clicked on, but every file in between them in the dialog (which is the expected behaviour when shift clicking in a file selection dialog). When I just want to select two files that are not displayed next to each other, I expect to be able to Ctrl+click on the files, and for them and only them to be selected. But, this doesn't happen, the second file does not get selected when I do that. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 10:08:32 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-08-04 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.0-2ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2022155/+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 1971242] Re: printing PDF appears always grey, no color
Sample PPD file for the SRU test plan.
** Description changed:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
+
+ [ Impact ]
+
+ If the PPD file for a printer has a ColorModel option and the only
+ choice in it for printing in color is not named RGB but CMYK instead,
+ the printer cannot be made printing in color with intuitive methods,
+ usually selcting the color choice in the print dialog (which makes
+ ColorModel=CMYK be sent along with the job).
+
+ Only an ugly command-line-based workaround, running the command
+
+ lpadmin -p PRINTER -o print-color-mode-default=color
+
+ makes the printer print in color.
+
+ An example for printers with such PPDs are printers from RICOH and OEM
+ (Lanier, InfoTec, Savin, ..), so many high-end color laser printers are
+ affected.
+
+ [ Test Plan ]
+
+ Remove the workaround if you had applied it:
+
+ lpadmin -p PRINTER -R print-color-mode-default
+
+ If you have an affected printer, print a PDF file (or use the print
+ functionality in an application) with colored content and choose the
+ setting for color printing in the print dialog. When printing via
+ command line do
+
+ lp -d PRINTER -o ColorModel=CMYK FILE.pdf
+
+ Without the SRU applied you will get a grayscale/monochrome printout,
+ with it applied, you will get a colored printout.
+
+ To test without a printer:
+
+ Stop CUPS:
+
+ sudo systemctl stop cups
+
+ Edit /etc/cups/cups-files.conf to have a line
+
+ FiileDevice Yes
+
+ ans start CUPS again:
+
+ sudo systemctl start cups
+
+ Then create a queue using the attached sample PPD file:
+
+ lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
+ PDF.ppd
+
+ Print a file to this queue as described above. When the job is done
+ ("lpstat" does not show it any more), open /tmp/printout with a text
+ editor. Chcke whether it contains a line
+
+ @PJL SET RENDERMODE=COLOR
+
+ near its beginning, and NOT a line
+
+ @PJL SET RENDERMODE=GRAYSCALE
+
+ [ Where problems could occur ]
+
+ The patches are simple and they are also for some time in newer CUPS
+ versions (2.4.2 and newer) which are included in several distributions
+ (Ubuntu 22.10, 23.04, and others) and did not cause any complaints about
+ color printing. So the regression potential is very low.
** Attachment added: "Ricoh-PDF_Printer-PDF.ppd"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1971242/+attachment/5679703/+files/Ricoh-PDF_Printer-PDF.ppd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Confirmed
Status in okular package in Ubuntu:
Confirmed
Status in atril source package in Lunar:
New
Status in cups source package in Lunar:
New
Status in okular source package in Lunar:
New
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
ans start C
[Touch-packages] [Bug 2012943] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2012943 Title: systemd-resolved crashes due to use-after-free bug Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [ Impact ] The continuous systemd-resolved crashes delay/hang the device startup. And this leads to unresponsive devices in the system. Specifically, the crash looks like: Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service. Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV [...] Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting. Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=6/ABRT [ Test Plan ] The exact steps to reproduce this issue are still not known. But we see this crash only in Static IP Addressing mode enabled, where systemd-resolved is enabled for LLMNR service. But we were not able to see this crash in DHCP mode. Steps to reproduce: 1) Powercycle the device. 2) Soft-reboot. It was also pointed out by Brian Murray that this error in the Ubuntu error tracker is likely the same bug: https://errors.ubuntu.com/problem/3cb08ae5efaa4d8c6ce992f7cebd2751ae3f168f. Therefore, we would expect to stop seeing this error in the tracker as a result of this patch. [ Where problems could occur ] The patch[1] simply disables the timer event source for a DNS query when the struct representing that query is free'd. I cannot see any realistic regression potential, because if the timer event fired on the DNS query after it has been free'd, then that would be this bug. I.e. no working code should be relying on the timer event source still being around after the query is free'd. [1] https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2012943] Re: systemd-resolved crashes due to use-after-free bug
This bug was fixed in the package systemd - 245.4-4ubuntu3.22 --- systemd (245.4-4ubuntu3.22) focal; urgency=medium * resolve: fix potential memleak and use-after-free (LP: #2012943) File: debian/patches/lp2012943-resolve-fix-potential-memleak-and-use-after-free.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ed2729587663dbab3583d06492b715df2896874e -- Nick Rosbrook Mon, 27 Mar 2023 13:54:06 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2012943 Title: systemd-resolved crashes due to use-after-free bug Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [ Impact ] The continuous systemd-resolved crashes delay/hang the device startup. And this leads to unresponsive devices in the system. Specifically, the crash looks like: Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service. Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV [...] Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting. Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=6/ABRT [ Test Plan ] The exact steps to reproduce this issue are still not known. But we see this crash only in Static IP Addressing mode enabled, where systemd-resolved is enabled for LLMNR service. But we were not able to see this crash in DHCP mode. Steps to reproduce: 1) Powercycle the device. 2) Soft-reboot. It was also pointed out by Brian Murray that this error in the Ubuntu error tracker is likely the same bug: https://errors.ubuntu.com/problem/3cb08ae5efaa4d8c6ce992f7cebd2751ae3f168f. Therefore, we would expect to stop seeing this error in the tracker as a result of this patch. [ Where problems could occur ] The patch[1] simply disables the timer event source for a DNS query when the struct representing that query is free'd. I cannot see any realistic regression potential, because if the timer event fired on the DNS query after it has been free'd, then that would be this bug. I.e. no working code should be relying on the timer event source still being around after the query is free'd. [1] https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2012943/+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 2000628] Re: The wifi password prompt disappear immediately after showing up on 22.04
I’m also experiencing this bug (Ubuntu 22.04, xorg) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2000628 Title: The wifi password prompt disappear immediately after showing up on 22.04 Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Some other people reported this bug [here](https://askubuntu.com/questions/1409433/22-04-cant-input- password-for-wifi) Basically, when you try to log into a network, there is no way to input your password. The only way to reach a visible network seems to be by one of the workarounds: use the "Connect to Hidden Network" option, or directly edit the network config files. It seems like a critical bug to me because it can demotivate new users of Ubuntu and Linux. I joined a screen record of the prompt blinking on screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2000628/+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 2021498] Re: Please merge 3.134 into mantic
** Patch removed: "debdiff between ubuntu adduser 1.129ubuntu1 and 1.134ubuntu1" https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+attachment/5679543/+files/ubuntu_adduser_3.129ubuntu1.debdiff ** Patch removed: "debdiff between debian adduser 1.134 and 1.134ubuntu1" https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+attachment/5679542/+files/debian_adduser_3.134.debdiff ** Patch added: "debdiff between debian adduser 1.134 and 1.134ubuntu1" https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+attachment/5679707/+files/debian_adduser_3.134.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2021498 Title: Please merge 3.134 into mantic Status in adduser package in Ubuntu: In Progress Bug description: The upstream version 3.134 should be merged into mantic. The current version is 3.129ubuntu1. See the merge conflict report: https://merges.ubuntu.com/a/adduser/REPORT Note: this is a tracking bug PPA for review: https://launchpad.net/~mateus- morais/+archive/ubuntu/adduser-merge-lp2021498 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+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 2021498] Re: Please merge 3.134 into mantic
** Patch added: "debdiff between ubuntu adduser 1.129ubuntu1 and 1.134ubuntu1" https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+attachment/5679708/+files/debian_adduser_3.129ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/2021498 Title: Please merge 3.134 into mantic Status in adduser package in Ubuntu: In Progress Bug description: The upstream version 3.134 should be merged into mantic. The current version is 3.129ubuntu1. See the merge conflict report: https://merges.ubuntu.com/a/adduser/REPORT Note: this is a tracking bug PPA for review: https://launchpad.net/~mateus- morais/+archive/ubuntu/adduser-merge-lp2021498 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2021498/+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 1990618] Re: PXE Boot - errors in dhclient-script
You found an incompatibility of /sbin/dhclient-script with busybox. Relevant code snippet: ``` if [ -f $resolv_conf ]; then chown --reference=$resolv_conf $new_resolv_conf chmod --reference=$resolv_conf $new_resolv_conf fi ``` The chown command from busybox does not have a --reference parameter. Simplified test case: ``` touch resolve.conf busybox chown --reference=/etc/resolv.conf resolve.conf ``` This also fails for Ubuntu 23.10 (mantic). Can you document the steps to reproduce it? The amd-net autopkgtest test cases for initramfs-tools do not trigger the bug (probably because they to not trigger the if-condition). ** Summary changed: - PXE Boot - errors in dhclient-script + PXE Boot - errors in dhclient-script: busybox chmod: unrecognized option --reference ** Changed in: isc-dhcp (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1990618 Title: PXE Boot - errors in dhclient-script: busybox chmod: unrecognized option --reference Status in isc-dhcp package in Ubuntu: Triaged Bug description: When booting 22.04.1 using ISO pulled vmlinuz/initrd/squashfs there are some errors in /sbin/dhclient-script. IDs redacted. Internet Systems Consortium DHCP Client 4.4.1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eno1/f0:92:~:~:~:~ Sending on LPF/eno1/f0:92:~:~:~:~ Sending on Socket/fallback DHCPDISCOVER on eno1 to 255.255.255.255 port 67 interval 3 (xid=0xa9d4e16d) DHCPOFFER of 10.0.~.~ from 10.0.~.1 DHCPREQUEST for 10.0.~.~ on eno1 to 255.255.255.255 port 67 (xid=0x6de1d4a9) DHCPACK of 10.0.~.~ from 10.0.~.1 (xid=0xa9d4e16d) /sbin/dhclient-script: line 99: chown: not found chmod: unrecognized option '--reference=/etc/resolv.conf' BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) multi-call binary. Usage: chmod [-R] MODE[,MODE]... FILE... Each MODE is one or more of the letters ugoa, one of the symbols +-= and one or more of the letters rwxst -R Recurse bound to 10.0.~.~ -- renewal in 2963 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1990618/+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)
Marking todo to recheck how the situation is today.
** Tags removed: server-triage-discuss
** Tags added: server-todo
--
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:
Triaged
Status in heartbeat package in Ubuntu:
Won't Fix
Status in keepalived package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Won't Fix
Status in keepalived source package in Bionic:
Confirmed
Status in systemd source package in Bionic:
Fix Released
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.com
smtp_server 10.22.11.7 # IP
smtp_connect_timeout 30 # integer, seconds
router_id system3 # string identifying the machine,
# (doesn't have to be hostname).
vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
vrrp_mcast_group6 ff02::12 # optional, default ff02::12
enable_traps # enable SNMP traps
}
vrrp_sync_group collecti
[Touch-packages] [Bug 2023789] [NEW] IPv6 fails with busybox: ip: either "dev" is duplicate, or "permanent" is garbage
Public bug reported:
This failure was detected while working on the amd64-net autopkgtest for
initramfs-tools. Create a dummy root file system and launch qemu with
user network and specify ip6=dhcp on the kernel command line:
```
qemu-system-x86_64 -m 1G -drive
"file=${ROOTDISK},if=${ROOTDISK_QEMU_IF},media=disk,format=raw" \
${USRDISK:+-drive
"file=${USRDISK},if=${USRDISK_QEMU_IF},media=disk,format=raw"} \
-nographic -no-reboot -kernel "/boot/vmlinuz-${KVER}" -initrd
"${INITRAMFS}" \
-device
"virtio-net-pci,netdev=net0,bus=pci.0,addr=3,mac=52:54:00:65:43:21" \
-netdev
"user,id=net0,net=10.0.3.0/24,ipv6-net=fec7::/48,hostname=pizza,dnssearch=test,domainname=example.com,bootfile=/path/to/bootfile2"
\
-device
"virtio-net-pci,netdev=net1,bus=pci.0,addr=5,mac=52:54:00:12:34:56" \
-netdev
"user,id=net1,hostname=goulash,dnssearch=example,dnssearch=example.net,domainname=test,bootfile=/path/to/bootfile"
\
-append "root=/dev/${ROOTDISK_LINUX_NAME} ro console=ttyS0,115200
ip6=dhcp"
```
/sbin/dhclient-script fails. Running the script with "set -x" shows the
culprit:
```
+ ip -6 addr flush dev ens5 scope global permanent
ip: either "dev" is duplicate, or "permanent" is garbage
```
The busybox ip command does not support the FLAG "permanent".
Distro: Ubuntu 23.10
Packages:
isc-dhcp-client 4.4.3-P1-2ubuntu2
busybox-initramfs 1:1.35.0-4ubuntu1
** Affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/2023789
Title:
IPv6 fails with busybox: ip: either "dev" is duplicate, or "permanent"
is garbage
Status in isc-dhcp package in Ubuntu:
New
Bug description:
This failure was detected while working on the amd64-net autopkgtest
for initramfs-tools. Create a dummy root file system and launch qemu
with user network and specify ip6=dhcp on the kernel command line:
```
qemu-system-x86_64 -m 1G -drive
"file=${ROOTDISK},if=${ROOTDISK_QEMU_IF},media=disk,format=raw" \
${USRDISK:+-drive
"file=${USRDISK},if=${USRDISK_QEMU_IF},media=disk,format=raw"} \
-nographic -no-reboot -kernel "/boot/vmlinuz-${KVER}" -initrd
"${INITRAMFS}" \
-device
"virtio-net-pci,netdev=net0,bus=pci.0,addr=3,mac=52:54:00:65:43:21" \
-netdev
"user,id=net0,net=10.0.3.0/24,ipv6-net=fec7::/48,hostname=pizza,dnssearch=test,domainname=example.com,bootfile=/path/to/bootfile2"
\
-device
"virtio-net-pci,netdev=net1,bus=pci.0,addr=5,mac=52:54:00:12:34:56" \
-netdev
"user,id=net1,hostname=goulash,dnssearch=example,dnssearch=example.net,domainname=test,bootfile=/path/to/bootfile"
\
-append "root=/dev/${ROOTDISK_LINUX_NAME} ro console=ttyS0,115200
ip6=dhcp"
```
/sbin/dhclient-script fails. Running the script with "set -x" shows
the culprit:
```
+ ip -6 addr flush dev ens5 scope global permanent
ip: either "dev" is duplicate, or "permanent" is garbage
```
The busybox ip command does not support the FLAG "permanent".
Distro: Ubuntu 23.10
Packages:
isc-dhcp-client 4.4.3-P1-2ubuntu2
busybox-initramfs 1:1.35.0-4ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2023789/+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 2023789] Re: IPv6 fails with busybox: ip: either "dev" is duplicate, or "permanent" is garbage
** Description changed:
This failure was detected while working on the amd64-net autopkgtest for
initramfs-tools. Create a dummy root file system and launch qemu with
user network and specify ip6=dhcp on the kernel command line:
```
qemu-system-x86_64 -m 1G -drive
"file=${ROOTDISK},if=${ROOTDISK_QEMU_IF},media=disk,format=raw" \
- ${USRDISK:+-drive
"file=${USRDISK},if=${USRDISK_QEMU_IF},media=disk,format=raw"} \
- -nographic -no-reboot -kernel "/boot/vmlinuz-${KVER}" -initrd
"${INITRAMFS}" \
- -device
"virtio-net-pci,netdev=net0,bus=pci.0,addr=3,mac=52:54:00:65:43:21" \
- -netdev
"user,id=net0,net=10.0.3.0/24,ipv6-net=fec7::/48,hostname=pizza,dnssearch=test,domainname=example.com,bootfile=/path/to/bootfile2"
\
- -device
"virtio-net-pci,netdev=net1,bus=pci.0,addr=5,mac=52:54:00:12:34:56" \
- -netdev
"user,id=net1,hostname=goulash,dnssearch=example,dnssearch=example.net,domainname=test,bootfile=/path/to/bootfile"
\
- -append "root=/dev/${ROOTDISK_LINUX_NAME} ro console=ttyS0,115200
ip6=dhcp"
+ ${USRDISK:+-drive
"file=${USRDISK},if=${USRDISK_QEMU_IF},media=disk,format=raw"} \
+ -nographic -no-reboot -kernel "/boot/vmlinuz-${KVER}" -initrd "${INITRAMFS}"
\
+ -device "virtio-net-pci,netdev=net0,bus=pci.0,addr=3,mac=52:54:00:65:43:21" \
+ -netdev
"user,id=net0,net=10.0.3.0/24,ipv6-net=fec7::/48,hostname=pizza,dnssearch=test,domainname=example.com,bootfile=/path/to/bootfile2"
\
+ -device "virtio-net-pci,netdev=net1,bus=pci.0,addr=5,mac=52:54:00:12:34:56" \
+ -netdev
"user,id=net1,hostname=goulash,dnssearch=example,dnssearch=example.net,domainname=test,bootfile=/path/to/bootfile"
\
+ -append "root=/dev/${ROOTDISK_LINUX_NAME} ro console=ttyS0,115200 ip6=dhcp"
```
/sbin/dhclient-script fails. Running the script with "set -x" shows the
- culprit:
+ culprit in PREINIT6:
```
+ ip -6 addr flush dev ens5 scope global permanent
ip: either "dev" is duplicate, or "permanent" is garbage
```
The busybox ip command does not support the FLAG "permanent".
Distro: Ubuntu 23.10
Packages:
- isc-dhcp-client 4.4.3-P1-2ubuntu2
- busybox-initramfs 1:1.35.0-4ubuntu1
+ isc-dhcp-client 4.4.3-P1-2ubuntu2
+ busybox-initramfs 1:1.35.0-4ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/2023789
Title:
IPv6 fails with busybox: ip: either "dev" is duplicate, or "permanent"
is garbage
Status in isc-dhcp package in Ubuntu:
New
Bug description:
This failure was detected while working on the amd64-net autopkgtest
for initramfs-tools. Create a dummy root file system and launch qemu
with user network and specify ip6=dhcp on the kernel command line:
```
qemu-system-x86_64 -m 1G -drive
"file=${ROOTDISK},if=${ROOTDISK_QEMU_IF},media=disk,format=raw" \
${USRDISK:+-drive
"file=${USRDISK},if=${USRDISK_QEMU_IF},media=disk,format=raw"} \
-nographic -no-reboot -kernel "/boot/vmlinuz-${KVER}" -initrd "${INITRAMFS}"
\
-device "virtio-net-pci,netdev=net0,bus=pci.0,addr=3,mac=52:54:00:65:43:21" \
-netdev
"user,id=net0,net=10.0.3.0/24,ipv6-net=fec7::/48,hostname=pizza,dnssearch=test,domainname=example.com,bootfile=/path/to/bootfile2"
\
-device "virtio-net-pci,netdev=net1,bus=pci.0,addr=5,mac=52:54:00:12:34:56" \
-netdev
"user,id=net1,hostname=goulash,dnssearch=example,dnssearch=example.net,domainname=test,bootfile=/path/to/bootfile"
\
-append "root=/dev/${ROOTDISK_LINUX_NAME} ro console=ttyS0,115200 ip6=dhcp"
```
/sbin/dhclient-script fails. Running the script with "set -x" shows
the culprit in PREINIT6:
```
+ ip -6 addr flush dev ens5 scope global permanent
ip: either "dev" is duplicate, or "permanent" is garbage
```
The busybox ip command does not support the FLAG "permanent".
Distro: Ubuntu 23.10
Packages:
isc-dhcp-client 4.4.3-P1-2ubuntu2
busybox-initramfs 1:1.35.0-4ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2023789/+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 1971242] Re: printing PDF appears always grey, no color
** Changed in: cups (Ubuntu Lunar)
Status: New => In Progress
** Changed in: cups (Ubuntu)
Status: Confirmed => Fix Committed
** Also affects: okular (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: cups (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: atril (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: cups (Ubuntu Lunar)
** Changed in: cups (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: cups (Ubuntu Jammy)
Status: New => In Progress
** No longer affects: okular (Ubuntu Lunar)
** No longer affects: okular (Ubuntu Jammy)
** No longer affects: atril (Ubuntu Lunar)
** No longer affects: atril (Ubuntu Jammy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Committed
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
In Progress
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
ans start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Chcke whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 2011458] Re: ssh fails to rebind when it is killed with -HUP
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu7.3 --- openssh (1:9.0p1-1ubuntu7.3) kinetic; urgency=medium * debian/patches/systemd-socket-activation.patch: do not leak sockets in child process. Follow-up fix for LP: #2011458. -- Nick Rosbrook Tue, 30 May 2023 16:58:06 -0400 ** Changed in: openssh (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Kinetic: Fix Released Status in openssh source package in Lunar: Fix Released Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22. Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running in debugging mode. Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: entering fd = 7 config len 3456 Apr 17 20:46:34 lunar sshd[1167]: debug3: ssh_msg_send: type 0 Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: done Apr 17 20:46:34 lunar sshd[1167]: debug1: rexec start in
[Touch-packages] [Bug 2011458] Update Released
The verification of the Stable Release Update for openssh has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Kinetic: Fix Released Status in openssh source package in Lunar: Fix Released Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22. Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running in debugging mode. Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: entering fd = 7 config len 3456 Apr 17 20:46:34 lunar sshd[1167]: debug3: ssh_msg_send: type 0 Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state:
[Touch-packages] [Bug 2011458] Re: ssh fails to rebind when it is killed with -HUP
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu8.2 --- openssh (1:9.0p1-1ubuntu8.2) lunar; urgency=medium * debian/patches/systemd-socket-activation.patch: do not leak sockets in child process. Follow-up fix for LP: #2011458. -- Nick Rosbrook Fri, 26 May 2023 10:44:48 -0400 ** Changed in: openssh (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Kinetic: Fix Released Status in openssh source package in Lunar: Fix Released Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22. Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running in debugging mode. Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: entering fd = 7 config len 3456 Apr 17 20:46:34 lunar sshd[1167]: debug3: ssh_msg_send: type 0 Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: done Apr 17 20:46:34 lunar sshd[1167]: debug1: rexec start in 4 o
[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color
Uploaded CUPS 2.4.5 to Mantic. This version has the mentioned fixes
included.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Committed
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
In Progress
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
ans start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Chcke whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66
Ok, via LP: #2018519, here is a test case.
$ mkdir /tmp/home
$ export HOME=/tmp/home
$ sudo apt install dput python3-pip python3-distro-info
$ pip3 install -U setuptools
$ dput
Traceback (most recent call last):
File "/usr/bin/dput", line 33, in
sys.exit(load_entry_point('dput===1.1.0ubuntu2', 'console_scripts',
'execute-dput')())
File "/usr/bin/dput", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/usr/share/dput/dput/dput.py", line 33, in
from .helper import dputhelper
File "/usr/share/dput/dput/helper/dputhelper.py", line 17, in
import pkg_resources
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/__init__.py", line
3327, in
def _initialize_master_working_set():
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/__init__.py", line
3301, in _call_aside
f(*args, **kwargs)
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/__init__.py", line
3339, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/__init__.py", line
629, in _build_master
ws.require(__requires__)
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/__init__.py", line
966, in require
needed = self.resolve(parse_requirements(requirements))
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/__init__.py", line
827, in resolve
dist = self._resolve_dist(
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/__init__.py", line
852, in _resolve_dist
if dist is None or (dist not in req and replace_conflicting):
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/__init__.py", line
3204, in __contains__
return self.specifier.contains(item, prereleases=True)
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/specifiers.py",
line 902, in contains
item = Version(item)
File
"/tmp/home/.local/lib/python3.10/site-packages/pkg_resources/_vendor/packaging/version.py",
line 197, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version:
'1.1.0ubuntu2'
$
I still think the better answer is "don't mix pip with your system
install". But this is at least a test case that satisfies my constraint
from above.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1991606
Title:
Invalid PEP440 package version breaking setuptools >= 66
Status in devscripts package in Ubuntu:
Fix Released
Status in distro-info package in Ubuntu:
Fix Released
Status in drslib package in Ubuntu:
New
Status in duecredit package in Ubuntu:
Fix Released
Status in gpgme1.0 package in Ubuntu:
Fix Released
Status in python-debian package in Ubuntu:
Fix Released
Status in reportbug package in Ubuntu:
Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
Fix Released
Status in update-manager package in Ubuntu:
Fix Released
Status in devscripts source package in Bionic:
New
Status in distro-info source package in Bionic:
New
Status in drslib source package in Bionic:
Invalid
Status in duecredit source package in Bionic:
New
Status in gpgme1.0 source package in Bionic:
New
Status in python-debian source package in Bionic:
Invalid
Status in reportbug source package in Bionic:
New
Status in ubuntu-dev-tools source package in Bionic:
New
Status in update-manager source package in Bionic:
New
Status in devscripts source package in Focal:
New
Status in distro-info source package in Focal:
New
Status in drslib source package in Focal:
New
Status in duecredit source package in Focal:
New
Status in gpgme1.0 source package in Focal:
New
Status in python-debian source package in Focal:
New
Status in reportbug source package in Focal:
New
Status in ubuntu-dev-tools source package in Focal:
New
Status in update-manager source package in Focal:
New
Status in devscripts source package in Jammy:
New
Status in distro-info source package in Jammy:
New
Status in drslib source package in Jammy:
New
Status in duecredit source package in Jammy:
New
Status in gpgme1.0 source package in Jammy:
New
Status in python-debian source package in Jammy:
New
Status in reportbug source package i
[Touch-packages] [Bug 2023917] [NEW] tzdata_2023c-0ubuntu0.20.04.2 does not build on focal
Public bug reported: I'm trying to build the latest version of tzdata on focal and the build fails with the below error: Test all zones to load, have a name, and have a reasonable offset. ... skipped 'Needs https://launchpad.net/bugs/207604' [12/12540] == ERROR: test_post_1970_symlinks_consistency (__main__.TestZoneinfo) [Europe/Uzhgorod -> Europe/Kyiv] Test that post-1970 symlinks are consistent with pre-1970 timezones. -- Traceback (most recent call last): File "debian/tests/python", line 136, in test_post_1970_symlinks_consistency tz_target = pytz.timezone(target) File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 181, in timezone raise UnknownTimeZoneError(zone) pytz.exceptions.UnknownTimeZoneError: 'Europe/Kyiv' == ERROR: test_post_1970_symlinks_consistency (__main__.TestZoneinfo) [Europe/Zaporozhye -> Europe/Kyiv] Test that post-1970 symlinks are consistent with pre-1970 timezones. -- Traceback (most recent call last): File "debian/tests/python", line 136, in test_post_1970_symlinks_consistency tz_target = pytz.timezone(target) File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 181, in timezone raise UnknownTimeZoneError(zone) pytz.exceptions.UnknownTimeZoneError: 'Europe/Kyiv' == ERROR: test_post_1970_symlinks_consistency (__main__.TestZoneinfo) [Pacific/Enderbury -> Pacific/Kanton] Test that post-1970 symlinks are consistent with pre-1970 timezones. -- Traceback (most recent call last): File "debian/tests/python", line 136, in test_post_1970_symlinks_consistency tz_target = pytz.timezone(target) File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 181, in timezone raise UnknownTimeZoneError(zone) pytz.exceptions.UnknownTimeZoneError: 'Pacific/Kanton' == ERROR: test_post_1970_symlinks_consistency (__main__.TestZoneinfo) [America/Godthab -> America/Nuuk] Test that post-1970 symlinks are consistent with pre-1970 timezones. -- Traceback (most recent call last): File "debian/tests/python", line 136, in test_post_1970_symlinks_consistency tz_target = pytz.timezone(target) File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 181, in timezone raise UnknownTimeZoneError(zone) pytz.exceptions.UnknownTimeZoneError: 'America/Nuuk'
[Touch-packages] [Bug 1875019] Re: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1875019 Title: ftbfs: Test failed: Basic functionality with the bind-mounted cache dir Status in fontconfig package in Ubuntu: New Bug description: 1) apt-src install fontconfig 2) cd fontconfig-2.13.1/ 3) debuild -us -uc -b gets to PASS: test-hash PASS: test-bz106632 FAIL: run-test.sh fontconfig 2.13.1: test/test-suite.log # TOTAL: 7 # PASS: 6 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: run-test == Running: Basic check Running: With a subdir Running: Subdir with a cache file Running: Complicated directory structure Running: Subdir with an out-of-date cache file Running: Dir with an out-of-date cache file Running: Re-creating .uuid Running: Consistency between .uuid and cache name b41b6931-2503-44dd-a5d0-465a2c171511/home/z/fontconfig-2.13.1/test/cache.dir/08acdce6-36bc-4684-9a7b-0f24192abc6b-le64.cache-7 Running: Keep mtime of the font directory Running: Basic functionality with the bind-mounted cache dir *** Test failed: Basic functionality with the bind-mounted cache dir cache was updated. FAIL run-test.sh (exit status: 1) ubuntu: focal 20.04 LTS fontconfig1: fontconfig: Installed: 2.13.1-2ubuntu3 Candidate: 2.13.1-2ubuntu3 Version table: *** 2.13.1-2ubuntu3 500 500 http://speglar.simnet.is/ubuntu focal/main amd64 Packages 500 http://ubuntu.hysing.is/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fontconfig 2.13.1-2ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 25 13:15:14 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fontconfig UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1875019/+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 2023927] [NEW] Screen flickering whe update images
Public bug reported: Often, when there are small changes in image displayed, an horizontal flickering is observed. This happen for example on a mouse right button menu, or when a hyperlink description appears on the screen bottom when mouse pointer cross some field on a webpage, also when favorites menu appear. The flickering usually disappear in a few moments, sometimes (usually when a few pixels are updating) it can last for seconds. This flickering is caused by a late updating of some horizontal lines, so for awhile a few lines of previous image coexist with a majority of new ones ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 22:44:12 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-40-generic, x86_64: installed virtualbox, 6.1.32, 5.13.0-41-generic, x86_64: installed virtualbox, 6.1.32, 5.4.0-126-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Device [1e39:a025] InstallationDate: Installed on 2022-01-01 (529 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Error: command ['lsusb'] failed with exit code 127: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_error_name Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 127: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_error_name Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 127: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_error_name MachineType: MEDION S15449 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic root=UUID=cbfc0023-baf3-4a11-b0aa-6dadbd0f60f7 ro quiet splash pci=noaer vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 212 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr212:bd04/09/2021:br5.19:svnMEDION:pnS15449:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:skuML-23000830031014: dmi.product.family: Akoya dmi.product.name: S15449 dmi.product.sku: ML-230008 30031014 dmi.product.version: Default string dmi.sys.vendor: MEDION version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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 N/A 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 ** Attachment added: "video explaining the bug when favorites menu appear/disappear" https://bugs.launchpad.net/bugs/2023927/+attachment/5679762/+files/WhatsApp%20Video%202023-06-14%20at%2022.59.56.mp4 -- 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/2023927 Title: Screen flickering whe update images Status in xorg package in Ubuntu: New Bug description: Often, when there are small changes in image displayed, an horizontal flickering is observed. This happen for example on a mouse right button menu, or when a hyperlink description appears on the screen bottom when mouse pointer cross some field on a webpage, also when favorites menu appear. The flickering usually disappear in a few moments, sometimes (usually when a few pixels are updating) it can last for seconds. This flickering is caused by a late updating of some horizontal lines, so for awhile a few lines of previous image coexist with a majority of new ones ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13
[Touch-packages] [Bug 2023917] Re: tzdata_2023c-0ubuntu0.20.04.2 does not build on focal
Which version of python3-tz do you use? You need python3-tz 2019.3-1ubuntu0.20.04.0 to add Europe/Kyiv: https://launchpad.net/ubuntu/+source/python-tz/2019.3-1ubuntu0.20.04.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2023917 Title: tzdata_2023c-0ubuntu0.20.04.2 does not build on focal Status in tzdata package in Ubuntu: New Bug description: I'm trying to build the latest version of tzdata on focal and the build fails with the below error: Test all zones to load, have a name, and have a reasonable offset. ... skipped 'Needs https://launchpad.net/bugs/207604' [12/12540] == ERROR: test_post_1970_symlinks_consistency (__main__.TestZoneinfo) [Europe/Uzhgorod -> Europe/Kyiv] Test that post-1970 symlinks are consistent with pre-1970 timezones. -- Traceback (most recent call last): File "debian/tests/python", line 136, in test_post_1970_symlinks_consistency tz_target = pytz.timezone(target) File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 181, in timezone raise UnknownTimeZoneError(zone) pytz.exceptions.UnknownTimeZoneError: 'Europe/Kyiv' == ERROR: test_post_1970_symlinks_consistency (__main__.TestZoneinfo) [Europe/Zaporozhye -> Europe/Kyiv] Test that post-1970 symlinks are consistent with pre-1970 timezones. -- Traceback (most recent call last): File "debian/tests/python", line 136, in test_post_1970_symlinks_consistency tz_target = pytz.timezone(target) File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 181, in timezone raise UnknownTimeZoneError(zone) pytz.exceptions.UnknownTimeZoneError: 'Europe/Kyiv' == ERROR: test_post_1970_symlinks_consistency (__main__.TestZoneinfo) [Pacific/Enderbury -> Pacific/Kanton] Test that post-1970 symlinks are consistent with pre-1970 timezones. -- Traceback (most recent call last): File "debian/tests/python", line 136, in test_post_1970_symlinks_consistency tz_target = pytz.timezone(target) File "/usr/lib/python3/dist-packages/pytz/__init__.py", line 181, in timezone raise UnknownTimeZoneError(zone) pytz.exceptions.UnknownTimeZoneError: 'Pacific/Kanton' == ERROR: test_post_1970_symlinks_consistency (__main__.TestZoneinfo) [America/Godthab -> America/Nuuk] Test that post-1970 symlinks are consistent with pre-1970 timezones.
[Touch-packages] [Bug 2023741] Re: package apparmor 3.0.4-2ubuntu2.2 failed to install/upgrade: installed apparmor package post-installation script subprocess was killed by signal (Broken pipe)
Hello Stephan, it looks a bit like you had an external hard drive disconnect or suffer low power immediately before these error messages. My guess is that making sure all the cables are plugged in tightly, rebooting, and then: sudo apt update sudo apt install -f will get you back up and running without trouble. If there's more errors here, let us know. Thanks ** Changed in: apparmor (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2023741 Title: package apparmor 3.0.4-2ubuntu2.2 failed to install/upgrade: installed apparmor package post-installation script subprocess was killed by signal (Broken pipe) Status in apparmor package in Ubuntu: Incomplete Bug description: I'm just following instructions for reporting, Not a guru, just a copy and paste end user who HATES microsoft. Freshly installed Ubuntu on laptop HP250G6 Had windows 10 home on laptop, suspect all the windows updates caused PC to be so slow, much better now of course. After installing had to enable visualization technology (VMX) and Software guard extensions (SGX) in bios for pc to boot up. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: apparmor 3.0.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jun 13 19:17:47 2023 DuplicateSignature: package:apparmor:3.0.4-2ubuntu2.2 Setting up apparmor (3.0.4-2ubuntu2.2) ... dpkg: error processing package apparmor (--configure): installed apparmor package post-installation script subprocess was killed by signal (Broken pipe) ErrorMessage: installed apparmor package post-installation script subprocess was killed by signal (Broken pipe) InstallationDate: Installed on 2023-06-13 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=1a48d7a5-5953-4fd2-9ea9-7eea65640625 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: apparmor Title: package apparmor 3.0.4-2ubuntu2.2 failed to install/upgrade: installed apparmor package post-installation script subprocess was killed by signal (Broken pipe) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2023741/+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
