This bug was fixed in the package udisks2 - 2.10.1-1ubuntu2 --------------- udisks2 (2.10.1-1ubuntu2) noble; urgency=medium
* Don't build with -Wl,-Bsymbolic-functions. It breaks module loading, as it confuses GObject's type loading cache: "cannot register existing type 'UDisksDaemon'". (Patch also applied to Debian packaging git, can be synced next time). (LP: #2040488) -- Martin Pitt <martin.p...@ubuntu.com> Tue, 05 Dec 2023 11:25:08 +0000 ** Changed in: udisks2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2040488 Title: loading lvm2 module crashes: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Mantic: In Progress Bug description: [Impact] Trying to load the lvm2 module crashes udisks immediately: busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/Manager org.freedesktop.UDisks2.Manager EnableModule sb lvm2 true udisksd[5709]: cannot register existing type 'UDisksDaemon' udisksd[5709]: g_once_init_leave: assertion 'result != 0' failed udisksd[5709]: udisks_module_lvm2_new: assertion 'UDISKS_IS_DAEMON (daemon)' failed systemd[1]: Started systemd-coredump@2-5767-0.service - Process Core Dump (PID 5767/UID 0). Module libudev.so.1 from deb systemd-253.5-1ubuntu6.amd64 Module libsystemd.so.0 from deb systemd-253.5-1ubuntu6.amd64 Stack trace of thread 5709: #0 0x000056079be701ad udisks_module_manager_load_modules (udisksd + 0x601ad) #1 0x000056079be5fdf5 n/a (udisksd + 0x4fdf5) #2 0x00007f7d5f122a11 n/a (libglib-2.0.so.0 + 0x5aa11) #3 0x00007f7d5f17e46f n/a (libglib-2.0.so.0 + 0xb646f) #4 0x00007f7d5f12346f g_main_loop_run (libglib-2.0.so.0 + 0x5b46f) #5 0x000056079be323d2 main (udisksd + 0x223d2) #6 0x00007f7d5ee280d0 __libc_start_call_main (libc.so.6 + 0x280d0) #7 0x00007f7d5ee28189 __libc_start_main_impl (libc.so.6 + 0x28189) #8 0x000056079be324f5 _start (udisksd + 0x224f5) This breaks at least cockpit, and possibly other consumers of udisks (GNOME Disks perhaps?). This is a regression in mantic, earlier releases were fine. [Test Plan] The above reproducer confirms the check. The busctl command should succeed, and afterwards `systemctl status udisks2` should still be "active (running)" instead of "failed". autopkgtests should take care of regression testing. I'm also happy to run cockpit's integration tests against the updated version; it exercises udisks2 thoroughly (and we find lots of bugs with it). At the moment we don't test 23.10 mantic at all, because it is so broken (https://github.com/cockpit-project/bots/pull/5432). [Where problems could occur] Changing the linker options is quite invasive. The autopkgtests cover the runtime functionality though, and as modules are currently 100% broken they can't possibly get any worse. [Other info] Fix committed to Debian: https://salsa.debian.org/utopia- team/udisks2/-/commit/e22881abdd90bd4878add165ccc46008a17163f8 Noble debdiff: http://launchpadlibrarian.net/701038246/udisks2_2.10.1-1ubuntu1_2.10.1-1ubuntu2.diff.gz ProblemType: Crash Architecture: amd64 Date: Wed Oct 25 12:13:14 2023 DistroRelease: Ubuntu 23.10 ExecutablePath: /usr/libexec/udisks2/udisksd Package: udisks2 2.10.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2040488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp