Bug#1041689: [Pkg-utopia-maintainers] Bug#1041689: udisks2: After upgrading to 2.10.0-3 on trixie, the service udisks2 does not start.

2023-07-22 Thread Marc Bres Gil
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)
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]: *** stack smashing detected ***:
terminated
de jul. 22 22:52:46 helm systemd[1]: udisks2.service: Main process exited,
code=killed, status=6/ABRT
de jul. 22 22:52:46 helm systemd[1]: udisks2.service: Failed with result
'signal'.
de jul. 22 22:52:46 helm systemd[1]: Failed to start udisks2.service - Disk
Manager.
-- Boot d1305a6d74754540b463848b4b0e353c --
de jul. 22 22:53:18 helm systemd[1]: Starting udisks2.service - Disk
Manager...
de jul. 22 22:53:18 helm udisksd[940]: udisks daemon version 2.10.0
starting
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)
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]: 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:18 helm udisksd[940]: Error getting 'loop7' information:
Failed to get status of the device loop7: No such device or address

Bug#1041689: [Pkg-utopia-maintainers] Bug#1041689: udisks2: After upgrading to 2.10.0-3 on trixie, the service udisks2 does not start.

2023-07-22 Thread Michael Biebl

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



OpenPGP_signature
Description: OpenPGP digital signature