You are not logged in.
Pages: 1
No github is required to report bugs - that's what reportbug is for. I think you'll want to use -B debian since udisks2 is not a forked package.
You mean, I could report this to Debian from this Devuan system?
Alternatively, I could install an up-to-date Debian system, and report it from there; I have been thinking of giving Debian another try anyway. Would that be more efficient, or wouldn’t it really matter?
I can confirm that the issue is not with labels, at least not that alone. Perhaps it's a combination of label and apfs, or even just an issue with apfs.
I have just done a test with a file-based loopback device with two ext4 partitions—one with a label, and one without, and you’re right: both will mount and unmount properly.
So, apparently something goes wrong with APFS; unfortunately, I have no access to a labelled APFS partition, hence I cannot test that combination.
You should probably report it to upstream.
I wouldn’t mind doing so, but I don’t have a GitHub account; I’m reluctant to creating one, after I have cleaned up a whole range of accounts on various web sites.
I got a dump of a complete Apple MacBook Air system disk, and I’m trying to access it through the ‘udisksctl’ utility, so I can read its contents. It mostly works—I installed the “apfs-dkms” package to support the APFS Apple filesystem.
There’s one little snag that I’m running into, however, in that the ‘udisksctl’ utility runs into an error when I attempt to unmount the APFS filesystem; the standard ‘umount’ command, on the other hand, will successfully unmount the filesystem.
I think I understand the cause of the problem; it looks like ‘udisksctl’ doesn’t record the mount point of a filesystem that doesn’t have a label; when it is subsequently instructed to unmount the filesystem, it thinks it wasn’t mounted in the first place, and consequently won’t unmount it. I have no idea how to get this issue resolved, however.
Just to illustrate the issue, the remainder of this post will explain what I’m doing, and where exactly it goes wrong.
The dump file is called ‘APPLE_SSD_SM0128.DMP’; I first associate a loop device with the file:
$ /usr/bin/udisksctl loop-setup --read-only --file APPLE_SSD_SM0128.DMP
Mapped file APPLE_SSD_SM0128.DMP as /dev/loop0.Since I will be running this in a script, I want to catch the name of the loop device into a variable; the ‘losetup’ utility will eventually help me out here:
$ /sbin/losetup --output NAME,BACK-FILE --associated APPLE_SSD_SM0128.DMP
NAME BACK-FILE
/dev/loop0 /mnt/local/Legacy/Apple MacBook Air/APPLE_SSD_SM0128.DMPNext, I list the partitions that are present in the dump file:
$ /bin/lsblk --output TYPE,PATH,FSTYPE,LABEL,MOUNTPOINT --list /dev/loop0
TYPE PATH FSTYPE LABEL MOUNTPOINT
loop /dev/loop0
part /dev/loop0p1 vfat EFI
part /dev/loop0p2 apfsI can mount the first partition alright:
$ /usr/bin/udisksctl mount --block-device /dev/loop0p1
Mounted /dev/loop0p1 at /media/luvr/EFIIf I list the partitions again, then I can clearly see the mountpoint:
$ /bin/lsblk --output TYPE,PATH,FSTYPE,LABEL,MOUNTPOINT --list /dev/loop0
TYPE PATH FSTYPE LABEL MOUNTPOINT
loop /dev/loop0
part /dev/loop0p1 vfat EFI /media/luvr/EFI
part /dev/loop0p2 apfsThe partition will unmount cleanly as well:
$ /usr/bin/udisksctl unmount --block-device /dev/loop0p1
Unmounted /dev/loop0p1.Now it’s time to try the same with the second partition on the dump file:
$ /usr/bin/udisksctl mount --block-device /dev/loop0p2
Mounted /dev/loop0p2 at /media/luvr/2a0db02b-d459-4583-a12f-f83c395bfe6d
$ /bin/lsblk --output TYPE,PATH,FSTYPE,LABEL,MOUNTPOINT --list /dev/loop0
TYPE PATH FSTYPE LABEL MOUNTPOINT
loop /dev/loop0
part /dev/loop0p1 vfat EFI
part /dev/loop0p2 apfs /media/luvr/2a0db02b-d459-4583-a12f-f83c395bfe6dSo far, so good; so, let’s unmount again:
$ /usr/bin/udisksctl unmount --block-device /dev/loop0p2
Error unmounting /dev/loop0p2: GDBus.Error:org.freedesktop.UDisks2.Error.NotMounted: Device `/dev/loop0p2' is not mountedHmmm… That does not seem to work.
What does work, is the ‘umount’ command:
$ sudo umount /dev/loop0p2
[sudo] password for root:After this, I can clean up and break the association between the loop device and the dump file:
$ /usr/bin/udisksctl loop-delete --block-device /dev/loop0Where does the ‘udisksctl’ Utility go wrong?
After some further investigation, I believe that ‘udisksctl’ won’t record the mount point of a partition for which no label was set. Indeed, when the first partition—which has its filesystem label set to “EFI”—is mounted, its info, as reported by the ‘udisksctl’ utility will correctly report the mountpoint (see the “MountPoints:” line below):
$ /usr/bin/udisksctl info --block-device /dev/loop0p1
/org/freedesktop/UDisks2/block_devices/loop0p1:
org.freedesktop.UDisks2.Block:
.
.
.
org.freedesktop.UDisks2.Filesystem:
MountPoints: /media/luvr/EFI
Size: 0
org.freedesktop.UDisks2.Partition:
.
.
.When, on the other hand, the second partition—which has no label assigned to it—is mounted, the mountpoint, as reported by the ‘udisksctl’ utility, will remain blank (again, see the “MountPoints:” line below—the value is missing):
$ /usr/bin/udisksctl info --block-device /dev/loop0p2
/org/freedesktop/UDisks2/block_devices/loop0p2:
org.freedesktop.UDisks2.Block:
.
.
.
org.freedesktop.UDisks2.Filesystem:
MountPoints:
Size: 0
org.freedesktop.UDisks2.Partition:
.
.
.This looks like a fairly small error in the code—at least for someone who can make sense of it; I’m afraid, though, that I’m not such a “someone”. ![]()
I have been getting “Network is unreachable” errors for the past few days:
# apt update
Get:1 file:/opt/linuxluvr-daedalus/linuxluvr daedalus-luvr InRelease [4,608 B]
Get:1 file:/opt/linuxluvr-daedalus/linuxluvr daedalus-luvr InRelease [4,608 B]
Get:2 [url]https://dl.google.com/linux/chrome/deb[/url] stable InRelease [1,825 B]
Hit:3 [url]https://files.eid.belgium.be/debian[/url] bookworm InRelease
Get:4 [url]https://dl.google.com/linux/chrome/deb[/url] stable/main amd64 Packages [1,215 B]
Ign:5 [url]http://deb.devuan.org/merged[/url] daedalus InRelease
Ign:6 [url]http://deb.devuan.org/merged[/url] daedalus-security InRelease
Ign:7 [url]http://deb.devuan.org/merged[/url] daedalus-updates InRelease
Err:8 [url]http://deb.devuan.org/merged[/url] daedalus Release
Cannot initiate the connection to deb.devuan.org:80 (2a0a:e5c0:10:3::6eeb). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:9e40::180). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2407:b6c0::12). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f9:2a:fa9::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2801:82:80ff:8000::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f8:140:1102:2b76:955d:b48f:bdf3). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:878:346::116). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:4ca0:4300::1:19). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2800:a8:c001::a). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:e42:102:1704:160:16:137:156). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a03:4000:28:24c::). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0d:eb00:8006::acab). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4ff:f0:dd3a::1). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2401:c080:2000:229e:4b70:fe82:36ed:f788). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2602:817:2000:401::138). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:67c:1220:8b0::93e5:b013). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2604:a880:5:1::154:0). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0a:4cc0:c0:4676:4242:4242:4242:4242). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:638:a000:1021:21::1). - connect (101: Network is unreachable)
Err:9 [url]http://deb.devuan.org/merged[/url] daedalus-security Release
Cannot initiate the connection to deb.devuan.org:80 (2a0a:e5c0:10:3::6eeb). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:9e40::180). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2407:b6c0::12). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f9:2a:fa9::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2801:82:80ff:8000::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f8:140:1102:2b76:955d:b48f:bdf3). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:878:346::116). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:4ca0:4300::1:19). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2800:a8:c001::a). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:e42:102:1704:160:16:137:156). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a03:4000:28:24c::). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0d:eb00:8006::acab). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4ff:f0:dd3a::1). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2401:c080:2000:229e:4b70:fe82:36ed:f788). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2602:817:2000:401::138). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:67c:1220:8b0::93e5:b013). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2604:a880:5:1::154:0). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0a:4cc0:c0:4676:4242:4242:4242:4242). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:638:a000:1021:21::1). - connect (101: Network is unreachable)
Err:10 [url]http://deb.devuan.org/merged[/url] daedalus-updates Release
Cannot initiate the connection to deb.devuan.org:80 (2a0a:e5c0:10:3::6eeb). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:9e40::180). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2407:b6c0::12). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f9:2a:fa9::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2801:82:80ff:8000::2). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4f8:140:1102:2b76:955d:b48f:bdf3). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:878:346::116). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:4ca0:4300::1:19). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2800:a8:c001::a). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:e42:102:1704:160:16:137:156). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a03:4000:28:24c::). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0d:eb00:8006::acab). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a01:4ff:f0:dd3a::1). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2401:c080:2000:229e:4b70:fe82:36ed:f788). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2602:817:2000:401::138). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:67c:1220:8b0::93e5:b013). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2604:a880:5:1::154:0). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2a0a:4cc0:c0:4676:4242:4242:4242:4242). - connect (101: Network is unreachable) Cannot initiate the connection to deb.devuan.org:80 (2001:638:a000:1021:21::1). - connect (101: Network is unreachable)
Reading package lists... Done
E: The repository 'http://deb.devuan.org/merged daedalus Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.devuan.org/merged daedalus-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.devuan.org/merged daedalus-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.If I subsequently retry the update a few minutes later, then everything returns to normal.
Pages: 1