Your message dated Fri, 4 Aug 2023 22:54:59 +0200
with message-id <78d189fe-886b-4ade-882b-370c7866e...@debian.org>
and subject line Re: [Pkg-utopia-maintainers] Bug#1041649: Bug still present in
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 ow...@bugs.debian.org
immediately.)
--
1041649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udisks2
Version: 2.10.0-3
Severity: normal
X-Debbugs-Cc: in.cognit...@arcor.de
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 ---
Am 04.08.23 um 21:21 schrieb Farblos:
Control: reopen
Thanks for taking care of this one, and sorry for re-opening.
I must have rebooted already a couple of times since udisks2/2.10.0-4
got installed by unattended upgrades, and I still see these messages:
Since I myself can't reproduce the issue anymore with 2.10.0-4, I'm
going to close this bug report again and you ask you to report this
upstream as a separate issue.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
