[Touch-packages] [Bug 2036149] [NEW] BlueZ release 5.69
Public bug reported: Update to BlueZ 5.69 (or later) in Ubuntu 24.04 ** Affects: bluez (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2036149 Title: BlueZ release 5.69 Status in bluez package in Ubuntu: Triaged Bug description: Update to BlueZ 5.69 (or later) in Ubuntu 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2036149/+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 2035221] Re: driver problem
Thanks for the bug report. There is no software brightness adjustment on desktop machines. You need to adjust the brightness on the monitor instead. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/2035221 Title: driver problem Status in Ubuntu: Invalid Bug description: my PC brightness cannot be adjust ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 20:41:05 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:308c] InstallationDate: Installed on 2023-08-20 (23 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 36644M9 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=d9fe23a3-2394-47aa-aa88-66e71e67d711 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2013 dmi.bios.release: 0.57 dmi.bios.vendor: LENOVO dmi.bios.version: F1KT57AUS dmi.board.vendor: LENOVO dmi.board.version: NOK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrF1KT57AUS:bd11/07/2013:br0.57:svnLENOVO:pn36644M9:pvrThinkCentreM72e:rvnLENOVO:rn:rvrNOK:cvnLENOVO:ct3:cvr:skuLENOVO_MT_3664: dmi.product.name: 36644M9 dmi.product.sku: LENOVO_MT_3664 dmi.product.version: ThinkCentre M72e dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.0.20230414.1+2061~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2035221/+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 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays
** Changed in: oem-priority Status: Confirmed => 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/2025563 Title: System can not shutdown if system has multiple VROC RAID arrays Status in OEM Priority Project: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [ Impact ] The system can not shutdown if the system has multiple VROC RAID arrays. Intel has fixed it in systemd v251 [1]. Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9. [1] The commit fixes the issue: commit 3a3b022d2cc112803ea7b9beea98bbcad110368a Author: Mariusz Tkaczyk Date: Tue Mar 29 12:49:54 2022 +0200 shutdown: get only active md arrays. Current md_list_get() implementation filters all block devices, started from "md*". This is ambiguous because list could contain: - partitions created upon md device (mdXpY) - external metadata container- specific type of md array. For partitions there is no issue, because they aren't handle STOP_ARRAY ioctl sent later. It generates misleading errors only. Second case is more problematic because containers are not locked in kernel. They are stopped even if container member array is active. For that reason reboot or shutdown flow could be blocked because metadata manager cannot be restarted after switch root on shutdown. Add filters to remove partitions and containers from md_list. Partitions can be excluded by DEVTYPE. Containers are determined by MD_LEVEL property, we are excluding all with "container" value. Signed-off-by: Mariusz Tkaczyk In the journal, we can see systemd-shutdown looping repeatedly as it tries and fails to detach all md devices: ... [ 513.416293] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:5). [ 513.422953] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or resource busy [ 513.431227] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:4). [ 513.437952] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or resource busy [ 513.449298] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124). [ 513.456278] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or resource busy [ 513.465323] systemd-shutdown[1]: Not all MD devices stopped, 4 left. [ 513.472564] systemd-shutdown[1]: Couldn't finalize remaining MD devices, trying again. [ 513.485302] systemd-shutdown[1]: Failed to open watchdog device /dev/watchdog: No such file or directory [ 513.496195] systemd-shutdown[1]: Stopping MD devices. [ 513.502176] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs [ 513.513382] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus [ 513.521436] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class [ 513.534810] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126). [ 513.545384] systemd-shutdown[1]: Failed to sync MD block device /dev/md126, ignoring: Input/output error [ 513.557265] md: md126 stopped. [ 513.561451] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:5). [ 513.576673] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or resource busy [ 513.589274] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:4). [ 513.597976] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or resource busy [ 513.607263] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124). [ 513.615067] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or resource busy [ 513.625157] systemd-shutdown[1]: Not all MD devices stopped, 4 left. [ 513.632209] systemd-shutdown[1]: Couldn't finalize remaining MD devices, trying again. [ 513.641474] systemd-shutdown[1]: Failed to open watchdog device /dev/watchdog: No such file or directory [ 513.653660] systemd-shutdown[1]: Stopping MD devices. [ 513.661257] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs [ 513.668833] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus [ 513.677347] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class [ 513.687047] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126). [ 513.697206] systemd-shutdown[1]: Failed to sync MD block device /dev/md126, ignoring: Input/output error [ 513.707193] md: md126 stopped. ... [ Test Plan ] 1. Build two VROC RAID. One RAID 0 for System volume, another RAID 10 for Data volume. 2. Install system on System volume. 3. Update systemd. 4. Reboot the system. 5. Verify if the system can reboot. [ Where problems could occur ] The patch confirmed fixed the reboot issue on the system with two VROC RAIDs but more than two VROC RAIDs and the
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
I downgraded to 249.11-0ubuntu3.9, 249.11-0ubuntu3.7 Because I know for a Fact I had no issues with it, My last install was working with 249.11-0ubuntu3.9, you rolled out the update to 249.11-0ubuntu3.10 and that is when all this started. I simply went back to an older version after a fresh install to be safe, one computer and already lost 2 days on it, could not afford to try out 249.11-0ubuntu3.9 again and hope it all worked, I also know for a fact it Broke on 249.11-0ubuntu3.10. Again I am no programmer or software engineer, so you do what you feel is best for the code, I know what broke, when it broke, but I will never know why it broke. Close this bug out if your comfortable with rolling out 249.11-0ubuntu3.10. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 1977630] Re: machinectl pull-tar/pull-raw Operation not permitted
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/1977630 Title: machinectl pull-tar/pull-raw Operation not permitted Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [impact] machinectl pull-tar does not work, ever [test case] see comment 2 [regression potential] problems/failures during pull-tar operation [scope] needed only in j fixed (indirectly) by upstream commit referenced in original description, which is included in v250, so fixed already in k pull-tar does not fail on f; no fix needed there [original description] There is a bug in systemd 249, where one can't pull any images. This was fixed in version 250, and never got backported. (FIX: https://github.com/systemd/systemd/commit/c40d82abf7b23803aa7394a7a7e24c40c32af851) Hopefully this can be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-container 249.11-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
[Touch-packages] [Bug 1991829] Re: machinectl read-only does not work
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/1991829 Title: machinectl read-only does not work Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Won't Fix Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [impact] machinectl read-only does not work [test case] On a system where the systemd machines dir is *not* on a btrfs volume (e.g. it's on a normal ext4 fs), create an image 'test' and then: $ sudo machinectl image-status test test Type: directory Path: /var/lib/machines/test Hostname: ubuntu OS: Ubuntu 20.04.5 LTS RO: writable Created: Wed 2022-10-05 13:41:15 EDT; 34s ago $ sudo machinectl read-only test Could not mark image read-only: Access denied [regression potential] failure marking images ro or rw [scope] this is needed in all releases that include machinectl this is fixed upstream by 137d162c42ed858613afc3d7493d08d4ae6d5c1b To manage notifications about this bug go to:
[Touch-packages] [Bug 1982218] Re: wait-online does not correctly identify managed links
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/1982218 Title: wait-online does not correctly identify managed links Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [Impact] systemd-networkd-wait-online will exit prematurely when the --any flag is passed, due to an incorrect patch in Ubuntu that is supposed to make systemd-networkd-wait-online exit when *no* links are managed. [Test Plan] This test uses a VM managed by libvirt. In this scenario we have the "default" network which provides DHCP to the VM, and the "no-dhcp" network which does not provide DHCP. To setup the VM (this assumes Jammy, but the same steps apply for Lunar using appropriate names and install media): 1. Define the default and no-dhcp networks: $ cat > /tmp/net-default.xml << EOF default 04260896-2701-422d-84e0-8e0df1122db3 $ virsh net-create --file /tmp/net-default.xml $ cat > /tmp/net-default.xml << EOF no-dhcp
[Touch-packages] [Bug 1999275] Re: systemd-binfmt.service fails in tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/1999275 Title: systemd-binfmt.service fails in tests-in-lxd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] systemd-binfmt.service fails in LXD because access /proc/sys/binfmt_misc is prevented by LXD apparmor config. This causes our autopkgtest to fail, and leaves systemd-binfmt.service in a failed state: root@jammy:~# systemctl status systemd-binfmt × systemd-binfmt.service - Set Up Additional Binary Formats Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static) Active: failed (Result: exit-code) since Thu 2023-08-17 18:54:18 UTC; 1min 12s ago Docs: man:systemd-binfmt.service(8) man:binfmt.d(5) https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems Main PID: 118 (code=exited, status=1/FAILURE) CPU: 5ms Aug 17 18:54:18 jammy systemd[1]: Starting Set Up Additional Binary Formats... Aug 17 18:54:18 jammy
[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/2009743 Title: networkd: classless routes served by DHCP are created incorrectly Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [Impact] Classless static routes served by DHCP are ignored by networkd in some cases. Specifically, the gateway is not being set for routes whenever the route destination is in the assigned network. This is a regression in behavior since Focal. [Test Plan] This is basically taken from systemd-networkd-tests.py. Using a veth pair, setup dnsmasq to serve the problematic routes: $ cat > /etc/systemd/network/25-dhcp-server-veth-peer.network << EOF [Match] Name=veth-peer [Network] IPv6AcceptRA=no Address=2600::1/0 Address=192.168.5.1/24 EOF $ cat > /etc/systemd/network/25-test.network << EOF [Match] Name=veth99 [Network] DHCP=ipv4 IPv6AcceptRA=false [DHCPv4] UseRoutes=yes EOF $ cat > /etc/systemd/network/25-veth.netdev << EOF [NetDev]
[Touch-packages] [Bug 2013543] Re: systemctl daemon-reexec forgets running services and starts everything new
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/2013543 Title: systemctl daemon-reexec forgets running services and starts everything new Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Lunar: Fix Released Bug description: [Impact] Depending on the contents of /proc/cmdline, when systemd is re- executed with systemctl daemon-reexec, the --deserialize flag may be ignored because it was added after the other arguments. For example, if /proc/cmdline contains ---, then the re-exec cmdline might look like: $ cat /proc/1/cmdline | tr '\0' '\n' /lib/systemd/systemd --- splash --system --deserialize 54 This causes systemd not to process the --deserialize 54 argument, causing it to start with a fresh state. This can cause all kinds of problems, and one easy symptom to see is many lines in the journal like: "$service.service: Found left-over process $pid ($service) in control group while starting unit. Ignoring." [Test Plan] 1. (Only needed if your test system is not
[Touch-packages] [Bug 2023229] Re: Autopkgtest failure for tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/2023229 Title: Autopkgtest failure for tests-in-lxd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Won't Fix Status in systemd source package in Lunar: Fix Released Status in systemd source package in Mantic: Fix Released Bug description: [Impact] systemd autopkgtests are failing in stable releases due to a change in LXD. We want the tests to be in good shape so that we can properly catch regressions etc. during SRUs. [Test Plan] The tests-in-lxd test should pass. [Where problems could occur] The patch adds a flag to lxc invocation in the debian/tests/tests-in- lxd script, so any problems would be contained to that test. [Original Description] Autopackagetests on multiple Jammy kernels show the same failure on the test-in-lxd test Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64 autopkgtest [16:33:58]: test tests-in-lxd: ---] autopkgtest [16:33:58]: test tests-in-lxd: - - - - - - - - - - results - - - - - - - - - -
[Touch-packages] [Bug 2023462] Re: chromeos_pstore.service started on non chrome platform hardware.
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/2023462 Title: chromeos_pstore.service started on non chrome platform hardware. Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] Kernel modules that provide pstore backends are unnecessarily loaded by systemd-pstore.service. While this is pretty benign behavior, it was introduced by an earlier SRU (bug 1978079) and is not consistent with newer releases in which systemd-pstore.service only tries to load efi_pstore. [Test Plan] Check which modules systemd-pstore.service depends on: $ systemctl list-dependencies systemd-pstore.service systemd-pstore.service * |--.mount * |-modprobe@chromeos_pstore.service * |-modprobe@efi_pstore.service * |-modprobe@pstore_blk.service * |-modprobe@pstore_zone.service * |-modprobe@ramoops.service * `-system.slice On an affected machine, we see several pstore providers in addition to efi_pstore. On a patched system, we should only see efi_pstore. [Where problems could occur] If somehow a user was running a configuration where one of
[Touch-packages] [Bug 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/2025563 Title: System can not shutdown if system has multiple VROC RAID arrays Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [ Impact ] The system can not shutdown if the system has multiple VROC RAID arrays. Intel has fixed it in systemd v251 [1]. Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9. [1] The commit fixes the issue: commit 3a3b022d2cc112803ea7b9beea98bbcad110368a Author: Mariusz Tkaczyk Date: Tue Mar 29 12:49:54 2022 +0200 shutdown: get only active md arrays. Current md_list_get() implementation filters all block devices, started from "md*". This is ambiguous because list could contain: - partitions created upon md device (mdXpY) - external metadata container- specific type of md array. For partitions there is no issue, because they aren't handle STOP_ARRAY ioctl sent later. It generates misleading errors only.
[Touch-packages] [Bug 2028180] Re: [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id
This bug was fixed in the package systemd - 249.11-0ubuntu3.10 --- systemd (249.11-0ubuntu3.10) jammy; urgency=medium [ Nick Rosbrook ] * debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229) File: debian/tests/tests-in-lxd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=85b2ceddff1a6cc1ddbca8a1b7e5381d146e6313 * pstore: only try to load efi_pstore module (LP: #2023462) File: debian/patches/lp1978079-efi-pstore-not-cleared-on-boot.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7600bbfb1e8a399e5aeb1010a20deda3e5a06c89 * shutdown: get only active md arrays. (LP: #2025563) File: debian/patches/lp2025563-shutdown-get-only-active-md-arrays.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=416a9245c8f0efbedcc4395cada23cb09c685ec3 * udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180) File: debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=26e85b944da9098e66fc0c39f64ee40254c0c278 * core: reorder systemd arguments on reexec (LP: #2013543) File: debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=19ba0f20d311642596dc65fa5d6eb96a2d4be280 * network/dhcp4: do not ignore the gateway even if the destination is in same network (LP: #2009743) Files: - debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch - debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=73e774a2fb99c82df6d0edd770bb84ab735ec2f0 * Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP: #1982218) File: debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=cf82f08feea456e1c65895b34bffa8c33d421588 * debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543 File: debian/systemd.postinst https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=be484dab06d590b1792a8f016f4292373d0174b7 * binfmt: fix systemd-binfmt in LXD containers (LP: #1999275) Files: - debian/patches/lp1999275/binfmt-check-if-binfmt-is-mounted-before-applying-rules.patch - debian/patches/lp1999275/binfmt-util-also-check-if-binfmt-is-mounted-in-read-write.patch - debian/patches/lp1999275/binfmt-util-split-out-binfmt_mounted.patch - debian/patches/lp1999275/unit-check-more-specific-path-to-be-written-by-systemd-bi.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0b9eadf05ee6db0e009dacbc71521480095880b3 [ Dan Streetman ] * Fix machinectl pull-tar and import-tar (LP: #1977630) Author: Dan Streetman File: debian/patches/lp1977630-fix_machinectl_pull_tar.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1e7d3febe1600c6eb03bd71a17be6a6af52988c7 * make machinectl read-only work (LP: #1991829) Author: Dan Streetman File: debian/patches/lp1991829-add-CAP_LINUX_IMMUTABLE-to-systemd-machined-so-it-ca.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7a7c47569e0a2d175915eb0b79c60f2611848731 -- Nick Rosbrook Mon, 21 Aug 2023 17:11:40 -0400 ** Changed in: systemd (Ubuntu Jammy) Status: Triaged => 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/2028180 Title: [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Won't Fix Status in systemd source package in Lunar: Fix Released Status in systemd source package in Mantic: Fix Released Bug description: [Impact] When working with NVMe/TCP host functionality, connecting to NVMe subsystem through multiple controllers can lead to an invalid device link created in /dev/disc/by-id/ being created. Steps to reproduce: Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system. Step 2: Install nvme-cli package, currently installed version is nvme version 1.16 Step 3: In the os terminal, type any nvme connect-all to connect to NVMe subsystems and check the duplicate entries in /dev/disk/by-id/. This may cause users to choose the wrong link and would not be able to work with it. [Fix] udev-rules: fix nvme symlink creation on namespace changes
[Touch-packages] [Bug 2028180] Re: [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id
** Tags removed: verification-failed-jammy ** Tags added: verification-done-jammy -- 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/2028180 Title: [SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Won't Fix Status in systemd source package in Lunar: Fix Released Status in systemd source package in Mantic: Fix Released Bug description: [Impact] When working with NVMe/TCP host functionality, connecting to NVMe subsystem through multiple controllers can lead to an invalid device link created in /dev/disc/by-id/ being created. Steps to reproduce: Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system. Step 2: Install nvme-cli package, currently installed version is nvme version 1.16 Step 3: In the os terminal, type any nvme connect-all to connect to NVMe subsystems and check the duplicate entries in /dev/disk/by-id/. This may cause users to choose the wrong link and would not be able to work with it. [Fix] udev-rules: fix nvme symlink creation on namespace changes https://github.com/systemd/systemd/commit/c5ba7a2a4dd19a2d31b8a9d52d3c4bdde78387f0 [Test Plan] Connect to NVMe/TCP subsystem using nvme connect-all. This was tested against a few Dell Storage systems. Steps to Reproduce: 1. Use nvme connect-all to connect to an NVMe/TCP subsystems 2. Check /dev/disk/by-id. The symlinks for NVMe devices should have the namespace id appended to them. E.g., if there is /dev/disk/by-id/nvme-$FOO, there should be a /dev/disk/by-id/name-$FOO_$ID. [ Where problems could occur ] This issue may be experienced by users who use NVMe/TCP solutions. Regression risk is low, because the existing symlink pattern is kept for backwards compatibility. This patch adds a new symlink pattern that includes the namespace ID, which will remain persistent throughout a boot. [ Other Info ] Expected Behavior: No duplicate entries of NVMe subsystems should exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2028180/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Your original bug report was about an upgrade from 249.11-0ubuntu3.9 (the previous SRU version we've now rolled back to) to 249.11-0ubuntu3.10 (the withdrawn SRU which is currently in jammy- proposed). > Downgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7) This shows that after reinstall, you installed the -0ubuntu3.9 version that you reported you already had installed before encountering this bug; and then downgraded to -0ubuntu3.7, the version in jammy-security. If you are saying that, after upgrading to -0ubuntu3.9, the problem with camera devices was still reproducible for you, then it is definitively not caused by any of the changes in -0ubuntu3.10. I will therefore be re-releasing the -0ubuntu3.10 SRU. We are still more than willing to assist you in determining the cause of the problems you're experiencing, but the evidence is not there that this is caused by the latest SRU. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2036128] [NEW] [FFe] enable unprivileged user namespace restrictions by default for mantic
Public bug reported: As per https://discourse.ubuntu.com/t/spec-unprivileged-user-namespace- restrictions-via-apparmor-in-ubuntu-23-10/37626, unprivileged user namespace restrictions for Ubuntu 23.10 are to be enabled by default via a sysctl.d conf file in apparmor. In https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2035315 new apparmor profiles were added to the apparmor package for various applications which require unprivileged user namespaces, using a new unconfined profile mode. To support this an additional change was added to the mantic kernel in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/commit?h=master- next=7327726a2dbf571e05f7c095916dcce0347790b4 which is still currently unreleased. Without this kernel change, if userns restrictions are enabled the existing policies added above will not actually work to allow them to be used by the various applications. As such we need to ensure that userns restrictions are not enabled via sysctl when this feature is not present / enabled. Whilst it may be possible to capture the dependency logic via `Breaks:` or similar, this would not help in the case that a user booted into an older kernel with the new apparmor userspace package. As such, as well as enabling the sysctl via the sysctl.d conf file, it is proposed to add logic into the apparmor.service systemd unit to check that the kernel supports the aforementioned unconfined profile mode and that it is enabled - and if not then to force disable the userns restrictions sysctl via the following logic: userns_restricted=$(sysctl -n kernel.apparmor_restrict_unprivileged_userns) unconfined_userns=$([ -f /sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns ] && cat /sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns || echo 0) if [ -n "$userns_restricted" ] && [ "$userns_restricted" -eq 1 ]; then if [ $unconfined_userns -eq 0 ]; then # userns restrictions rely on unconfined userns to be supported echo "disabling unprivileged userns restrictions since unconfined userns is not supported / enabled" sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 fi fi this allows a local admin to disable the sysctl via the regular sysctl.d conf approach, but to also make sure we don't inadvertently enable it when it is not supported by the kernel. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/2036128 Title: [FFe] enable unprivileged user namespace restrictions by default for mantic Status in apparmor package in Ubuntu: New Bug description: As per https://discourse.ubuntu.com/t/spec-unprivileged-user- namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626, unprivileged user namespace restrictions for Ubuntu 23.10 are to be enabled by default via a sysctl.d conf file in apparmor. In https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2035315 new apparmor profiles were added to the apparmor package for various applications which require unprivileged user namespaces, using a new unconfined profile mode. To support this an additional change was added to the mantic kernel in https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/commit?h=master- next=7327726a2dbf571e05f7c095916dcce0347790b4 which is still currently unreleased. Without this kernel change, if userns restrictions are enabled the existing policies added above will not actually work to allow them to be used by the various applications. As such we need to ensure that userns restrictions are not enabled via sysctl when this feature is not present / enabled. Whilst it may be possible to capture the dependency logic via `Breaks:` or similar, this would not help in the case that a user booted into an older kernel with the new apparmor userspace package. As such, as well as enabling the sysctl via the sysctl.d conf file, it is proposed to add logic into the apparmor.service systemd unit to check that the kernel supports the aforementioned unconfined profile mode and that it is enabled - and if not then to force disable the userns restrictions sysctl via the following logic: userns_restricted=$(sysctl -n kernel.apparmor_restrict_unprivileged_userns) unconfined_userns=$([ -f /sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns ] && cat /sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns || echo 0) if [ -n "$userns_restricted" ] && [ "$userns_restricted" -eq 1 ]; then if [ $unconfined_userns -eq 0 ]; then # userns restrictions rely on unconfined userns to be supported echo "disabling unprivileged userns restrictions since unconfined userns is not supported / enabled" sysctl -w
[Touch-packages] [Bug 2035220] Re: cve-2023-4863
** Changed in: libwebp (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in firefox-esr package in Ubuntu:
Confirmed
Status in libwebp package in Ubuntu:
Confirmed
Status in thunderbird package in Ubuntu:
Fix Released
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
Fix Released
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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 2034261] Re: [FFe] Restore the desktop non-minimal option
That was a very sane decision. Thank you. Just a minimal option that doesn't install the desktop-recommends is good enough, I think. -- 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/2034261 Title: [FFe] Restore the desktop non-minimal option Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Following the decision on https://discourse.ubuntu.com/t/thank-you- for-the-passionate-discussion-an-update-on-installation-options-and- provisioning-overhaul we want to revert the change which removed 'minimal' from the desktop ISO. We basically want to go back to what we had previous cycle but change the default selection to be 'minimal' (and probably relabel the options) It will require reverting also the changes we did to debian-cd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2034261/+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 2034261] Re: [FFe] Restore the desktop non-minimal option
This bug was fixed in the package ubuntu-meta - 1.520 --- ubuntu-meta (1.520) mantic; urgency=medium * Refreshed dependencies * Make changes to restore desktop non-minimal install option (LP: #2034261) * Added aisleriot to desktop-raspi-recommends, desktop-recommends * Added branding-ubuntu to desktop-raspi-recommends, desktop- recommends * Added cheese to desktop-raspi-recommends, desktop-recommends * Added file-roller to desktop-raspi-recommends, desktop-recommends * Added gnome-mahjongg to desktop-raspi-recommends, desktop-recommends * Added gnome-mines to desktop-raspi-recommends, desktop-recommends * Added gnome-sudoku to desktop-raspi-recommends, desktop-recommends * Added hplip to desktop-minimal-recommends, desktop-raspi-recommends, desktop-recommends * Added libreoffice-calc to desktop-raspi-recommends, desktop- recommends * Added libreoffice-gnome to desktop-raspi-recommends, desktop- recommends * Added libreoffice-impress to desktop-raspi-recommends, desktop- recommends * Added libreoffice-math to desktop-raspi-recommends, desktop- recommends * Added libreoffice-style-yaru to desktop-raspi-recommends, desktop- recommends * Added libreoffice-writer to desktop-raspi-recommends, desktop- recommends * Added remmina to desktop-raspi-recommends, desktop-recommends * Added rhythmbox to desktop-raspi-recommends, desktop-recommends * Added shotwell to desktop-raspi-recommends, desktop-recommends * Added simple-scan to desktop-raspi-recommends, desktop-recommends * Added thunderbird to desktop-raspi-recommends, desktop-recommends * Added thunderbird-gnome-support to desktop-raspi-recommends, desktop- recommends * Added transmission-gtk to desktop-raspi-recommends, desktop- recommends -- Jeremy Bícha Thu, 14 Sep 2023 18:28:42 -0400 ** Changed in: ubuntu-meta (Ubuntu) Status: Fix Committed => Fix Released -- 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/2034261 Title: [FFe] Restore the desktop non-minimal option Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Following the decision on https://discourse.ubuntu.com/t/thank-you- for-the-passionate-discussion-an-update-on-installation-options-and- provisioning-overhaul we want to revert the change which removed 'minimal' from the desktop ISO. We basically want to go back to what we had previous cycle but change the default selection to be 'minimal' (and probably relabel the options) It will require reverting also the changes we did to debian-cd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2034261/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
22.04.3LTS -Ubuntu Downgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.7) Camera any kind, I tried both my NikonD5600 and Olympus OM-D E-M5, which both work again as they should and did before this mess started. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2036127] [NEW] Restarting `systemd-networkd` looses unmanaged bridged parents
Public bug reported: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd-networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 3. Restart `systemd-networkd` $ lxc exec networkd-bug -- systemctl restart systemd-networkd 4. Notice `vlan1` lost it's master config $ lxc exec networkd-bug -- ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: vlan1@eth0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff 3: br0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 42:b6:31:01:47:9a brd ff:ff:ff:ff:ff:ff 164: eth0@if165: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:16:3e:94:6e:47 brd ff:ff:ff:ff:ff:ff link-netnsid 0 Ideally, `vlan1` should retain it's `master` setting and I wouldn't loose connectivity :) Additional information: # apt-cache policy systemd netplan.io iproute2 systemd: Installed: 249.11-0ubuntu3.9 Candidate: 249.11-0ubuntu3.9 Version table: *** 249.11-0ubuntu3.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3.7 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 249.11-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages netplan.io: Installed: 0.105-0ubuntu2~22.04.3 Candidate: 0.105-0ubuntu2~22.04.3 Version table: *** 0.105-0ubuntu2~22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.104-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages iproute2: Installed: 5.15.0-1ubuntu2 Candidate: 5.15.0-1ubuntu2 Version table: *** 5.15.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 # uname -a Linux networkd-bug 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/2036127 Title: Restarting `systemd-networkd` looses unmanaged bridged parents Status in systemd package in Ubuntu: New Bug description: My home network comprises many VLANs managed by `systemd- networkd`/`netplan`. Those VLANs are then used as parent interfaces for LXD networks. Whenever `systemd-networkd` is restarted (i.e: post- update), my whole network breaks because all the unmanaged bridges lose their parent devices. Another way to see it is that `systemd- networkd` undoes the `master` setting of those VLAN devices. Here is a simplified reproducer: 1. Create a `vlan1` device $ lxc launch ubuntu:22.04 networkd-bug Creating networkd-bug Starting networkd-bug $ lxc file push - networkd-bug/etc/netplan/99-vlan1.yaml << EOF network: version: 2 vlans: vlan1: id: 1 link: eth0 EOF $ lxc exec networkd-bug -- netplan apply 2. Manually create a bridge and join `vlan1` to it $ lxc exec networkd-bug -- ip link add br0 type bridge $ lxc exec networkd-bug -- ip link set vlan1 master br0 $ lxc exec networkd-bug
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
To reproduce your problem, can you specify steps to reproduce (with version numbers)? Which Ubuntu image did you use for installation? To which udev version did you downgrade? Which camera do you have and how did you connect it to your computer? -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2036124] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
350 MiB for /boot is a little bit too small especially when you have nvidia drivers installed. You could try compress the initramfs with xz with a high level. I am marking this bug as invalid since is it caused by a full /boot partition. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/2036124 Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: A crash notification popped up when I was not doing anything so I'm not sure what caused it. I hope the automatically-added debug information contains something useful. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Sep 11 00:24:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (704 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-08-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036124/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Tried all your steps, they kept breaking my system more and more. Had to re-install ubutnu from liveusb, installed synaptic downgraded udev and locked verison, read markings, reboot, update, upgrade reboot, get my audio and bluetooth up and working again reboot, everything works, its your udev update, dont know how, dont know why, and not sure how my system is the only one effected, but its your udev update. Thanks for your help, hope you figure it out before it causes more issues wide spread. Im out for now on this bug. As fresh install and down grade udev and locking version has everything working again. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2034261] Re: [FFe] Restore the desktop non-minimal option
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Committed -- 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/2034261 Title: [FFe] Restore the desktop non-minimal option Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: Following the decision on https://discourse.ubuntu.com/t/thank-you- for-the-passionate-discussion-an-update-on-installation-options-and- provisioning-overhaul we want to revert the change which removed 'minimal' from the desktop ISO. We basically want to go back to what we had previous cycle but change the default selection to be 'minimal' (and probably relabel the options) It will require reverting also the changes we did to debian-cd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2034261/+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 2036124] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Looking at the attached, it looks like I'm out of space on /boot again. It looks like maybe https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154 intended to fix this, but I seem to only have room for two kernels in /boot. -- 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/2036124 Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: A crash notification popped up when I was not doing anything so I'm not sure what caused it. I hope the automatically-added debug information contains something useful. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Sep 11 00:24:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (704 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-08-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036124/+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 2036124] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** 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/2036124 Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: A crash notification popped up when I was not doing anything so I'm not sure what caused it. I hope the automatically-added debug information contains something useful. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Sep 11 00:24:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (704 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-08-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036124/+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 2036124] [NEW] package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: A crash notification popped up when I was not doing anything so I'm not sure what caused it. I hope the automatically-added debug information contains something useful. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Sep 11 00:24:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (704 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-08-23 (22 days ago) ** 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/2036124 Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: A crash notification popped up when I was not doing anything so I'm not sure what caused it. I hope the automatically-added debug information contains something useful. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Sep 11 00:24:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (704 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-08-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036124/+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
Re: [Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
> pipewire:i386 This explains the loss of audio after downgrade. Unfortunately the semantics of package pins do not match on foreign-arch packages without explicitly listing the arch name. And for some reason, you had pipewire installed on your system for the wrong architecture. Julian's apt commandline approach appears to avoid this problem. But you appear to have committed the results of either the pin-based downgrade or a synaptic downgrade, without paying attention to the caveat that it should not remove any packages. So 'apt install pipewire' (NOT pipewire:i386) should have fixed the audio regression. It's still the case that, if the camera problem was still visible after downgrading all of the binaries that were part of the systemd source package, there is nothing that points to the camera behavior change being the result of the systemd update. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2016252]
Has this been addressed(*)? If so, could the respective commit ID's be
posted here for reference, please?
(*) https://sourceware.org/pipermail/libc-alpha/2023-June/148812.html would
suggest that it was but perhaps not entirely?
--
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/2016252
Title:
qemu-system-x86_64 crashes inside nested VM
Status in GLibC:
Confirmed
Status in glibc package in Ubuntu:
Fix Released
Status in qemu package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Bug description:
Systemd package has autopkgtests
the upstream-2 test cases use upstream systemd testsuite, i.e. make -C
str/test/TEST-70-TPM2 setup run
it launches a nested VM to do quick tests inside it.
It appears that qemu-system-x86_64 crashes in such cases:
TEST-70-TPM2 RUN: cryptenroll/cryptsetup with TPM2 devices
+ timeout --foreground 1800 /bin/qemu-system-x86_64 -smp 4 -net none -m 1024M
-nographic -vga none -kernel /boot/vmlinuz-6.2.0-1003-lowlatency -drive
format=raw,cache=unsafe,file=/var/tmp/systemd-test.G2RH6i/tpm2.img -device
virtio-rng-pci,max-bytes=1024,period=1000 -chardev
socket,id=chrtpm,path=/tmp/tmp.cRBa43SrLC/sock -tpmdev
emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0 -initrd
/boot/initrd.img-6.2.0-1003-lowlatency -append 'root=LABEL=systemd_boot rw
raid=noautodetect rd.luks=0 loglevel=2 init=/lib/systemd/systemd console=ttyS0
SYSTEMD_UNIT_PATH=/usr/lib/systemd/tests/testdata/testsuite-70.units:/usr/lib/systemd/tests/testdata/units:
systemd.unit=testsuite.target systemd.wants=testsuite-70.service oops=panic
panic=1 softlockup_panic=1 systemd.wants=end.service'
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info: Assertion
`(isize & (isize - 1)) == 0' failed.
timeout: the monitored command dumped core
..//test-functions: line 377: 152120 Aborted ( set -x;
"${qemu_cmd[@]}" "${qemu_options[@]}" -append "${kernel_params[*]}" )
E: qemu failed with exit code 134
The important bit seems to be:
qemu-system-x86_64: ../../util/cacheflush.c:208: init_cache_info:
Assertion `(isize & (isize - 1)) == 0' failed.
Which is an assert inside qemu source code.
Is the systemd test suite VM setup doing something wrong, or is there
something wrong in qemu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/2016252/+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 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable
> When working with ubuntu core or ubuntu core desktop, neither > /etc/default/locale > nor /etc/default/keyboard are modificable They should be. This needs to be fixed in Ubuntu Core, not in systemd. -- 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/2035122 Title: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable Status in systemd package in Ubuntu: New Status in systemd source package in Jammy: New Bug description: When working with ubuntu core or ubuntu core desktop, neither /etc/default/locale nor /etc/default/keyboard are modificable, so it's not possible to set the global keyboard or the global language. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+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
Re: [Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
On Thu, Sep 14, 2023 at 07:52:49PM -, Philip A Swiderski Jr wrote: > PROBLEM STILL PERSISTS, and Now I HAVE NO AUDIO. You didn't show the output of the apt command or otherwise confirm, but I did stipulate that: > This should offer to downgrade all binary packages from the systemd source > package to the current jammy-updates versions, without removing any other > packages. If other packages were removed, but you proceeded with the downgrade, then there could understandably be other regressions. If no other packages were removed, but systemd was downgraded to the 249.11-0ubuntu3.9 version that you had installed before the most recent stable release update, and you are having these problems, then there is no evidence to indicate these problems are caused by either the downgrade, OR the upgrade of systemd. > Because they can not talk to the camera, I understand the appimage has > everything self contained, so it makes sense it works that way. No, that doesn't make sense, because the only point at which any of these applications, either as appimage or deb, should be interacting with anything handled by systemd, is when opening the device file and either succeeding or getting permission denied. This is a question of udev acls, which should apply equally to the appimage and the native .deb, unless the appimage runs as a different user with different privileges. (And if it runs with different privileges, whatever is setting up those "different privileges" could be the actual source of your bug.) My next step for debugging this problem would be to run 'strace -efile digikam 2>&1 | grep /dev.*EPERM' to confirm whether there is a permissions problem on your device files. > Now back to re-installing > ubuntu and putting it all back together, hoping your update does not > break it again. Yours is the only bug report of problems with this SRU and it so far has not been reproducible. If we continue to be unable to reproduce it and you are not able to assist with further debugging to isolate the problem on your system, then this bug will eventually be closed and the update will be re-published to jammy-updates. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias:
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
PROBLEM STILL PERSISTS, and Now I HAVE NO AUDIO. No I have to do a fresh install. You guys really need to pay better attention to your updates, this is a system break not an upgrade. Im really not happy, and as I love ubuntu, and I really appreciate all the hard work you guys all put into making and keeping it great, sometimes I wish you took just a few extra minuets to verify nothing will break with your new updates. It sure would saved all of us a bunch of work. Now back to re-installing ubuntu and putting it all back together, hoping your update does not break it again. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
A shorter version that avoids the preferences file is: sudo apt update && sudo apt install --no-remove '?installed?source- package(^systemd$)/jammy-updates' Unless something else depends on a newer systemd in which case both don't work, but essentially this should. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Please install the attached apt preferences file to /etc/apt/preferences.d/ (as root) and then run 'sudo apt update && sudo apt upgrade'. This should offer to downgrade all binary packages from the systemd source package to the current jammy-updates versions, without removing any other packages. After doing so, you can run 'sudo rm /etc/apt/preferences.d/systemd- downgrade /lib/udev/rules.d/60-persistent-storage.rules.bak'. Then reboot and let us know whether the problem with digikam, gphoto2, et al persists. ** Attachment added: "systemd-downgrade" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+attachment/5701003/+files/systemd-downgrade -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
More interesting info, so I just tested digiKam-8.1.0-x86-64.appimage and it Can talk to my camera, but the Installed digikam package CAN NOT TALK, but I still can not use gphoto2 to stream my camera, nor can I use entangle to use my camera tethered. Because they can not talk to the camera, I understand the appimage has everything self contained, so it makes sense it works that way. But I wanted to let you know, as somehow it may be useful to figuring out this very odd bug. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Dont know if this helps, but here is a complete list of installed libnova-0.16-0 install libgpg-error-l10n install dpkginstall kerneloops install libkf5quickaddons5 install golang-golang-x-term-devinstall fontconfig:i386 install r-cran-quantreg install libkdecorations2-5v5install libvulkan1 install libvulkan1:i386 install telnet install libgdal30 install libkf5alarmcalendar5abi2install r-cran-evd install signon-ui-service install libdleyna-core-1.0-5install libnetfilter-conntrack3 install php-composer-metadata-minifier install python3-incremental install libkf5wallet-data install megapixels install libqt5webengine-datainstall php-symfony-config install libkf5konq6 install breeze install libkf5mailtransportakonadi5 install lsb-release install libtext-unidecode-perl install clamav-daemon install libpulse-java install puredata-import install libpipewire-0.3-dev install libevent-pthreads-2.1-7 install plasma-runners-addons install r-cran-fnn install r-cran-mlmetricsinstall clamav-milter install gconf2-common install fonts-cantarell install r-cran-fts install libgucharmap-2-90-7 install python3-pyxattr install libsphinxbase3 install librust-syn+printing-devinstall libkf5identitymanagement5abi1 install python3-parso install libklu1 install libkf5kdelibs4support5-bin install cervisiainstall libjs-prettify install r-cran-jquerylibinstall libssh2-1 install libcuda1-340install libsub-exporter-perlinstall fonts-sil-andikainstall libsynctex2 install tcpdump install libperl5.34 install node-highlight.js install libokular5core10install fonts-tlwg-purisa-ttf install fonts-tibetan-machine install vlc-plugin-qt install libsimage-dev install tracker install libopenblas0install openjdk-11-jre install xserver-xorg-video-nouveau install libblkid-devinstall dmidecode install r-cran-gsl install libspa-0.2-dev install libel-api-java install r-cran-spatstat.sparse install libcups2install jalvinstall libpoppler-qt5-1install libneon27-gnutlsinstall libkf5dav-data install lintian install gnustep-back0.29install qttranslations5-l10ninstall pkg-kde-tools install libxcb-present0 install libxcb-present0:i386install libvlc5 install libxapian30 install libwrap0install python3-jediinstall r-cran-hms install dvipng install fonts-kacst-one install python3-appdirs install libcanberra-gtk3-0 install reiserfsprogs install libkf5kipi32.0.0install node-acorn install libkeyutils1install libkeyutils1:i386 install libmrpt-common-dev install libkf5mailimporterakonadi5 install python3-pycparser install python3-blinker install lsp-plugins-lv2 install gstreamer1.0-qt5install qtchooser install debhelper install ruby-sdbm install libkf5widgetsaddons5install kwave install qtspeech5-flite-plugin install libyajl2install libhtml-treebuilder-xpath-perl install python3-pyclamd install libhtml-treebuilder-libxml-perl install libselinux1-dev install r-cran-ini install chafa install libxtables12install libkpimimportwizard5install libcurl4install fonts-jura install libpolkit-agent-1-0 install dv4linstall libupower-glib3 install libxml-namespacesupport-perlinstall dmeventdinstall fonts-lohit-beng-bengaliinstall libqt5websockets5 install golang-go install librust-winapi-x86-64-pc-windows-gnu-devinstall filelight install libkf5baloowidgets-data install libalgorithm-merge-perl install libobasis7.6-librelogo install libcsound64-6.0 install gir1.2-wp-0.4 install qastools-common install
[Touch-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted
I've tested the kernel from focal-proposed, with the systemd packages from my personal PPA (as the systemd patches aren't yet available in focal-proposed). All test variants from the rep-tmpfs.sh script ran succesfully, and general smoke testing revealed no further issues. ubuntu@z-rotomvm35:~$ uname -rv 5.4.0-164-generic #181-Ubuntu SMP Fri Sep 1 13:41:22 UTC 2023 ubuntu@z-rotomvm35:~$ dpkg -l systemd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--= ii systemd245.4-4ubuntu3.22+20230626dbg2 amd64system and service manager ** Tags removed: verification-needed-focal-linux ** Tags added: verification-done-focal-linux -- 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/1837227 Title: systemd mount units fail during boot, while file system is correctly mounted Status in systemd: New Status in Ubuntu Pro: In Progress Status in Ubuntu Pro 18.04 series: In Progress Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in systemd source package in Bionic: Won't Fix Status in linux source package in Focal: Fix Committed Status in systemd source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] systemd mount units fail during boot, and the system boots into emergency mode [Test Plan] This issue seems to happen randomly, and doesn't seem related to a specific mount unit. We've used a test script with good results during investigation to reproduce similar mount failures in a running system, and have seen a strong correlation between the script failures and the boot time mount failures. The attached 'rep-tmpfs.sh' script should be used to validate that mount points are working correctly under stress. One can run through the different variants as below: # ./rep-tmpfs.sh --variant-0 # ./rep-tmpfs.sh --variant-1 # ./rep-tmpfs.sh --variant-2 # ./rep-tmpfs.sh --variant-3 # ./rep-tmpfs.sh --variant-4 All of these should run successfully without any reported errors. [Where problems could occur] The patches change the way systemd tracks and handles mount points in general, so potential regressions could affect other mount units. We should keep an eye out for any issues with mounting file systems, as well as rapid mount/unmount operations. Successful test runs with the reproducer script should increase reliability in having no new regressions. [Other Info] This has been tackled upstream with several attempts, which have resulted in the final patch from 2022: 01400460ae16 core/mount: adjust deserialized state based on /proc/self/mountinfo For Bionic, systemd requires several dependency patches as below: 6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a new unit cycle 7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the other way round 350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() results 1d086a6e5972 mount: mark an existing "mounting" unit from /proc/self/mountinfo as "just_mounted" Additionally, the kernel also requires the following patches: 28ca0d6d39ab list: introduce list_for_each_continue() 9f6c61f96f2d proc/mounts: add cursor [Original Description] In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode with a failed mount unit (ext4 file system), while the corresponding file system is in fact correctly mounted. It happens roughly once every 1000 reboots. It seems to be related with this bug : https://github.com/systemd/systemd/issues/10872 Is it possible to apply the fix (https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21) in Ubuntu 18.04 ? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837227/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Tried to stream with debug,
gphoto2 --stdout --capture-movie --debug | ffmpeg -i - -vcodec rawvideo
-pix_fmt yuv420p -threads 0 -f v4l2 /dev/video0
0.000107 main(2): ALWAYS INCLUDE THE FOLLOWING LINES
WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000131 main(2): gphoto2 2.5.27
0.000137 main(2): gphoto2 has been compiled with the
following options:
0.000145 main(2): + gcc (C compiler used)
0.000148 main(2): + popt (mandatory, for handling
command-line parameters)
0.000151 main(2): + exif (for displaying EXIF
information)
0.000154 main(2): + cdk (for accessing configuration
options)
0.000157 main(2): + aa (for displaying live previews)
0.000161 main(2): + jpeg (for displaying live previews
in JPEG format)
0.000164 main(2): + readline (for easy navigation in
the shell)
0.000172 main(2): libgphoto2 2.5.31
0.000175 main(2): libgphoto2 has been compiled with the
following options:
0.000180 main(2): + standard camlib set SKIPPING SOME
(ax203 canon digigr8 dimagev directory jl2005a jl2005c kodak_dc240 mars pentax
ptp2 ricoh_g3 sierra sonix sq905 st2205 topfield tp6801 SKIPPING docupen lumix)
0.000184 main(2): + gcc (C compiler used)
0.000187 main(2): + no ltdl (for portable loading of
camlibs)
0.000190 main(2): + EXIF (for special handling of EXIF
files)
0.000196 main(2): libgphoto2_port 0.12.2
0.000200 main(2): libgphoto2_port has been compiled
with the following options:
0.000203 main(2): + iolibs: disk ptpip serial
0.000206 main(2): + gcc (C compiler used)
0.000211 main(2): + no ltdl (for portable loading of
iolibs)
0.000214 main(2): + EXIF (for vusb)
0.000217 main(2): + no USB (for USB cameras)
0.000221 main(2): + serial (for serial cameras)
0.000224 main(2): + no resmgr (serial port access and
locking)
0.000227 main(2): + no ttylock (serial port locking)
0.000230 main(2): + no lockdev (serial port locking)
0.000235 main(2): CAMLIBS env var not set, using
compile-time default instead
0.000238 main(2): IOLIBS env var not set, using
compile-time default instead
0.000242 main(2): invoked with following arguments:
0.000245 main(2): --stdout
0.000248 main(2): --capture-movie
0.000252 main(2): --debug
0.000268 load_settings (2): Creating gphoto config directory
('/home/pasjrwoctx/.gphoto')
0.000306 load_settings (2): Loading settings from file
'/home/pasjrwoctx/.gphoto/settings'.
0.000341 main(2): The user has not specified both a
model and a port. Try to figure them out.
0.000347 gp_port_init_localedir (2): localedir has been set to
/usr/local/share/locale (compile-time default)
0.000353 gp_port_info_list_load (2): Using ltdl to load io-drivers from
'/usr/local/lib/libgphoto2_port/0.12.2'...
0.000410 foreach_func(2): Called for filename
'/usr/local/lib/libgphoto2_port/0.12.2/disk'.
0.000644 gp_port_library_list(2): found fstab fstype vfat
0.000660 gp_port_library_list(2): found fstab fstype ext4
0.000667 gp_port_library_list(2): found fstab fstype ext4
0.000676 gp_port_library_list(2): found fstab fstype tmpfs
0.000757 gp_port_library_list(2): found mtab fstype sysfs
0.000763 gp_port_library_list(2): found mtab fstype proc
0.000767 gp_port_library_list(2): found mtab fstype devtmpfs
0.000779 gp_port_library_list(2): found mtab fstype devpts
0.000784 gp_port_library_list(2): found mtab fstype tmpfs
0.000794 gp_port_library_list(2): found mtab fstype ext4
0.000801 gp_port_library_list(2): found mtab fstype securityfs
0.000805 gp_port_library_list(2): found mtab fstype tmpfs
0.000817 gp_port_library_list(2): found mtab fstype tmpfs
0.000829 gp_port_library_list(2): found mtab fstype cgroup2
0.000833 gp_port_library_list(2): found mtab fstype pstore
0.000846 gp_port_library_list(2): found mtab fstype bpf
0.000857 gp_port_library_list(2): found mtab fstype autofs
0.000863 gp_port_library_list(2): found mtab fstype mqueue
0.000890 gp_port_library_list(2): found mtab fstype hugetlbfs
0.000902 gp_port_library_list(2): found mtab fstype debugfs
0.000912
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
In order to roll back udev in Synaptic, I get To Be Removed libgstreamer-plugins-base1.0-dev libgudev-1.0-dev libnm0:i386 libpipewire-0.3-0:i386 libpipewire-0.3-modules:i386 libspa-0.2-modules:i386 libudev-dev libudev1:i386 pipewire:i386 steam:i386 To be downgraded libudev1 I cant roll back or lose functionality and software. Im not sure how all this works together, but that update really messed things up, and I am no Programmer or Engineer, but normally I can with a little bit of digging, figure things out, but this has me very confused, as none of this should be tied together, and the bug has to do with how udev handles protocols for camera to software, because the computer can in fact see the camera when attached, the software is simply blocked from seeing the camera. USB harddrive not affected, I tried to reprogram my hand held Ham radio via usb, worked fine, it simply between what ever protocols ubuntu, udev and software packages use to see and communicate with cameras. And as a digital creator, this is a huge issue for me. If I do a fresh install I lose another 2 days getting everything back up running, not to mention I dont have extra drives right now for backing up, nor the funds to buy one, also the reason I have yet to, is if I do, and go to update, and this all happens again, then I am further behind. So I am trying to figure out how this update broke my system, and fix it so it is right. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035977] [NEW] PCI/internal sound card not detected
Public bug reported: No sound. Impossible to install the driver for hp 850 G6 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 14 18:44:33 2023 InstallationDate: Installed on 2023-09-12 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2022 dmi.bios.release: 22.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.22.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.6E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.110 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.22.00:bd10/14/2022:br22.0:efr82.110:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.6E.00:cvnHP:ct10:cvr:sku6XD55EA#ABF: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 6XD55EA#ABF dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2035977 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No sound. Impossible to install the driver for hp 850 G6 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 14 18:44:33 2023 InstallationDate: Installed on 2023-09-12 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2022 dmi.bios.release: 22.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.22.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.6E.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.110 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.22.00:bd10/14/2022:br22.0:efr82.110:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.6E.00:cvnHP:ct10:cvr:sku6XD55EA#ABF: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 6XD55EA#ABF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2035977/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
I downloaded your rules and used you commands to move it, I rebooted and
same issue, here is the result of gphoto2 --debug
gphoto2 --debug
0.000101 main(2): ALWAYS INCLUDE THE FOLLOWING LINES
WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST:
0.000114 main(2): gphoto2 2.5.27
0.000127 main(2): gphoto2 has been compiled with the
following options:
0.000129 main(2): + gcc (C compiler used)
0.000131 main(2): + popt (mandatory, for handling
command-line parameters)
0.000132 main(2): + exif (for displaying EXIF
information)
0.000134 main(2): + cdk (for accessing configuration
options)
0.000137 main(2): + aa (for displaying live previews)
0.000140 main(2): + jpeg (for displaying live previews
in JPEG format)
0.000153 main(2): + readline (for easy navigation in
the shell)
0.000157 main(2): libgphoto2 2.5.31
0.000160 main(2): libgphoto2 has been compiled with the
following options:
0.000163 main(2): + standard camlib set SKIPPING SOME
(ax203 canon digigr8 dimagev directory jl2005a jl2005c kodak_dc240 mars pentax
ptp2 ricoh_g3 sierra sonix sq905 st2205 topfield tp6801 SKIPPING docupen lumix)
0.000166 main(2): + gcc (C compiler used)
0.000168 main(2): + no ltdl (for portable loading of
camlibs)
0.000171 main(2): + EXIF (for special handling of EXIF
files)
0.000175 main(2): libgphoto2_port 0.12.2
0.000177 main(2): libgphoto2_port has been compiled
with the following options:
0.000179 main(2): + iolibs: disk ptpip serial
0.000181 main(2): + gcc (C compiler used)
0.000183 main(2): + no ltdl (for portable loading of
iolibs)
0.000185 main(2): + EXIF (for vusb)
0.000187 main(2): + no USB (for USB cameras)
0.000188 main(2): + serial (for serial cameras)
0.000190 main(2): + no resmgr (serial port access and
locking)
0.000192 main(2): + no ttylock (serial port locking)
0.000195 main(2): + no lockdev (serial port locking)
0.000197 main(2): CAMLIBS env var not set, using
compile-time default instead
0.000199 main(2): IOLIBS env var not set, using
compile-time default instead
0.000201 main(2): invoked with following arguments:
0.000203 main(2): --debug
0.000212 load_settings (2): Creating gphoto config directory
('/home/pasjrwoctx/.gphoto')
0.000248 load_settings (2): Loading settings from file
'/home/pasjrwoctx/.gphoto/settings'.
0.000309 gp_camera_free (2): Freeing camera...
0.000312 gp_port_free(2): Freeing port...
0.000325 gp_filesystem_reset (2): resetting filesystem
0.000327 gp_filesystem_lru_clear (2): Clearing fscache LRU list...
0.000329 gp_filesystem_lru_clear (2): fscache LRU list already empty
0.000331 delete_all_folders (2): Internally deleting all folders from
'/'...
0.000333 lookup_folder (2): Lookup folder '/'...
0.000336 lookup_folder (2): Found! / is 0x55cbf0b9e8e0
0.000337 recurse_delete_folder (2): Recurse delete folder 0x55cbf0b9e8e0//
0.000340 delete_all_files(2): Delete all files in folder
0x55cbf0b9e8e0//
Maybe this help?
--
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/2035406
Title:
udev update has broken ubuntu's ability to import photos in digikam,
gphoto2 can no longer see usb camera, entangle can no longer see
camera
Status in systemd package in Ubuntu:
Invalid
Status in systemd source package in Jammy:
Incomplete
Status in systemd source package in Lunar:
Invalid
Status in systemd source package in Mantic:
Invalid
Bug description:
udev update has broken ubuntu's ability to import photos in digikam, gphoto2
can no longer see usb camera, entangle can no longer see camera
after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9,
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9,
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9,
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
The backtrace unfortunately doesn't provide any information that points
to how this could be a systemd problem. The crashing thread appears to
be:
Thread 12 (Thread 0x7f50a9f2e640 (LWP 282533) "ThreadPoolServi"):
#1 0x7f50de277845 in buffered_vfprintf (s=0x7f50de41a6a0
<_IO_2_1_stderr_>, format=format@entry=0x7f50c74e8c85 "[%s] %s\n",
args=args@entry=0x7f50a9f1c1e0, mode_flags=mode_flags@entry=2) at
./stdio-common/vfprintf-internal.c:2265
#2 0x7f50de2766de in __vfprintf_internal (s=,
format=0x7f50c74e8c85 "[%s] %s\n", ap=ap@entry=0x7f50a9f1c1e0, mode_flags=2) at
./stdio-common/vfprintf-internal.c:1236
#3 0x7f50de334ec3 in ___fprintf_chk (fp=, flag=, format=) at ./debug/fprintf_chk.c:33
#4 0x7f50c74cd37e in event_logv_ () at
/lib/x86_64-linux-gnu/libevent-2.1.so.7
#5 0x7f50c74cd549 in event_warn () at
/lib/x86_64-linux-gnu/libevent-2.1.so.7
#6 0x7f50c74d223c in () at /lib/x86_64-linux-gnu/libevent-2.1.so.7
#7 0x7f50c74c95d1 in event_base_loop () at
/lib/x86_64-linux-gnu/libevent-2.1.so.7
#8 0x7f50d357c624 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
since we don't see the format string arguments, this doesn't tell us
what's being printed that's a problem or how it could be systemd-
related.
I'm attaching the /lib/udev/rules.d/60-persistent-storage.rules from the
previous version of systemd, 249.11-0ubuntu3.9. Since this is the only
change in the new version affecting udev, even though we don't see how
it would break your devices, we should test whether reverting this fixes
your problem.
Please download the attached file and run the following commands:
sudo cp -a /lib/udev/rules.d/60-persistent-storage.rules{,.bak}
sudo mv 60-persistent-storage.rules
/lib/udev/rules.d/60-persistent-storage.rules
Then reboot and report whether this has fixed your problem.
If it has not, we can walk you through a full manual rollback of the
systemd package on your system.
** Attachment added: "60-persistent-storage.rules"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+attachment/5700985/+files/60-persistent-storage.rules
--
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/2035406
Title:
udev update has broken ubuntu's ability to import photos in digikam,
gphoto2 can no longer see usb camera, entangle can no longer see
camera
Status in systemd package in Ubuntu:
Invalid
Status in systemd source package in Jammy:
Incomplete
Status in systemd source package in Lunar:
Invalid
Status in systemd source package in Mantic:
Invalid
Bug description:
udev update has broken ubuntu's ability to import photos in digikam, gphoto2
can no longer see usb camera, entangle can no longer see camera
after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9,
249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9,
249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10),
systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64
(249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9,
249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10)
ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the
camera fine, but the upgrade broke the usage, and cant roll back shows it will
break system to roll back please fix ASAP.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: udev 249.11-0ubuntu3.10
ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
Uname: Linux 6.2.0-1009-lowlatency x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Sep 13 18:16:14 2023
InstallationDate: Installed on 2023-08-23 (21 days ago)
InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release
amd64 (20230807)
MachineType: Alienware Alienware 18
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency
root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash
vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2019
dmi.bios.vendor: Alienware
dmi.bios.version: A15
dmi.board.name: 0FT9KT
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A15
dmi.ec.firmware.release: 1.1
dmi.modalias:
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Here is some backtrace of digikam crashing after trying to import photos from camera, Application: digiKam (digikam), signal: Segmentation fault [KCrash Handler] #4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 #5 0x7f50de2a8603 in __GI___strdup (s=0x0) at ./string/strdup.c:41 #6 0x7f50e1c66820 in gp_port_set_info (port=0x7f4fc0001c00, info=info@entry=0x7f4fd37ec860) at gphoto2-port.c:146 #7 0x7f50e0f8323d in gp_camera_set_port_info (camera=0x7f4fc0004760, info=0x7f4fd37ec860) at gphoto2-camera.c:421 #8 0x7f50e196ae23 in () at /usr/lib/digikam/libdigikamgui.so.8.1.0 #9 0x7f50e195f921 in Digikam::CameraController::executeCommand(Digikam::CameraCommand*) () at /usr/lib/digikam/libdigikamgui.so.8.1.0 #10 0x7f50e1963164 in Digikam::CameraController::run() () at /usr/lib/digikam/libdigikamgui.so.8.1.0 #11 0x7f50deaccca1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f50de294b43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #13 0x7f50de326a00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 29 (Thread 0x7f4fd27fc640 (LWP 282576) "ThreadPoolSingl"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f4fd27ea988) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f4fd27ea988, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f50de293ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f4fd27ea938, cond=0x7f4fd27ea960) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x7f4fd27ea960, mutex=0x7f4fd27ea938) at ./nptl/pthread_cond_wait.c:627 #5 0x7f50d356a67b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f4fd27ea860 in () #7 0x7f4fd27ea8c0 in () #8 0x7f50d7f17d70 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x55b28184abe0 in () #10 0x in () Thread 28 (Thread 0x7f4fd17fa640 (LWP 282575) "MemoryInfra"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f4fd17e8878) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f4fd17e8878, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f50de293ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f4fd17e8828, cond=0x7f4fd17e8850) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x7f4fd17e8850, mutex=0x7f4fd17e8828) at ./nptl/pthread_cond_wait.c:627 #5 0x7f50d356a67b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x in () Thread 27 (Thread 0x7f4ff17fa640 (LWP 282551) "ThreadPoolSingl"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x7f4ff17e8988) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f4ff17e8988, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f50de293ac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f4ff17e8938, cond=0x7f4ff17e8960) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x7f4ff17e8960, mutex=0x7f4ff17e8938) at ./nptl/pthread_cond_wait.c:627 #5 0x7f50d356a67b in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x in () Thread 26 (Thread 0x7f4ff1ffb640 (LWP 282550) "CacheThread_Blo"): #1 __GI___lll_lock_wait_private (futex=0x7f50de41ba60 <_IO_stdfile_2_lock>) at ./nptl/lowlevellock.c:34 #2 0x7f50de277845 in buffered_vfprintf (s=0x7f50de41a6a0 <_IO_2_1_stderr_>, format=format@entry=0x7f50c74e8c85 "[%s] %s\n", args=args@entry=0x7f4ff1fe9200, mode_flags=mode_flags@entry=2) at ./stdio-common/vfprintf-internal.c:2265 #3 0x7f50de2766de in __vfprintf_internal (s=, format=0x7f50c74e8c85 "[%s] %s\n", ap=ap@entry=0x7f4ff1fe9200, mode_flags=2) at ./stdio-common/vfprintf-internal.c:1236 #4 0x7f50de334ec3 in ___fprintf_chk (fp=, flag=, format=) at ./debug/fprintf_chk.c:33 #5 0x7f50c74cd37e in event_logv_ () at /lib/x86_64-linux-gnu/libevent-2.1.so.7 #6 0x7f50c74cd549 in event_warn () at /lib/x86_64-linux-gnu/libevent-2.1.so.7 #7 0x7f50c74d223c in () at /lib/x86_64-linux-gnu/libevent-2.1.so.7 #8 0x7f50c74c95d1 in event_base_loop () at /lib/x86_64-linux-gnu/libevent-2.1.so.7 #9 0x7f50d357c624 in () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x00010008 in () #11 0x7f4ff1fe9908 in () #12 0x7f4ff1fe99c0 in () #13 0x01c78437 in () #14 0x001d in () #15 0x000d02f7 in () #16
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
YES this bug persists after (a) sudo systemctl daemon-reexec, and/or (b) reboot -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Rebooting does nothing, same issue. systemctl daemon-reexec does nothing, same issue no one can talk to my camera, I tried a different camera same issue, lsusb cameras show up just fine so usb's are working, but something happens with that update that caused a roadblock between usb and other software packages. -- 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/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2003331] Re: Can't log in to lunar x11 session
Dropping the rls-ll-incoming tag, which is an incoming queue for Canonical teams to assess prioritization. Since the only open task is against a universe package, it does not apply here. ** Tags removed: rls-ll-incoming -- 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/2003331 Title: Can't log in to lunar x11 session Status in ubuntu-meta package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: New Bug description: On a freshly installed and updated lunar in VirtualBox it doesn't let me log in to Ubuntu on Xorg. I'm just bumped back to the login screen. journalctl extract attached. On my regular (updated) lunar install, logging in to Ubuntu on Xorg works fine. But that's anything but a fresh install. Missing dependency? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003331/+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 2034986] Re: some text became unreadable during a distribution upgrade
** Also affects: ubuntu-meta (Ubuntu Mantic) Importance: Undecided Status: Confirmed ** Also affects: ubuntu-release-upgrader (Ubuntu Mantic) Importance: Critical Status: Confirmed -- 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/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-meta source package in Mantic: Confirmed Status in ubuntu-release-upgrader source package in Mantic: Confirmed Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2035061] Re: uptime -p reports incorrect output after 52 weeks
History is a little bit tricky, patch hhttps://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749 (applied in current debdiff) was merged to the master branch but probably was lost while repository was moving to a "newlib". Last released version https://gitlab.com/procps-ng/procps/-/tags/v3.3.17 did not have this patch applied. Next release version https://gitlab.com/procps-ng/procps/-/tags/v4.0.0 was based on refactored code. With newlib as master this commit has been applied with some modifications in https://gitlab.com/procps-ng/procps/-/commit/0496b39876d569fe1cecb76ad5ef212cd14c0374 Looking at that function there is one more change applied to it https://gitlab.com/procps-ng/procps/-/commit/f08082093192b7d93f28517ffc5298172d182a1e which fixes and issue caused by previous modifications. Differences in both patches are fairly small and affects upminutes/uphours calculation. However after closer look (and writing some tests to check corner cases) there is one additional bug with updays and uphours calculation in proposed patch. If there is exactly 60*60*24 (24h) input, updays will be equal to 0 and uphours will be 24%24 -> 0 which is a regression. Having said that I would not recommend going forward with current proposed patch, another option is to backport https://gitlab.com/procps-ng/procps/-/commit/0496b39876d569fe1cecb76ad5ef212cd14c0374. However because base code has been modified this patch will not apply on 3.3.16/17 and needs some tweaks. I already started working on that and output looks promising. There is still 1 issue with exactly 60s of uptime but it comes from the upstream (I have already created an issue in upstream gitlab repo). Attaching testing results "uptime_test_results". I'll work on providing new debdiffs and keep improving Bug Description. ** Attachment added: "uptime_test_results" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2035061/+attachment/5700926/+files/uptime_test_results -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/2035061 Title: uptime -p reports incorrect output after 52 weeks Status in procps package in Ubuntu: New Status in procps source package in Focal: New Status in procps source package in Jammy: New Bug description: [IMPACT] uptime will provide incorrect data after 52 weeks. This is at least confusing for users utilizing this tool. Issue is already fixed in upstream https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749. Latest procps releases already include this patch (procps 4.0.3 lunar/mantic) The fix is needed for following set of packages: procps | 2:3.3.17-6ubuntu2 | jammy procps | 2:3.3.16-1ubuntu2 | focal [TEST CASE] UPTIME="31528920 31528800"; mkfifo uptime_fifo; while true; do cat <<<$UPTIME > uptime_fifo; done & sudo mount -obind uptime_fifo /proc/uptime uptime -p Running above commands will result in incorrect uptime output. [REGRESSION POTENTIAL] The patch is already available in upstream, lunar/mantic releases already include is as well. Old behavior will inaccurately print uptime -p for 24h after 31449600 seconds (0 years, 0 weeks). With new patch during that time uptime -p will print "52 weeks". [OTHER] Bug upstream: https://gitlab.com/procps-ng/procps/-/issues/217 Following patch is needed for older releases: https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2035061/+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 2035585] Re: Versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329
** Patch added: "gst-plugins-bad1.0_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2035585/+attachment/5700925/+files/gst-plugins-bad1.0_focal.debdiff ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-37329 ** Tags added: community-security focal jammy lunar patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2035585 Title: Versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329 Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Bug description: The versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2035585/+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 2031942] Re: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set
This bug was fixed in the package openssh - 1:8.9p1-3ubuntu0.4 --- openssh (1:8.9p1-3ubuntu0.4) jammy; urgency=medium * d/p/fix-authorized-principals-command.patch: Fix the situation where sshd ignores AuthorizedPrincipalsCommand if AuthorizedKeysCommand is also set by checking if the value pointed to by the pointer 'charptr' is NULL. (LP: #2031942) -- Michal Maloszewski Thu, 24 Aug 2023 15:40:24 +0200 ** Changed in: openssh (Ubuntu Jammy) 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/2031942 Title: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: Fix Released Status in openssh source package in Lunar: Fix Released Status in openssh source package in Mantic: Fix Released Bug description: [Impact] User of openssh reported an issue that affects Lunar and Jammy. If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand configuration in sshd_config that comes after it is ignored. In this scenario, where AuthorizedPrincipalsCommand is needed and set, users relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals' with permissions 755 as follows: #!/bin/sh if [ "$1" = "otheruser" ]; then echo certuser fi Exit the file. Ensure you are in the /root/reproducer/ directory: # adduser --disabled-password otheruser (Enter multiple times, leave all fields blank) Then do the same for another user: # adduser --disabled-password keyonlyuser Create a script '/root/reproducer/authorized_keys' with permissions 755 as follows: #!/bin/sh if [ "$1" = "keyonlyuser" ]; then echo fi Go to the /etc/ssh/sshd_config file. Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u AuthorizedKeysCommandUser root AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u AuthorizedPrincipalsCommandUser root TrustedUserCAKeys /root/reproducer/certuser/ca.pub Exit from the file and restart the ssh service: # systemctl restart ssh Use these commands to manifest the bug: # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key # ssh otheruser@localhost -i /root/reproducer/certuser/key -o CertificateFile=/root/reproducer/certuser/key-cert.pub Expected results: both ssh commands should succeed. Actual results: the second ssh fails because the AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set. [Where problems could occur] * The patch itself modifies only the servconf.c, so regressions should be limited to the server configuration. * Since the fix touches pointers, there might be regression related to memory handling and fetching data. -original report-- Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code: if (*activep && options->authorized_keys_command == NULL) *charptr = xstrdup(str + len); However, this is executed for both authorized_keys_command and authorized_principals_command. As a result, if authorized_keys_command is set (for instance, if using ec2-instance-connect), any AuthorizedPrincipalsCommand configuration in sshd_config is ignored. This is fixed in 9.4p1 with the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2031942/+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 2031942] 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/2031942 Title: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: Fix Released Status in openssh source package in Lunar: Fix Released Status in openssh source package in Mantic: Fix Released Bug description: [Impact] User of openssh reported an issue that affects Lunar and Jammy. If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand configuration in sshd_config that comes after it is ignored. In this scenario, where AuthorizedPrincipalsCommand is needed and set, users relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals' with permissions 755 as follows: #!/bin/sh if [ "$1" = "otheruser" ]; then echo certuser fi Exit the file. Ensure you are in the /root/reproducer/ directory: # adduser --disabled-password otheruser (Enter multiple times, leave all fields blank) Then do the same for another user: # adduser --disabled-password keyonlyuser Create a script '/root/reproducer/authorized_keys' with permissions 755 as follows: #!/bin/sh if [ "$1" = "keyonlyuser" ]; then echo fi Go to the /etc/ssh/sshd_config file. Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u AuthorizedKeysCommandUser root AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u AuthorizedPrincipalsCommandUser root TrustedUserCAKeys /root/reproducer/certuser/ca.pub Exit from the file and restart the ssh service: # systemctl restart ssh Use these commands to manifest the bug: # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key # ssh otheruser@localhost -i /root/reproducer/certuser/key -o CertificateFile=/root/reproducer/certuser/key-cert.pub Expected results: both ssh commands should succeed. Actual results: the second ssh fails because the AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set. [Where problems could occur] * The patch itself modifies only the servconf.c, so regressions should be limited to the server configuration. * Since the fix touches pointers, there might be regression related to memory handling and fetching data. -original report-- Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code: if (*activep && options->authorized_keys_command == NULL) *charptr = xstrdup(str + len); However, this is executed for both authorized_keys_command and authorized_principals_command. As a result, if authorized_keys_command is set (for instance, if using ec2-instance-connect), any AuthorizedPrincipalsCommand configuration in sshd_config is ignored. This is fixed in 9.4p1 with the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2031942/+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 2031942] Re: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu8.5 --- openssh (1:9.0p1-1ubuntu8.5) lunar; urgency=medium * d/p/fix-authorized-principals-command.patch: Fix the situation where sshd ignores AuthorizedPrincipalsCommand if AuthorizedKeysCommand is also set by checking if the value pointed to by the pointer 'charptr' is NULL. (LP: #2031942) -- Michal Maloszewski Thu, 24 Aug 2023 15:52:47 +0200 ** 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/2031942 Title: AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Jammy: Fix Released Status in openssh source package in Lunar: Fix Released Status in openssh source package in Mantic: Fix Released Bug description: [Impact] User of openssh reported an issue that affects Lunar and Jammy. If AuthorizedKeysCommand is set, an AuthorizedPrincipalsCommand configuration in sshd_config that comes after it is ignored. In this scenario, where AuthorizedPrincipalsCommand is needed and set, users relying on ssh certificates for authentication will be denied access. [Test Plan] Launch container: $ lxc launch ubuntu:jammy Shell into that container: $ lxc shell Create the main directory for our task (e.g. “reproducer”) # mkdir reproducer Go to that directory: # cd reproducer Create 2 more dirs that reflect users: # mkdir certuser keyonlyuser Go to the keyonlyuser: # cd keyonlyuser Do: # ssh-keygen -t ed25519 -f key Go to the certuser: # cd /root/reproducer/certuser/ Do: # ssh-keygen -t rsa -f ca # ssh-keygen -t ed25519 -f key # ssh-keygen -s ca -I key_id -n certuser key.pub Create a script '/root/reproducer/authorized_principals' with permissions 755 as follows: #!/bin/sh if [ "$1" = "otheruser" ]; then echo certuser fi Exit the file. Ensure you are in the /root/reproducer/ directory: # adduser --disabled-password otheruser (Enter multiple times, leave all fields blank) Then do the same for another user: # adduser --disabled-password keyonlyuser Create a script '/root/reproducer/authorized_keys' with permissions 755 as follows: #!/bin/sh if [ "$1" = "keyonlyuser" ]; then echo fi Go to the /etc/ssh/sshd_config file. Add at the top: AuthorizedKeysCommand /root/reproducer/authorized_keys %u AuthorizedKeysCommandUser root AuthorizedPrincipalsCommand /root/reproducer/authorized_principals %u AuthorizedPrincipalsCommandUser root TrustedUserCAKeys /root/reproducer/certuser/ca.pub Exit from the file and restart the ssh service: # systemctl restart ssh Use these commands to manifest the bug: # ssh keyonlyuser@localhost -i /root/reproducer/keyonlyuser/key # ssh otheruser@localhost -i /root/reproducer/certuser/key -o CertificateFile=/root/reproducer/certuser/key-cert.pub Expected results: both ssh commands should succeed. Actual results: the second ssh fails because the AuthorizedPrincipalsCommand is ignored if AuthorizedKeysCommand is set. [Where problems could occur] * The patch itself modifies only the servconf.c, so regressions should be limited to the server configuration. * Since the fix touches pointers, there might be regression related to memory handling and fetching data. -original report-- Versions of OpenSSH from 8.7p1 to 9.3p1 contain the following code: if (*activep && options->authorized_keys_command == NULL) *charptr = xstrdup(str + len); However, this is executed for both authorized_keys_command and authorized_principals_command. As a result, if authorized_keys_command is set (for instance, if using ec2-instance-connect), any AuthorizedPrincipalsCommand configuration in sshd_config is ignored. This is fixed in 9.4p1 with the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2031942/+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 2035778] Re: upstream autopkgtests fail to build test images
The Europe/Kiev symlink is now in tzdata-legacy, so we can just depend on that for these autopkgtests. ** Changed in: systemd (Ubuntu) Status: New => Triaged -- 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/2035778 Title: upstream autopkgtests fail to build test images Status in systemd package in Ubuntu: Triaged Bug description: Example test log: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/s/systemd/20230912_054033_0b699@/log.gz Basically every upstream test fails with odd errors. Early in the tests, a common default.img is supposed to be built, but this fails: 2614s I: Install time zones 2614s D: Installing /usr/share/zoneinfo/Asia/Seoul 2614s D: Installing /usr/share/zoneinfo/Asia/Vladivostok 2614s D: Installing /usr/share/zoneinfo/Australia/Sydney 2614s D: Installing /usr/share/zoneinfo/Europe/Berlin 2614s D: Installing /usr/share/zoneinfo/Europe/Dublin 2614s make: *** [Makefile:4: setup] Error 1 But, the tests continue anyways, without a complete test image, hence the odd errors. Looking at the test script, I found that it it is failing trying to install /usr/share/zoneinfo/Europe/Kiev, which is now called /usr/share/zoneinfo/Europe/Kyiv. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035778/+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 2035220] Re: cve-2023-4863
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox-esr (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in firefox-esr package in Ubuntu:
Confirmed
Status in libwebp package in Ubuntu:
Confirmed
Status in thunderbird package in Ubuntu:
Fix Released
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
Confirmed
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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 2035220] Re: cve-2023-4863
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libwebp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in firefox-esr package in Ubuntu:
Confirmed
Status in libwebp package in Ubuntu:
Confirmed
Status in thunderbird package in Ubuntu:
Fix Released
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
Confirmed
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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 2035585] Re: Versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329
** Changed in: gst-plugins-bad1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2035585 Title: Versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329 Status in gst-plugins-bad1.0 package in Ubuntu: Confirmed Bug description: The versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2035585/+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 2035221] Re: driver problem
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/2035221 Title: driver problem Status in xorg package in Ubuntu: New Bug description: my PC brightness cannot be adjust ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 20:41:05 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:308c] InstallationDate: Installed on 2023-08-20 (23 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: LENOVO 36644M9 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=d9fe23a3-2394-47aa-aa88-66e71e67d711 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2013 dmi.bios.release: 0.57 dmi.bios.vendor: LENOVO dmi.bios.version: F1KT57AUS dmi.board.vendor: LENOVO dmi.board.version: NOK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrF1KT57AUS:bd11/07/2013:br0.57:svnLENOVO:pn36644M9:pvrThinkCentreM72e:rvnLENOVO:rn:rvrNOK:cvnLENOVO:ct3:cvr:skuLENOVO_MT_3664: dmi.product.name: 36644M9 dmi.product.sku: LENOVO_MT_3664 dmi.product.version: ThinkCentre M72e dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.0.20230414.1+2061~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2035221/+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 2035778] [NEW] upstream autopkgtests fail to build test images
Public bug reported: Example test log: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/s/systemd/20230912_054033_0b699@/log.gz Basically every upstream test fails with odd errors. Early in the tests, a common default.img is supposed to be built, but this fails: 2614s I: Install time zones 2614s D: Installing /usr/share/zoneinfo/Asia/Seoul 2614s D: Installing /usr/share/zoneinfo/Asia/Vladivostok 2614s D: Installing /usr/share/zoneinfo/Australia/Sydney 2614s D: Installing /usr/share/zoneinfo/Europe/Berlin 2614s D: Installing /usr/share/zoneinfo/Europe/Dublin 2614s make: *** [Makefile:4: setup] Error 1 But, the tests continue anyways, without a complete test image, hence the odd errors. Looking at the test script, I found that it it is failing trying to install /usr/share/zoneinfo/Europe/Kiev, which is now called /usr/share/zoneinfo/Europe/Kyiv. ** Affects: systemd (Ubuntu) Importance: High Assignee: Nick Rosbrook (enr0n) Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Nick Rosbrook (enr0n) -- 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/2035778 Title: upstream autopkgtests fail to build test images Status in systemd package in Ubuntu: New Bug description: Example test log: https://autopkgtest.ubuntu.com/results/autopkgtest- mantic/mantic/amd64/s/systemd/20230912_054033_0b699@/log.gz Basically every upstream test fails with odd errors. Early in the tests, a common default.img is supposed to be built, but this fails: 2614s I: Install time zones 2614s D: Installing /usr/share/zoneinfo/Asia/Seoul 2614s D: Installing /usr/share/zoneinfo/Asia/Vladivostok 2614s D: Installing /usr/share/zoneinfo/Australia/Sydney 2614s D: Installing /usr/share/zoneinfo/Europe/Berlin 2614s D: Installing /usr/share/zoneinfo/Europe/Dublin 2614s make: *** [Makefile:4: setup] Error 1 But, the tests continue anyways, without a complete test image, hence the odd errors. Looking at the test script, I found that it it is failing trying to install /usr/share/zoneinfo/Europe/Kiev, which is now called /usr/share/zoneinfo/Europe/Kyiv. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035778/+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 1615641] Re: initramfs waits for 5 seconds when executing /scripts/local-premount/resume
Okay. I am closing this bug report. ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Invalid -- 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/1615641 Title: initramfs waits for 5 seconds when executing /scripts/local- premount/resume Status in initramfs-tools package in Ubuntu: Invalid Bug description: I've noticed that boots on Ubuntu Yakkety have slowed down recently. I added some debug into my kernel to see where delays are occurring and I can observe 5 seconds being consumed in /scripts/local- premount/resume : Aug 22 14:34:36 lenovo kernel: [6.823263] _do_fork: 1 (init) Aug 22 14:34:36 lenovo kernel: [6.82] do_exec: 824 (init) /scripts/local-premount/ntfs_3g Aug 22 14:34:36 lenovo kernel: [6.823766] _do_fork: 1 (init) Aug 22 14:34:36 lenovo kernel: [6.823845] do_exec: 825 (init) /scripts/local-premount/resume Aug 22 14:34:36 lenovo kernel: [6.824214] _do_fork: 825 (resume) Aug 22 14:34:36 lenovo kernel: [6.824322] do_exec: 826 (resume) /sbin/wait-for-root Aug 22 14:34:36 lenovo kernel: [ 11.825642] _do_fork: 1 (init) Aug 22 14:34:36 lenovo kernel: [ 11.825800] do_exec: 827 (init) /sbin/wait-for-root Aug 22 14:34:36 lenovo kernel: [ 11.826691] _do_fork: 1 (init) It seems that /scripts/local-premount/resume is being called and wait- for-root times out after 5 seconds. The resume script does set a 5 second timeout, so I must be hitting that for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1615641/+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 1615641] Re: initramfs waits for 5 seconds when executing /scripts/local-premount/resume
We may as well close this issue, I don't have that laptop any more, I don't work for Canonical any more and the boot speed regressions seem to have fallen off the CTO's "must do priority radar" otherwise this kind of regression would have had more engineering time devoted to it. -- 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/1615641 Title: initramfs waits for 5 seconds when executing /scripts/local- premount/resume Status in initramfs-tools package in Ubuntu: Incomplete Bug description: I've noticed that boots on Ubuntu Yakkety have slowed down recently. I added some debug into my kernel to see where delays are occurring and I can observe 5 seconds being consumed in /scripts/local- premount/resume : Aug 22 14:34:36 lenovo kernel: [6.823263] _do_fork: 1 (init) Aug 22 14:34:36 lenovo kernel: [6.82] do_exec: 824 (init) /scripts/local-premount/ntfs_3g Aug 22 14:34:36 lenovo kernel: [6.823766] _do_fork: 1 (init) Aug 22 14:34:36 lenovo kernel: [6.823845] do_exec: 825 (init) /scripts/local-premount/resume Aug 22 14:34:36 lenovo kernel: [6.824214] _do_fork: 825 (resume) Aug 22 14:34:36 lenovo kernel: [6.824322] do_exec: 826 (resume) /sbin/wait-for-root Aug 22 14:34:36 lenovo kernel: [ 11.825642] _do_fork: 1 (init) Aug 22 14:34:36 lenovo kernel: [ 11.825800] do_exec: 827 (init) /sbin/wait-for-root Aug 22 14:34:36 lenovo kernel: [ 11.826691] _do_fork: 1 (init) It seems that /scripts/local-premount/resume is being called and wait- for-root times out after 5 seconds. The resume script does set a 5 second timeout, so I must be hitting that for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1615641/+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 1646017] Re: package linux-image-4.4.0-51-generic 4.4.0-51.72 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: cp: cannot stat '/usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf': No such file or directory This file is part of the ttf-dejavu-core package (on Ubuntu 16.04). Installing that packages should solve the failure: sudo apt install ttf-dejavu-core sudo update-initramfs -u ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- 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/1646017 Title: package linux-image-4.4.0-51-generic 4.4.0-51.72 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Nothing at this time ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-51-generic 4.4.0-51.72 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: lyn2443 F...m pulseaudio /dev/snd/pcmC0D0p: lyn2443 F...m pulseaudio /dev/snd/controlC0: lyn2443 F pulseaudio /dev/snd/seq:lyn3223 F chrome Date: Wed Nov 30 07:43:09 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=074926a9-381d-4427-b731-ebee649db332 InstallationDate: Installed on 2015-09-08 (448 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: NOVATECH LTD BB-21204A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=35f26562-11cc-4de2-baa9-792e92b7a396 ro quiet splash crashkernel=384M-:128M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-51-generic 4.4.0-51.72 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-S2PV dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFH:bd02/25/2013:svnNOVATECHLTD:pnBB-21204A:pvr1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2PV:rvrx.x:cvnNOVATECHLTD:ct3:cvr: dmi.product.name: BB-21204A dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1646017/+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 1629707] Re: package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:
mv: impossible d'évaluer '/boot/initrd.img-4.4.0-38-generic.new': Aucun
fichier ou dossier de ce type
deepl trantlates it to:
mv: unable to evaluate '/boot/initrd.img-4.4.0-38-generic.new': No such
files or folders
I don't know what causes it, but running "sudo update-initramfs -u" will
solve it. I am making this bug as invalid since it is an old bug. Please
re-open or open a new bug in case you experience with a recent Ubuntu
version.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Invalid
--
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/1629707
Title:
package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 1
Status in initramfs-tools package in Ubuntu:
Invalid
Bug description:
Bug notification automatic after login
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.4.0-38-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: SB [HDA ATI SB], device 0: 92HD81B1X5 Analog [92HD81B1X5 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: 92HD81B1X5 Analog [92HD81B1X5 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: guy1709 F pulseaudio
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xf050 irq 16'
Mixer name : 'IDT 92HD81B1X5'
Components : 'HDA:111d7605,103c1443,00100402'
Controls : 23
Simple ctrls : 11
Date: Sun Oct 2 22:32:39 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 1
HibernationDevice: RESUME=UUID=a101ccab-5f9a-4f81-bee3-73cda7f5ad0a
InstallationDate: Installed on 2016-10-02 (0 days ago)
InstallationMedia: budgie-remix 16.04.1 "Budgie-remix" - amd64 (20160723)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcFB:
0 radeondrmfb
1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic
root=UUID=85b456d6-d514-4880-8f66-8fc03bf4ea4e 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.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-38-generic 4.4.0-38.57 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.29
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1443
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 67.33
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.29:bd02/25/2013:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn1443:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: 058B11242B1020100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1629707/+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 1615641] Re: initramfs waits for 5 seconds when executing /scripts/local-premount/resume
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1615641 and any other logs that are relevant for this particular issue. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Incomplete -- 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/1615641 Title: initramfs waits for 5 seconds when executing /scripts/local- premount/resume Status in initramfs-tools package in Ubuntu: Incomplete Bug description: I've noticed that boots on Ubuntu Yakkety have slowed down recently. I added some debug into my kernel to see where delays are occurring and I can observe 5 seconds being consumed in /scripts/local- premount/resume : Aug 22 14:34:36 lenovo kernel: [6.823263] _do_fork: 1 (init) Aug 22 14:34:36 lenovo kernel: [6.82] do_exec: 824 (init) /scripts/local-premount/ntfs_3g Aug 22 14:34:36 lenovo kernel: [6.823766] _do_fork: 1 (init) Aug 22 14:34:36 lenovo kernel: [6.823845] do_exec: 825 (init) /scripts/local-premount/resume Aug 22 14:34:36 lenovo kernel: [6.824214] _do_fork: 825 (resume) Aug 22 14:34:36 lenovo kernel: [6.824322] do_exec: 826 (resume) /sbin/wait-for-root Aug 22 14:34:36 lenovo kernel: [ 11.825642] _do_fork: 1 (init) Aug 22 14:34:36 lenovo kernel: [ 11.825800] do_exec: 827 (init) /sbin/wait-for-root Aug 22 14:34:36 lenovo kernel: [ 11.826691] _do_fork: 1 (init) It seems that /scripts/local-premount/resume is being called and wait- for-root times out after 5 seconds. The resume script does set a 5 second timeout, so I must be hitting that for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1615641/+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 2035644] [NEW] apt status not updated ubuntu 20 LTS
Public bug reported: Hi, is this a cache bug? The packages are installed, but "apt list --upgradable" say's no, the are not installed. root@minion:~# apt list --upgradable Listing... Done uls-client/luxux-standard-ubuntu20-x-amd64-dp-tserver 3.15-7ubuntu20 amd64 [upgradable from: 3.15-7ubuntu20] venv-salt-minion/ubuntu20-x-amd64-res-suma-dp-tserver 3006.0-2.35.1 amd64 [upgradable from: 3006.0-2.35.1] root@minion:~# apt install uls-client Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-5.4.0-153 linux-headers-5.4.0-153-generic linux-image-5.4.0-153-generic linux-modules-5.4.0-153-generic linux-modules-extra-5.4.0-153-generic Use 'apt autoremove' to remove them. Recommended packages: libncursesw5 The following packages will be upgraded: uls-client 1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/194 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 177475 files and directories currently installed.) Preparing to unpack .../uls-client_3.15-7ubuntu20_amd64.deb ... redirecting to systemd Unpacking uls-client (3.15-7ubuntu20) over (3.15-7ubuntu20) ... Setting up uls-client (3.15-7ubuntu20) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.22) ... root@minion:~# apt list --upgradable Listing... Done uls-client/luxux-standard-ubuntu20-x-amd64-dp-tserver 3.15-7ubuntu20 amd64 [upgradable from: 3.15-7ubuntu20] venv-salt-minion/ubuntu20-x-amd64-res-suma-dp-tserver 3006.0-2.35.1 amd64 [upgradable from: 3006.0-2.35.1] root@minion:~# apt update Hit:12 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-dp-tserver/ Release Hit:13 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-main-dp-tserver/ Release Hit:14 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-res-suma-dp-tserver/ Release Hit:15 https://SuMa:443/rhn/manager/download luxux-puppet-ubuntu20-x-amd64-dp-tserver/ Release Hit:16 https://SuMa:443/rhn/manager/download tvm-standard-ubuntu20-x-amd64-dp-tserver/ Release Hit:17 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-main-updates-dp-tserver/ Release Hit:18 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-main-security-dp-tserver/ Release Hit:19 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-main-universe-dp-tserver/ Release Hit:20 https://SuMa:443/rhn/manager/download luxux-standard-ubuntu20-x-amd64-dp-tserver/ Release Hit:21 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-main-updates-universe-dp-tserver/ Release Hit:22 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-main-security-universe-dp-tserver/ Release Reading package lists... Done Building dependency tree Reading state information... Done 2 packages can be upgraded. Run 'apt list --upgradable' to see them. root@minion:~# apt list --upgradable Listing... Done uls-client/luxux-standard-ubuntu20-x-amd64-dp-tserver 3.15-7ubuntu20 amd64 [upgradable from: 3.15-7ubuntu20] venv-salt-minion/ubuntu20-x-amd64-res-suma-dp-tserver 3006.0-2.35.1 amd64 [upgradable from: 3006.0-2.35.1] root@minion:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-headers-5.4.0-153 linux-headers-5.4.0-153-generic linux-image-5.4.0-153-generic linux-modules-5.4.0-153-generic linux-modules-extra-5.4.0-153-generic Use 'apt autoremove' to remove them. The following packages will be upgraded: uls-client venv-salt-minion 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 22.7 MB/22.9 MB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 https://SuMa:443/rhn/manager/download ubuntu20-x-amd64-res-suma-dp-tserver/ venv-salt-minion 3006.0-2.35.1 [22.7 MB] Fetched 22.7 MB in 0s (76.8 MB/s) (Reading database ... 177475 files and directories currently installed.) Preparing to unpack .../uls-client_3.15-7ubuntu20_amd64.deb ... redirecting to systemd Unpacking uls-client (3.15-7ubuntu20) over (3.15-7ubuntu20) ... Preparing to unpack .../venv-salt-minion_3006.0-2.35.1_amd64.deb ... Unpacking venv-salt-minion (3006.0-2.35.1) over (3006.0-2.35.1) ... Setting up venv-salt-minion (3006.0-2.35.1) ... Setting up uls-client (3.15-7ubuntu20) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.22) ... root@minion:~# apt list --upgradable Listing... Done uls-client/luxux-standard-ubuntu20-x-amd64-dp-tserver 3.15-7ubuntu20 amd64 [upgradable from: 3.15-7ubuntu20] venv-salt-minion/ubuntu20-x-amd64-res-suma-dp-tserver 3006.0-2.35.1 amd64 [upgradable from: 3006.0-2.35.1] ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received
[Touch-packages] [Bug 1597445] Re: package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: update-initramfs: Generating /boot/initrd.img-4.4.0-28-generic /etc/initramfs-tools/hooks/reiserfsprogs: line 3: ./usr/share/initramfs-tools/hook-functions: Permission denied /etc/initramfs-tools/hooks/reiserfsprogs: line 6: copy_exec: command not found /etc/initramfs-tools/hooks/reiserfsprogs: line 3: ./usr/share/initramfs-tools/hook-functions: Permission denied /etc/initramfs-tools/hooks/reiserfsprogs: line 6: copy_exec: command not found E: /etc/initramfs-tools/hooks/reiserfsprogs failed with return 127. Line 3 of /etc/initramfs-tools/hooks/reiserfsprogs is lacking a space between the dot and the path. A freshly installed reiserfsprogs 1:3.6.24-3.1 on Ubuntu 16.04 LTS "Xenial Xerus" contain that space: ``` #! /bin/bash . /usr/share/initramfs-tools/hook-functions if command -v reiserfsck >/dev/null 2>&1; then copy_exec /sbin/reiserfsck sbin/reiserfsck fi ``` Please add this space in case you run into this problem. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Invalid -- 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/1597445 Title: package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 Status in initramfs-tools package in Ubuntu: Invalid Bug description: I was updating the kernal headers using symantic and it crashed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-28-generic 4.4.0-28.47 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vergon 7022 F pulseaudio Date: Wed Jun 29 12:10:45 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 HibernationDevice: RESUME=UUID=c10d442c-ed19-4e49-a6a1-50932e56369d InstallationDate: Installed on 2016-05-29 (30 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/lubuntu--vg-root ro priority=low edd=on nodmraid 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. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3 SourcePackage: initramfs-tools Title: package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2008 dmi.bios.vendor: Phoenix dmi.bios.version: F.2A dmi.board.name: 30CD dmi.board.vendor: Wistron dmi.board.version: 80.52 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrF.2A:bd03/25/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2A:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv2700 Notebook PC dmi.product.version: F.2A dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1597445/+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 2012992] Re: kernel-5.19.0-38 battery charge fails
Thank you for taking the time to report this bug and helping to make Ubuntu better. I re-assigned your bug report against the linux package. ** Package changed: initramfs-tools (Ubuntu) => linux (Ubuntu) -- 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/2012992 Title: kernel-5.19.0-38 battery charge fails Status in linux package in Ubuntu: Incomplete Bug description: I just installed linux-image-5.19.0-38 on my HP ProBook 640 G2 with Ubuntu-22.0.4LTS and my battery no longer charges. Battery reports 77% charge, but "pending charge." Leaving it connected to charger give no change in charge status. Booting to Windows-10 shows charge at 77%, status charging, and charge report increasing as expected. Reverting to kernel-5.15.0-69 shows 76% charge, status "charging." john@stolat:~$ upower -i /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Hewlett-Packard model:Primary serial: 36600 2017/12/20 power supply: yes updated: Mon 27 Mar 2023 08:18:01 PM CDT (114 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging warning-level: none energy: 31.1106 Wh energy-empty:0 Wh energy-full: 40.5954 Wh energy-full-design: 48.0168 Wh energy-rate: 0 W voltage: 12.15 V charge-cycles: 57 percentage: 76% capacity:84.5442% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012992/+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 2015095] Re: Doing suggested updates package linux-image-5.15.0-69-generic 5.15.0-69.76~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exite
Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: pigz: abort: write error on (No space left on device) E: mkinitramfs failure cpio 141 pigz 28 So generating the initramfs fails because your boot partition is full. Please cleanup your boot partition. Feel free to continue to report any other bugs you may find. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Summary changed: - Doing suggested updates package linux-image-5.15.0-69-generic 5.15.0-69.76~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 + Doing suggested updates package linux-image-5.15.0-69-generic 5.15.0-69.76~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -> boot partition full -- 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/2015095 Title: Doing suggested updates package linux-image-5.15.0-69-generic 5.15.0-69.76~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -> boot partition full Status in initramfs-tools package in Ubuntu: Invalid Bug description: The system suggested I do updates. This is what happened ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-69-generic 5.15.0-69.76~20.04.1 ProcVersionSignature: Ubuntu 5.14.0-1056.63-oem 5.14.21 Uname: Linux 5.14.0-1056-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 3 16:43:23 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-next-release+X149.1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2023-01-02 (90 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-69-generic 5.15.0-69.76~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2015095/+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 2017182] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files -- 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/2017182 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Upgrading from 18.04 to 20.04. No space left on /boot. Solved by changing compression from lz4 to xz and regenerating before reboot. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-147.164-generic 5.4.231 Uname: Linux 5.4.0-147-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 21 00:16:53 2023 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-03-02 (2605 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017182/+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 2008137] Re: package linux-image-5.4.0-139-generic 5.4.0-139.156 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: cp: error writing '/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/vega10_uvd.bin': No space left on device cp: error writing '/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/vegam_uvd.bin': No space left on device cp: error writing '/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/polaris12_uvd.bin': No space left on device cp: error writing '/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/polaris11_uvd.bin': No space left on device cp: error writing '/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/polaris10_uvd.bin': No space left on device cp: error writing '/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/stoney_uvd.bin': No space left on device cp: error writing '/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/fiji_uvd.bin': No space left on device cp: error writing '/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/carrizo_uvd.bin': No space left on device cp: error writing '/var/tmp/mkinitramfs_m6ETye//usr/lib/firmware/amdgpu/tonga_uvd.bin': No space left on device So generating the initramfs fails because your root partition is full. Please cleanup your root partition. Feel free to continue to report any other bugs you may find. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid ** Summary changed: - package linux-image-5.4.0-139-generic 5.4.0-139.156 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 + package linux-image-5.4.0-139-generic 5.4.0-139.156 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -> root partition full -- 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/2008137 Title: package linux-image-5.4.0-139-generic 5.4.0-139.156 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -> root partition full Status in initramfs-tools package in Ubuntu: Invalid Bug description: I ran out of disk space -- ideally the updater should have recognized this problem before it ran out and given me some time to deal w/ it... ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-139-generic 5.4.0-139.156 ProcVersionSignature: Ubuntu 4.15.0-204.215-generic 4.15.18 Uname: Linux 4.15.0-204-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 22 22:34 seq crw-rw 1 root audio 116, 33 Feb 22 22:34 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed Feb 22 22:48:19 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Google Google Compute Engine PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-204-generic root=UUID=567ab888-a3b5-43d4-a92a-f594e8653924 ro console=ttyS0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: initramfs-tools Title: package linux-image-5.4.0-139-generic 5.4.0-139.156 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2023-02-22 (0 days ago) dmi.bios.date: 01/12/2023 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: 2DBA0E4C-F303-6B72-EA06-7713C146E294 dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/12/2023:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2008137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 2018171] Re: package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post-installation script subprocess return
Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: update-initramfs: Generating /boot/initrd.img-5.19.0-35-generic grep: /boot/config-5.19.0-35-generic: No such file or directory W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip grep: /boot/config-5.19.0-35-generic: No such file or directory E: gzip compression (CONFIG_RD_GZIP) not supported by kernel update-initramfs: failed for /boot/initrd.img-5.19.0-35-generic with 1. /boot/config-5.19.0-35-generic is not present any more. Probably the kernel version 5.19.0-35-generic is not fully installed any more. I recommend to remove this kernel completely: sudo apt remove linux-image-5.19.0-35-generic linux- modules-5.19.0-35-generic linux-modules-extra-5.19.0-35-generic ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- 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/2018171 Title: package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post- installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: Upgrading from 22.10 to 23.04 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-kernel-common-525 525.105.17-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sat Apr 29 19:33:35 2023 ErrorMessage: installed nvidia-kernel-common-525 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-22 (158 days ago) InstallationMedia: Ubuntu-Server 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: initramfs-tools Title: package nvidia-kernel-common-525 525.105.17-0ubuntu1 failed to install/upgrade: installed nvidia-kernel-common-525 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2018171/+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 2018704] Re: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: sync: error syncing '/boot/initrd.img-5.19.0-41-generic': Input/output error Input/output error indicates a problem with your storage device. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/2018704 Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: not able to update ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon May 8 09:46:48 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2023-02-05 (91 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2018704/+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 2035385] Re: package initram is not updated
Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: E: /usr/share/initramfs-tools/hooks/fuse failed with return 1. Sadly there is no error message explaining the exit code 1. Can you edit /usr/share/initramfs-tools/hooks/fuse and add "set -x" (without the quotes) to the script and then run update-initramfs to get more log output? sudo nano /usr/share/initramfs-tools/hooks/fuse sudo update-initramfs -u Please attach the output to the bug report then. ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete ** Summary changed: - package initram is not updated + update-initramfs fails: /usr/share/initramfs-tools/hooks/fuse failed with return 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/2035385 Title: update-initramfs fails: /usr/share/initramfs-tools/hooks/fuse failed with return 1. Status in initramfs-tools package in Ubuntu: Incomplete Bug description: The system is not fully updated and gives the following error Setting up initramfs-tools (0.136ubuntu6.7) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.136ubuntu6.7) ... update-initramfs: Generating /boot/initrd.img-5.4.0-162-generic E: /usr/share/initramfs-tools/hooks/fuse failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-162-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-162.179-generic 5.4.246 Uname: Linux 5.4.0-162-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 13 19:39:18 2023 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-09-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2035385/+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 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays
** Changed in: oem-priority Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2025563 Title: System can not shutdown if system has multiple VROC RAID arrays Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Fix Released Bug description: [ Impact ] The system can not shutdown if the system has multiple VROC RAID arrays. Intel has fixed it in systemd v251 [1]. Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9. [1] The commit fixes the issue: commit 3a3b022d2cc112803ea7b9beea98bbcad110368a Author: Mariusz Tkaczyk Date: Tue Mar 29 12:49:54 2022 +0200 shutdown: get only active md arrays. Current md_list_get() implementation filters all block devices, started from "md*". This is ambiguous because list could contain: - partitions created upon md device (mdXpY) - external metadata container- specific type of md array. For partitions there is no issue, because they aren't handle STOP_ARRAY ioctl sent later. It generates misleading errors only. Second case is more problematic because containers are not locked in kernel. They are stopped even if container member array is active. For that reason reboot or shutdown flow could be blocked because metadata manager cannot be restarted after switch root on shutdown. Add filters to remove partitions and containers from md_list. Partitions can be excluded by DEVTYPE. Containers are determined by MD_LEVEL property, we are excluding all with "container" value. Signed-off-by: Mariusz Tkaczyk In the journal, we can see systemd-shutdown looping repeatedly as it tries and fails to detach all md devices: ... [ 513.416293] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:5). [ 513.422953] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or resource busy [ 513.431227] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:4). [ 513.437952] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or resource busy [ 513.449298] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124). [ 513.456278] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or resource busy [ 513.465323] systemd-shutdown[1]: Not all MD devices stopped, 4 left. [ 513.472564] systemd-shutdown[1]: Couldn't finalize remaining MD devices, trying again. [ 513.485302] systemd-shutdown[1]: Failed to open watchdog device /dev/watchdog: No such file or directory [ 513.496195] systemd-shutdown[1]: Stopping MD devices. [ 513.502176] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs [ 513.513382] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus [ 513.521436] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class [ 513.534810] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126). [ 513.545384] systemd-shutdown[1]: Failed to sync MD block device /dev/md126, ignoring: Input/output error [ 513.557265] md: md126 stopped. [ 513.561451] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:5). [ 513.576673] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or resource busy [ 513.589274] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:4). [ 513.597976] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or resource busy [ 513.607263] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124). [ 513.615067] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or resource busy [ 513.625157] systemd-shutdown[1]: Not all MD devices stopped, 4 left. [ 513.632209] systemd-shutdown[1]: Couldn't finalize remaining MD devices, trying again. [ 513.641474] systemd-shutdown[1]: Failed to open watchdog device /dev/watchdog: No such file or directory [ 513.653660] systemd-shutdown[1]: Stopping MD devices. [ 513.661257] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs [ 513.668833] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus [ 513.677347] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class [ 513.687047] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126). [ 513.697206] systemd-shutdown[1]: Failed to sync MD block device /dev/md126, ignoring: Input/output error [ 513.707193] md: md126 stopped. ... [ Test Plan ] 1. Build two VROC RAID. One RAID 0 for System volume, another RAID 10 for Data volume. 2. Install system on System volume. 3. Update systemd. 4. Reboot the system. 5. Verify if the system can reboot. [ Where problems could occur ] The patch confirmed fixed the reboot issue on the system with two VROC RAIDs but more than two VROC RAIDs and the combinations of
[Touch-packages] [Bug 2035406] Re: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera
Okay, so looking again at the diff from 249.11-0ubuntu3.9 to 249.11-0ubuntu3.10[1], the only udev change is a new symlink for nvme devices. It seems very unlikely that this is related. The only other change that would be suspicious to me is the systemd.postinst change, i.e. requesting a reboot for this upgrade (because of bug 2013543), and not re-execing systemd. Since no one has indicated otherwise, can you please tell us if this bug persists after (a) sudo systemctl daemon-reexec, and/or (b) reboot? I have not yet looked into the details of the packages you are trying to use, so I am not sure if the above will help, but it will be very quick to test. [1] http://launchpadlibrarian.net/683070059/systemd_249.11-0ubuntu3.9_249.11-0ubuntu3.10.diff.gz ** Changed in: systemd (Ubuntu Jammy) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2035406 Title: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Incomplete Status in systemd source package in Lunar: Invalid Status in systemd source package in Mantic: Invalid Bug description: udev update has broken ubuntu's ability to import photos in digikam, gphoto2 can no longer see usb camera, entangle can no longer see camera after Upgrade: udev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-timesyncd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libpam-systemd:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libsystemd0:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libnss-systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev-dev:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), libudev1:i386 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10), systemd-sysv:amd64 (249.11-0ubuntu3.9, 249.11-0ubuntu3.10) ubuntu no longer allows gphoto2 or entangle control of my dslr, lsusb sees the camera fine, but the upgrade broke the usage, and cant roll back shows it will break system to roll back please fix ASAP. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: udev 249.11-0ubuntu3.10 ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13 Uname: Linux 6.2.0-1009-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 13 18:16:14 2023 InstallationDate: Installed on 2023-08-23 (21 days ago) InstallationMedia: Ubuntu-Studio 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) MachineType: Alienware Alienware 18 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-1009-lowlatency root=UUID=17502284-0952-44fe-81f8-54cebffc3800 ro threadirqs quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Alienware dmi.bios.version: A15 dmi.board.name: 0FT9KT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A15 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnAlienware:bvrA15:bd07/22/2019:efr1.1:svnAlienware:pnAlienware18:pvrA15:rvnAlienware:rn0FT9KT:rvrA00:cvnAlienware:ct8:cvrA15:skuAlienware18: dmi.product.family: 00 dmi.product.name: Alienware 18 dmi.product.sku: Alienware 18 dmi.product.version: A15 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035406/+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 2035585] Re: Versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2035585 Title: Versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329 Status in gst-plugins-bad1.0 package in Ubuntu: New Bug description: The versions in Ubuntu 20.04, 22.04 and 23.04 are vulnerable to CVE-2023-37329. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2035585/+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 2023545] Comment bridged from LTC Bugzilla
--- Comment From christian.r...@de.ibm.com 2023-09-14 03:15 EDT--- First, reproduced the behaviour of the problem as described and encountered the segmentation fault situation as described. Wrote out the coredump with coredumpctl dump and saw from the call stack the reported problem was reproduced. The installed libssl3 and openssl versions were: # dpkg -l libssl3 openssl Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=-- ii libssl3:s390x 3.0.2-0ubuntu1.10 s390xSecure Sockets Layer toolkit - shared libraries ii openssl3.0.2-0ubuntu1.10 s390xSecure Sockets Layer toolkit - cryptographic utility Next, added the ppa repository as instructed. # apt list --upgradable Listing... Done libssl-dev/jammy 3.0.2-0ubuntu1.11~ppa2 s390x [upgradable from: 3.0.2-0ubuntu1.10] libssl3/jammy 3.0.2-0ubuntu1.11~ppa2 s390x [upgradable from: 3.0.2-0ubuntu1.10] openssl/jammy 3.0.2-0ubuntu1.11~ppa2 s390x [upgradable from: 3.0.2-0ubuntu1.10] Successfully updated the three required packages to the version provided by the ppa package: # apt upgrade libssl3 openssl libssl-dev The following packages will be upgraded: libssl-dev libssl3 openssl 3 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. Need to get 5,038 kB of archives. After this operation, 5,120 B of additional disk space will be used. Do you want to continue? [Y/n] Y ... Cross-checked the libssl3 and openssl packages had been successfully upgraded: # dpkg -l libssl3 openssl Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-- ii libssl3:s390x 3.0.2-0ubuntu1.11~ppa2 s390xSecure Sockets Layer toolkit - shared libraries ii openssl3.0.2-0ubuntu1.11~ppa2 s390xSecure Sockets Layer toolkit - cryptographic utility Next checked the ibmca engine is still enabled, and subsequently was able to run the key generation request without encountering the segmentation fault. Thanks for providing the fix. Please integrate. Thanks. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl version OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022) # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' ..+..+.+..+...+.+.+..+...+.+.+*..+..+.+.+...++...++.+*+.+.+...+..+...+..+..+.+..+.+..+..+.++...+...+.+..+..++...+...+...+..+.+ +...+.++..++..+++.+..+...+.+...+.+..++*..+..+...+...+..+..+...+..+...+*++..+..+...++..+.+.+..+ - # echo RC=$? RC=0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2023545 Title: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate Status in Ubuntu on IBM z Systems: In Progress Status in openssl package in Ubuntu: In Progress Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel:
[Touch-packages] [Bug 2035220] Re: cve-2023-4863
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/2035220
Title:
cve-2023-4863
Status in chromium-browser package in Ubuntu:
Fix Released
Status in firefox package in Ubuntu:
Fix Released
Status in firefox-esr package in Ubuntu:
New
Status in libwebp package in Ubuntu:
New
Status in thunderbird package in Ubuntu:
Fix Released
Status in chromium package in Debian:
New
Status in libwebp package in Debian:
Confirmed
Bug description:
[$NA][1479274] Critical CVE-2023-4863: Heap buffer overflow in WebP. Reported
by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at
The University of Torontoʼs Munk School on 2023-09-06
https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-desktop_11.html
high profile remote vulnerability
themusicgod1@eva1:~$ apt-cache policy chromium-browser
chromium-browser:
Installed: 1:85.0.4183.83-0ubuntu2.22.04.1
Candidate: 1:85.0.4183.83-0ubuntu2.22.04.1
Version table:
current available snap:
chromium 116.0.5845.179
fix is in:
chromium 116.0.5845.187
ubuntu: 22.04.3 LTS jammy
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 12 08:38:06 2023
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda2 ext4 228G 162G 55G 75% /
tmpfs tmpfs 3.9G 66M 3.8G 2% /dev/shm
/dev/sda2 ext4 228G 162G 55G 75% /
InstallationDate: Installed on 2017-04-18 (2337 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: MSI MS-7994
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic
root=UUID=333c5e4f-3f61-4abf-b950-f19431c843d6 ro text
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 116.0.5845.179
(17ff023f3eb4f6883321db9399bfc65560ef84a9-refs/branch-heads/5845@{#1745})
Snap.ChromiumVersion: Chromium 116.0.5845.179 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to jammy on 2023-06-14 (89 days ago)
dmi.bios.date: 12/16/2016
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.80
dmi.board.asset.tag: Default string
dmi.board.name: H110M GAMING (MS-7994)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.80:bd12/16/2016:br5.12:svnMSI:pnMS-7994:pvr1.0:rvnMSI:rnH110MGAMING(MS-7994):rvr1.0:cvnMSI:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7994
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: MSI
mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035220/+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 2035397] Re: I had a problem with HDMI
I'm guessing the HDMI port is connected to the Nvidia GPU, it usually is on a hybrid laptop. And I'm seeing that you don't have a proper driver for the Nvidia GPU installed. Please open the 'Additional Drivers' app to install a supported Nvidia driver. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: hybrid multigpu multimonitor nouveau -- 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/2035397 Title: I had a problem with HDMI Status in Ubuntu: Incomplete Bug description: I don't know a lot about Linux and Ubuntu, but recently, due to college, I did a duo boot so I could have both Windows and Linux. But, whenever im at Linux, for some reason, my screen doesn't share with another monitor through HDMI, but with Windows it does. So i searched for some instructions, and ive been told to try and run this code in my therminal ubuntu-bug xorg, and that's why im here. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 13:56:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited CometLake-H GT2 [UHD Graphics] [1d05:1116] NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Tongfang Hongkong Limited GA106M [GeForce RTX 3060 Mobile / Max-Q] [1d05:1116] InstallationDate: Installed on 2023-08-31 (13 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Avell High Performance A70 LIV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=c99dc4b0-1110-43e9-a231-5487f4e4ce0d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.07AVE00 dmi.board.asset.tag: Standard dmi.board.name: Avell A70 LIV dmi.board.vendor: Avell High Performance dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: Standard dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.07AVE00:bd02/22/2021:br5.17:efr1.14:svnAvellHighPerformance:pnA70LIV:pvrStandard:rvnAvellHighPerformance:rnAvellA70LIV:rvrStandard:cvnAvellHighPerformance:ct10:cvrStandard:skuA70LIV: dmi.product.family: A70 LIV dmi.product.name: A70 LIV dmi.product.sku: A70 LIV dmi.product.version: Standard dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2035397/+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
