Bug#1041689: stack smashing detected in libnvme
I've downloaded it from sid repositories, installed manually and seems to work. Thank you On 6/8/23 10:31, Daniel Baumann wrote: Hi Marc, I think the bug you reported is fixed when using libnvme 1.5-2. Can you confirm? Regards, Daniel
Bug#1041689: [Pkg-utopia-maintainers] Bug#1041689: Bug#1041689: Bug#1041689: udisks2: After upgrading to 2.10.0-3 on trixie, the service udisks2 does not start.
Hello Michael, I went to upstream with the traces, and found an already reported bug there on issues after updating to 2.10 with kde plasma ( https://github.com/storaged-project/udisks/issues/1139) . Added the info to that bug report, for what I understand from the gdb trace, seems related to some nvme function. Will see if it helps there. Thanks for your guidance Missatge de Michael Biebl del dia dg., 23 de jul. 2023 a les 10:03: > Am 23.07.23 um 09:53 schrieb Michael Biebl: > > > @Marc: Can you please install the udisks2/libblockdev dbgsym package, > > gather a backtrace and then filing the issue upstream. > > > https://wiki.debian.org/HowToGetABacktrace > -- Marc Bres Gil m...@bres.cat marc.b...@gmail.com
Bug#1041689: [Pkg-utopia-maintainers] Bug#1041689: Bug#1041689: udisks2: After upgrading to 2.10.0-3 on trixie, the service udisks2 does not start.
Good morning John the missing libraries messages occur when using udisks 2.9.4, which starts just fine. After upgrading to udisks 2.10.0-3 is when fails, and no libraries missing error shows, only the multiple "error getting loop6/7" errors and ends with a *** stack smashing detected ***: terminated message. Missatge de John Cooper del dia ds., 22 de jul. 2023 a les 23:24: > Hi, > > I had a look at this (included logs) and noticed that the udisks2 2.10.0-3 > on trixie is complaining about not being able to find or load some > libraries. Namely libbd_crypto.so.2 and libbd_mdraid.so.2. Without these > libraries the rest of udisks2 Daemon fails and crashes. It’s these missing > or un-loadable libraries causing the issue. > > Sent from my iPad > > On 22 Jul 2023, at 22:03, Marc Bres Gil wrote: > > > Hello, > > thanks for your quick answer. Here are the logs you asked. > > Systemctl: > > × udisks2.service - Disk Manager > Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; preset: > enabled) > Active: failed (Result: signal) since Sat 2023-07-22 22:53:20 CEST; > 1min 10s ago >Docs: man:udisks(8) > Process: 1286 ExecStart=/usr/libexec/udisks2/udisksd (code=killed, > signal=ABRT) >Main PID: 1286 (code=killed, signal=ABRT) > CPU: 28ms > > de jul. 22 22:53:20 helm systemd[1]: Starting udisks2.service - Disk > Manager... > de jul. 22 22:53:20 helm udisksd[1286]: udisks daemon version 2.10.0 > starting > de jul. 22 22:53:20 helm udisksd[1286]: Error getting 'loop6' information: > Failed to get status of the device loop6: No such device or address > (g-bd-loop-error-quark, 1) > de jul. 22 22:53:20 helm udisksd[1286]: Error getting 'loop7' information: > Failed to get status of the device loop7: No such device or address > (g-bd-loop-error-quark, 1) > de jul. 22 22:53:20 helm udisksd[1286]: Error getting 'loop6' information: > Failed to get status of the device loop6: No such device or address > (g-bd-loop-error-quark, 1) > de jul. 22 22:53:20 helm udisksd[1286]: Error getting 'loop7' information: > Failed to get status of the device loop7: No such device or address > (g-bd-loop-error-quark, 1) > de jul. 22 22:53:20 helm udisksd[1286]: *** stack smashing detected ***: > terminated > de jul. 22 22:53:20 helm systemd[1]: udisks2.service: Main process exited, > code=killed, status=6/ABRT > de jul. 22 22:53:20 helm systemd[1]: udisks2.service: Failed with result > 'signal'. > de jul. 22 22:53:20 helm systemd[1]: Failed to start udisks2.service - > Disk Manager. > > - > Journalctl, before upgrading on udisks 2.9.4 starts ok, and after > upgrading on 2.10.0 fails: > > -- Boot 567f68c732264f54917bdb7a37b26720 -- > de jul. 22 22:49:27 helm systemd[1]: Starting udisks2.service - Disk > Manager... > de jul. 22 22:49:27 helm udisksd[945]: udisks daemon version 2.9.4 > starting > de jul. 22 22:49:27 helm udisksd[945]: failed to load module crypto: > libbd_crypto.so.2: cannot open shared object file: No such file or > directory > de jul. 22 22:49:27 helm udisksd[945]: failed to load module mdraid: > libbd_mdraid.so.2: cannot open shared object file: No such file or > directory > de jul. 22 22:49:27 helm udisksd[945]: Failed to load the 'mdraid' > libblockdev plugin > de jul. 22 22:49:27 helm udisksd[945]: Failed to load the 'crypto' > libblockdev plugin > de jul. 22 22:49:27 helm systemd[1]: Started udisks2.service - Disk > Manager. > de jul. 22 22:49:27 helm udisksd[945]: Acquired the name > org.freedesktop.UDisks2 on the system message bus > de jul. 22 22:52:46 helm systemd[1]: Stopping udisks2.service - Disk > Manager... > de jul. 22 22:52:46 helm udisksd[945]: udisks daemon version 2.9.4 exiting > de jul. 22 22:52:46 helm systemd[1]: udisks2.service: Deactivated > successfully. > de jul. 22 22:52:46 helm systemd[1]: Stopped udisks2.service - Disk > Manager. > de jul. 22 22:52:46 helm systemd[1]: Starting udisks2.service - Disk > Manager... > de jul. 22 22:52:46 helm udisksd[4414]: udisks daemon version 2.10.0 > starting > de jul. 22 22:52:46 helm udisksd[4414]: Error getting 'loop6' information: > Failed to get status of the device loop6: No such device or address > (g-bd-loop-error-quark, 1) > de jul. 22 22:52:46 helm udisksd[4414]: Error getting 'loop7' information: > Failed to get status of the device loop7: No such device or address > (g-bd-loop-error-quark, 1) > de jul. 22 22:52:46 helm udisksd[4414]: Error getting 'loop6' information: > Failed to get status of the device loop6: No such device or address > (g-bd-loop-error-quark, 1)
Bug#1041689: [Pkg-utopia-maintainers] Bug#1041689: udisks2: After upgrading to 2.10.0-3 on trixie, the service udisks2 does not start.
1) de jul. 22 22:53:18 helm udisksd[940]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1) de jul. 22 22:53:18 helm udisksd[940]: *** stack smashing detected ***: terminated de jul. 22 22:53:18 helm systemd[1]: udisks2.service: Main process exited, code=killed, status=6/ABRT de jul. 22 22:53:18 helm systemd[1]: udisks2.service: Failed with result 'signal'. de jul. 22 22:53:18 helm systemd[1]: Failed to start udisks2.service - Disk Manager. de jul. 22 22:53:20 helm systemd[1]: Starting udisks2.service - Disk Manager... de jul. 22 22:53:20 helm udisksd[1286]: udisks daemon version 2.10.0 starting de jul. 22 22:53:20 helm udisksd[1286]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1) de jul. 22 22:53:20 helm udisksd[1286]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1) de jul. 22 22:53:20 helm udisksd[1286]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1) de jul. 22 22:53:20 helm udisksd[1286]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1) de jul. 22 22:53:20 helm udisksd[1286]: *** stack smashing detected ***: terminated de jul. 22 22:53:20 helm systemd[1]: udisks2.service: Main process exited, code=killed, status=6/ABRT de jul. 22 22:53:20 helm systemd[1]: udisks2.service: Failed with result 'signal'. de jul. 22 22:53:20 helm systemd[1]: Failed to start udisks2.service - Disk Manager. Thank you Missatge de Michael Biebl del dia ds., 22 de jul. 2023 a les 22:04: > Control: tags -1 + moreinfo unreproducible > > Am 22.07.23 um 09:43 schrieb Marc Bres Gil: > > Package: udisks2 > > Version: 2.10.0-3 > > Severity: important > > X-Debbugs-Cc: marc.b...@gmail.com > > > > Dear Maintainer, > > > > * What led up to the situation? > >Upgrade udisks2 to 2.10.0-3 > > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > Upgrade with apt-update and apt-upgradem. > > > > * What was the outcome of this action? > >It broke my desktop system: As plasma-desktop seems to depend on > udisks2 for some functions, it let me out of my desktop. Luckily I've been > able to still access with cinnamon desktop to check and fill the bug > report. If I download the udisks2 from stable and its dependencies, and > then install it manually, udisks2 starts but it is not a real solution > > > > * What outcome did you expect instead? > > udisks2 continue working as usual before the upgrade > > I can't reproduce the problem. > > Can you please send me the output of > systemctl status udisks2.service > and > journalctl -u udisks2.service > > -- Marc Bres Gil m...@bres.cat marc.b...@gmail.com
Bug#1041689: udisks2: After upgrading to 2.10.0-3 on trixie, the service udisks2 does not start.
Package: udisks2 Version: 2.10.0-3 Severity: important X-Debbugs-Cc: marc.b...@gmail.com Dear Maintainer, * What led up to the situation? Upgrade udisks2 to 2.10.0-3 * What exactly did you do (or not do) that was effective (or ineffective)? Upgrade with apt-update and apt-upgradem. * What was the outcome of this action? It broke my desktop system: As plasma-desktop seems to depend on udisks2 for some functions, it let me out of my desktop. Luckily I've been able to still access with cinnamon desktop to check and fill the bug report. If I download the udisks2 from stable and its dependencies, and then install it manually, udisks2 starts but it is not a real solution * What outcome did you expect instead? udisks2 continue working as usual before the upgrade -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages udisks2 depends on: ii dbus 1.14.8-2 ii libacl12.3.1-3 ii libatasmart4 0.19-5 ii libblkid1 2.38.1-6 ii libblockdev-crypto33.0.1-2 ii libblockdev-fs33.0.1-2 ii libblockdev-loop3 3.0.1-2 ii libblockdev-mdraid33.0.1-2 ii libblockdev-nvme3 3.0.1-2 ii libblockdev-part3 3.0.1-2 ii libblockdev-swap3 3.0.1-2 ii libblockdev-utils3 3.0.1-2 ii libblockdev3 3.0.1-2 ii libc6 2.37-5 ii libglib2.0-0 2.74.6-2 ii libgudev-1.0-0 237-2 ii libmount1 2.38.1-6 ii libpolkit-agent-1-0122-4 ii libpolkit-gobject-1-0 122-4 ii libsystemd0253.5-1 ii libudisks2-0 2.10.0-3 ii libuuid1 2.38.1-6 ii parted 3.6-3 ii udev 253.5-1 Versions of packages udisks2 recommends: ii dosfstools 4.2-1 ii e2fsprogs 1.47.0-2 ii eject 2.38.1-6 ii exfatprogs 1.2.1-2 ii libpam-systemd 253.5-1 ii ntfs-3g 1:2022.10.3-1+b1 ii polkitd 122-4 Versions of packages udisks2 suggests: pn btrfs-progs pn f2fs-tools pn mdadm pn nilfs-tools pn reiserfsprogs pn udftools pn udisks2-btrfs pn udisks2-lvm2 pn xfsprogs -- no debconf information
