<div dir="ltr"><div>Good morning John</div><div><br></div><div>the missing libraries messages occur when using udisks 2.9.4, which starts just fine. <br></div><div><br></div><div>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 <span style="font-family:monospace">*** stack smashing detected ***: terminated message.</span></div><div><span style="font-family:monospace"><br></span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Missatge de John Cooper <<a href="mailto:johnpcooper@icloud.com">johnpcooper@icloud.com</a>> del dia ds., 22 de jul. 2023 a les 23:24:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><span style="color:rgb(0,0,0)">Hi,</span><div><span style="color:rgb(0,0,0)"><br></span></div><div><span style="color:rgb(0,0,0)">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 <font face="AppleSDGothicNeo-Regular">libbd_crypto.so.2 and </font></span><font face="AppleSDGothicNeo-Regular">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.</font><span style="color:rgb(0,0,0)"><br></span><br><div dir="ltr">Sent from my iPad</div><div dir="ltr"><br><blockquote type="cite">On 22 Jul 2023, at 22:03, Marc Bres Gil <<a href="mailto:marc.bres@gmail.com" target="_blank">marc.bres@gmail.com</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>Hello,</div><div><br></div><div>thanks for your quick answer. Here are the logs you asked.</div><div><br></div><div>Systemctl:</div><div><br></div><div>× udisks2.service - Disk Manager<br> Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; preset: enabled)<br> Active: failed (Result: signal) since Sat 2023-07-22 22:53:20 CEST; 1min 10s ago<br> Docs: man:udisks(8)<br> Process: 1286 ExecStart=/usr/libexec/udisks2/udisksd (code=killed, signal=ABRT)<br> Main PID: 1286 (code=killed, signal=ABRT)<br> CPU: 28ms<br><br>de jul. 22 22:53:20 helm systemd[1]: Starting udisks2.service - Disk Manager...<br>de jul. 22 22:53:20 helm udisksd[1286]: udisks daemon version 2.10.0 starting<br>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)<br>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)<br>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)<br>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)<br>de jul. 22 22:53:20 helm udisksd[1286]: *** stack smashing detected ***: terminated<br>de jul. 22 22:53:20 helm systemd[1]: udisks2.service: Main process exited, code=killed, status=6/ABRT<br>de jul. 22 22:53:20 helm systemd[1]: udisks2.service: Failed with result 'signal'.<br>de jul. 22 22:53:20 helm systemd[1]: Failed to start udisks2.service - Disk Manager.</div><div><br></div><div>-----------------------------------------<br></div><div></div><div>Journalctl, before upgrading on udisks 2.9.4 starts ok, and after upgrading on 2.10.0 fails:<br></div><div><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">-- Boot 567f68c732264f54917bdb7a37b26720 --
</span><br>de jul. 22 22:49:27 helm systemd[1]: Starting udisks2.service - Disk Manager...
<br>de jul. 22 22:49:27 helm udisksd[945]: udisks daemon version 2.9.4 starting
<br>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
<br>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
<br>de jul. 22 22:49:27 helm udisksd[945]: Failed to load the 'mdraid' libblockdev plugin
<br>de jul. 22 22:49:27 helm udisksd[945]: Failed to load the 'crypto' libblockdev plugin
<br>de jul. 22 22:49:27 helm systemd[1]: Started udisks2.service - Disk Manager.
<br>de jul. 22 22:49:27 helm udisksd[945]: Acquired the name org.freedesktop.UDisks2 on the system message bus
<br>de jul. 22 22:52:46 helm systemd[1]: Stopping udisks2.service - Disk Manager...
<br>de jul. 22 22:52:46 helm udisksd[945]: udisks daemon version 2.9.4 exiting
<br>de jul. 22 22:52:46 helm systemd[1]: udisks2.service: Deactivated successfully.
<br>de jul. 22 22:52:46 helm systemd[1]: Stopped udisks2.service - Disk Manager.
<br>de jul. 22 22:52:46 helm systemd[1]: Starting udisks2.service - Disk Manager...
<br>de jul. 22 22:52:46 helm udisksd[4414]: udisks daemon version 2.10.0 starting
<br>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)
<br>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)
<br>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)
<br>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)
<br>de jul. 22 22:52:46 helm udisksd[4414]: *** stack smashing detected ***: terminated
<br>de jul. 22 22:52:46 helm systemd[1]: udisks2.service: Main process exited, code=killed, status=6/ABRT
<br>de jul. 22 22:52:46 helm systemd[1]: udisks2.service: Failed with result 'signal'.
<br>de jul. 22 22:52:46 helm systemd[1]: Failed to start udisks2.service - Disk Manager.
<br>-- Boot d1305a6d74754540b463848b4b0e353c --
<br>de jul. 22 22:53:18 helm systemd[1]: Starting udisks2.service - Disk Manager...
<br>de jul. 22 22:53:18 helm udisksd[940]: udisks daemon version 2.10.0 starting
<br>de jul. 22 22:53:18 helm udisksd[940]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
<br>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)
<br>de jul. 22 22:53:18 helm udisksd[940]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
<br>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)
<br>de jul. 22 22:53:18 helm udisksd[940]: *** stack smashing detected ***: terminated
<br>de jul. 22 22:53:18 helm systemd[1]: udisks2.service: Main process exited, code=killed, status=6/ABRT
<br>de jul. 22 22:53:18 helm systemd[1]: udisks2.service: Failed with result 'signal'.
<br>de jul. 22 22:53:18 helm systemd[1]: Failed to start udisks2.service - Disk Manager.
<br>de jul. 22 22:53:20 helm systemd[1]: Starting udisks2.service - Disk Manager...
<br>de jul. 22 22:53:20 helm udisksd[1286]: udisks daemon version 2.10.0 starting
<br>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)
<br>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)
<br>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)
<br>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)
<br>de jul. 22 22:53:20 helm udisksd[1286]: *** stack smashing detected ***: terminated
<br>de jul. 22 22:53:20 helm systemd[1]: udisks2.service: Main process exited, code=killed, status=6/ABRT
<br>de jul. 22 22:53:20 helm systemd[1]: udisks2.service: Failed with result 'signal'.
<br>de jul. 22 22:53:20 helm systemd[1]: Failed to start udisks2.service - Disk Manager.<br></span></div><div><br></div><div><br></div><div>Thank you<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Missatge de Michael Biebl <<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>> del dia ds., 22 de jul. 2023 a les 22:04:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Control: tags -1 + moreinfo unreproducible<br>
<br>
Am 22.07.23 um 09:43 schrieb Marc Bres Gil:<br>
> Package: udisks2<br>
> Version: 2.10.0-3<br>
> Severity: important<br>
> X-Debbugs-Cc: <a href="mailto:marc.bres@gmail.com" target="_blank">marc.bres@gmail.com</a><br>
> <br>
> Dear Maintainer,<br>
> <br>
> * What led up to the situation?<br>
> Upgrade udisks2 to 2.10.0-3<br>
> <br>
> * What exactly did you do (or not do) that was effective (or<br>
> ineffective)?<br>
> Upgrade with apt-update and apt-upgradem.<br>
> <br>
> * What was the outcome of this action?<br>
> 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<br>
> <br>
> * What outcome did you expect instead?<br>
> udisks2 continue working as usual before the upgrade<br>
<br>
I can't reproduce the problem.<br>
<br>
Can you please send me the output of<br>
systemctl status udisks2.service<br>
and<br>
journalctl -u udisks2.service<br>
<br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Marc Bres Gil<br><a href="mailto:marc@bres.cat" target="_blank">marc@bres.cat</a><br><a href="mailto:marc.bres@gmail.com" target="_blank">marc.bres@gmail.com</a></div>
<span>_______________________________________________</span><br><span>Pkg-utopia-maintainers mailing list</span><br><span><a href="mailto:Pkg-utopia-maintainers@alioth-lists.debian.net" target="_blank">Pkg-utopia-maintainers@alioth-lists.debian.net</a></span><br><span><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers</a></span><br></div></blockquote></div></div></blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Marc Bres Gil<br><a href="mailto:marc@bres.cat" target="_blank">marc@bres.cat</a><br><a href="mailto:marc.bres@gmail.com" target="_blank">marc.bres@gmail.com</a></div>