Your message dated Sun, 23 Jul 2023 21:38:45 +0000
with message-id <[email protected]>
and subject line Bug#1041649: fixed in udisks2 2.10.0-4
has caused the Debian Bug report #1041649,
regarding udisks2: udisksd report errors Error getting 'loop0' information:
Failed to get status of the device loop0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1041649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041649
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: udisks2
Version: 2.10.0-3
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
Upgrade of package udisks2 from 2.9.4-4 to 2.10.0-3.
More precisely, unattended-upgrade did the following batch:
----------------------------------------------------------------------
Packages that were upgraded:
anacron bsdextrautils bsdutils fdisk libavif15 libblkid1 libcdr-0.1-1
libexttextcat-2.0-0 libexttextcat-data libfdisk1 libmount1
librubberband2 libselinux1 libsemanage-common libsemanage2 libsepol2
libsmartcols1 libudisks2-0 libuuid1 media-types mount rfkill udisks2
util-linux util-linux-extra util-linux-locales
Packages that were auto-removed:
libblockdev-part-err2 libblockdev-part2 libblockdev-fs2
libblockdev-loop2 libblockdev2 gdisk libparted-fs-resize0
libblockdev-swap2
----------------------------------------------------------------------
Plus the installation of the libblockdev*3 replacements of those packages
that got auto-removed.
* What was the outcome of this action?
Getting below errors in the journal, both during boot and when mounting a
loop device. Other than errors being reported everything seems to work
normally. This system comes without a desktop environment and has a
APT::Install-Recommends == false setting.
Here the journal during startup with a bunch of these messages:
----------------------------------------------------------------------
[ 21.131297] sappc1 udisksd[968]: Error getting 'loop0' information: Failed
to get status of the device loop0: No such device or address
(g-bd-loop-error-quark, 1)
[ 21.131460] sappc1 udisksd[968]: Error getting 'loop1' information: Failed
to get status of the device loop1: No such device or address
(g-bd-loop-error-quark, 1)
[ 21.131618] sappc1 udisksd[968]: Error getting 'loop2' information: Failed
to get status of the device loop2: No such device or address
(g-bd-loop-error-quark, 1)
[ 21.131768] sappc1 udisksd[968]: Error getting 'loop3' information: Failed
to get status of the device loop3: No such device or address
(g-bd-loop-error-quark, 1)
[ 21.131922] sappc1 udisksd[968]: Error getting 'loop4' information: Failed
to get status of the device loop4: No such device or address
(g-bd-loop-error-quark, 1)
[ 21.132156] sappc1 udisksd[968]: Error getting 'loop5' information: Failed
to get status of the device loop5: No such device or address
(g-bd-loop-error-quark, 1)
[ 21.132340] sappc1 udisksd[968]: Error getting 'loop6' information: Failed
to get status of the device loop6: No such device or address
(g-bd-loop-error-quark, 1)
[ 21.132481] sappc1 NetworkManager[984]: <info> [1689929537.4442]
bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
[ 21.132512] sappc1 systemd[1]: Started NetworkManager.service - Network
Manager.
[ 21.132531] sappc1 udisksd[968]: Error getting 'loop7' information: Failed
to get status of the device loop7: No such device or address
(g-bd-loop-error-quark, 1)
----------------------------------------------------------------------
Here the journal corresponding to a (loop mount, loop unmount) cycle:
----------------------------------------------------------------------
[27502.382864] foobar kernel: loop0: detected capacity change from 0 to 2097152
[27502.287538] foobar udisksd[968]: Set up loop device /dev/loop0 (backed by
/media/usb/Documents/data00.vol)
[27515.952475] foobar udisksd[968]: Deleted loop device /dev/loop0 (was backed
by /media/usb/Documents/data00.vol)
[27515.953535] foobar udisksd[968]: No longer watching loop device /dev/loop0
[27515.957314] foobar udisksd[968]: Error getting 'loop0' information: Failed
to get status of the device loop0: No such device or address
(g-bd-loop-error-quark, 1)
[27515.958549] foobar udisksd[968]: Error getting 'loop0' information: Failed
to get status of the device loop0: No such device or address
(g-bd-loop-error-quark, 1)
[27519.987721] foobar kernel: loop0: detected capacity change from 0 to 2097152
[27519.896150] foobar udisksd[968]: Set up loop device /dev/loop0 (backed by
/media/usb/Documents/data00.vol)
[27528.280587] foobar udisksd[968]: Unlocked device /dev/loop0 as /dev/dm-6
[27528.359394] foobar udisksd[968]: Mounted /dev/dm-6 at /media/data00 on
behalf of uid 1000
[27538.533501] foobar systemd[1]: media-data00.mount: Deactivated successfully.
[27538.533798] foobar udisksd[968]: Cleaning up mount point /media/data00
(device 253:6 is not mounted)
[27538.535520] foobar udisksd[968]: Unmounted /dev/dm-6 on behalf of uid 1000
[27538.753368] foobar kernel: dm-6: detected capacity change from 2064384 to 0
[27538.616470] foobar udisksd[968]: Removing unlocked-crypto-dev entry {uint64
64774, {'crypto-device': <uint64 1792>, 'dm-uuid':
<b'CRYPT-LUKS2-SOME-FUNNY-UUID'>, 'unlocked-by-uid': <uint32 1000>}} because
/dev/dm-6 now has another dm-uuid (NULL)
[27538.617060] foobar udisksd[968]: Removing unlocked-crypto-dev entry {uint64
64774, {'crypto-device': <uint64 1792>, 'dm-uuid':
<b'CRYPT-LUKS2-SOME-FUNNY-UUID'>, 'unlocked-by-uid': <uint32 1000>}} because
/dev/dm-6 now has another dm-uuid (NULL)
[27538.645218] foobar udisksd[968]: Locked device /dev/loop0 (was unlocked as
/dev/dm-6)
[27538.728625] foobar udisksd[968]: Deleted loop device /dev/loop0 (was backed
by /media/usb/Documents/data00.vol)
[27538.729370] foobar udisksd[968]: No longer watching loop device /dev/loop0
[27538.730442] foobar udisksd[968]: Error getting 'loop0' information: Failed
to get status of the device loop0: No such device or address
(g-bd-loop-error-quark, 1)
[27538.731263] foobar udisksd[968]: Error getting 'loop0' information: Failed
to get status of the device loop0: No such device or address
(g-bd-loop-error-quark, 1)
[27540.665841] foobar systemd[1]: media-usb.mount: Deactivated successfully.
[27540.668558] foobar udisksd[968]: Cleaning up mount point /media/usb (device
8:1 is not mounted)
----------------------------------------------------------------------
* What outcome did you expect instead?
No errors, as before the upgrade.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
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 libacl1 2.3.1-3
ii libatasmart4 0.19-5
ii libblkid1 2.38.1-6
ii libblockdev-crypto3 3.0.1-2
ii libblockdev-fs3 3.0.1-2
ii libblockdev-loop3 3.0.1-2
ii libblockdev-mdraid3 3.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-0 122-4
ii libpolkit-gobject-1-0 122-4
ii libsystemd0 253.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
pn eject <none>
pn exfatprogs <none>
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 <none>
pn f2fs-tools <none>
ii mdadm 4.2+20230508-5
pn nilfs-tools <none>
pn reiserfsprogs <none>
pn udftools <none>
pn udisks2-btrfs <none>
pn udisks2-lvm2 <none>
pn xfsprogs <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: udisks2
Source-Version: 2.10.0-4
Done: Michael Biebl <[email protected]>
We believe that the bug you reported is fixed in the latest version of
udisks2, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <[email protected]> (supplier of updated udisks2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 23 Jul 2023 22:02:00 +0200
Source: udisks2
Architecture: source
Version: 2.10.0-4
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<[email protected]>
Changed-By: Michael Biebl <[email protected]>
Closes: 1041649
Changes:
udisks2 (2.10.0-4) unstable; urgency=medium
.
* Drop obsolete --disable-vdo configure switch as well
* udiskslinuxloop: Avoid warnings on empty loop devices (Closes: #1041649)
Checksums-Sha1:
561e51bb067dcc3b076b58da47204ae3bd573a23 3460 udisks2_2.10.0-4.dsc
b572c28d0969af01172cfff4e33fdd0afa62896e 19968 udisks2_2.10.0-4.debian.tar.xz
82922bd6472c038173f0907df206992b014d314e 9641 udisks2_2.10.0-4_source.buildinfo
Checksums-Sha256:
07514a5fda5e3d9790fcfb15e11f44cbe9ad107233cdc520e5f8210fef77bd5c 3460
udisks2_2.10.0-4.dsc
851831bc6989b6375d4412443eafffa356c2af62156c2eb8a82d62f1981e781a 19968
udisks2_2.10.0-4.debian.tar.xz
ba3ea643f8c726d018d0eb68275252dcfacea9b8f64a1ad04fdc6dbb7715883e 9641
udisks2_2.10.0-4_source.buildinfo
Files:
a8beead53c01deb78c448196c2c344de 3460 admin optional udisks2_2.10.0-4.dsc
7213df3b48e1a74308e3813e9a33e8de 19968 admin optional
udisks2_2.10.0-4.debian.tar.xz
484f96c947e13317bbe38291bf814a8c 9641 admin optional
udisks2_2.10.0-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAmS9kaEACgkQauHfDWCP
ItyRTA/9HTwjClzESv4TufVfnTrw3IPj0bR62oleRfsUtbfJLFSogrfvzwKIDMO8
jRKKUs9dy1vyHe/xBnnYPNH+ctlnNL6oIVtbOginNMj3jMKLmTFprjj6GFBSkI3J
vH3RUqfsn1Nqug99KseDCE625Vp6XX4FI7KXv2Vu2HVd8/Vu4wZ0jZu168X7gSOg
AJyQz+WRfDd/yFtPt/S8E5WN0jOA7CNnYj+LPRl3dFdU0UCha5irTmJQALIwZ03O
3Th4yGJOE+7jtqrM8AefnRJ5sIpW4gQ6Z4aLjJAV9fEvqQbRk5pvkbEc86ufEvy1
C4k9u6heq2fGI8iowzL8Q0BCmq6SkPz4QukfLdmsDgz38jqMtzDTtRBsQmpiQFxE
l+4eQvMHKX35zqoJTaJkNxcVmg0YCQB3w4CHVhZ/MSkW/EqgXd2BdjTLKMxlorv3
/JdNesAHKVBbv3MsR3LN4lK8NwI5izgwX14jXhVXoWT07Z1QzgbtVK5bpC/NoybU
FILAUTZFvToPSOWGD6eOPrBhFyQ7490/d+8xMMdSrKhDO0wucZ06YHMkGIaMT0fr
IwzLj6NDXc2ui45A3mmw8mVxAoQl8ISD5oYh+SCT15FgoVFa7Z50OkPreyyLf19d
57QXKll1TjhiB52ceyG2aWRhgBrLir+X96JbzfG69biMYX58/nM=
=hcgl
-----END PGP SIGNATURE-----
--- End Message ---
