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
