chromium 150 appears to be working okay on a new installation (that is, I did not previously have 149).
does 'chromium --temp-profile' work?

Very nice.
I know it's simple and maybe you want to keep it that way.
One feature request would be, after searching, to double-click an item in the list would either (1) view that page, or (2) put it in the "view page" text box.
Another feature request would be for the new window it opens to remember its last size and position - or at least make it as wide as the text that it's displaying, to prevent the word-wrap.

I use overlay-boot on several servers now.  A couple different configurations -- mainly using overlayfs, one is using a loop image file with drbd.  In fact just this last weekend I updated my installation of overlay-boot -- it was a bit outdated.  There's now a SHARE option that will bind-mount, which I've also found helpful for my use case.  In my overlay-boot configuration, the subhost's LOWER directory is a higher version of devuan than the hosting system (I created it with debootstrap --minbase and added things as needed).  For example, on a chimaera host I run daedalus subhosts; on a daedalus host, I run excalibur subhosts.  It's taken a bit of trial-and-error getting things set up, but for the most part it's been working well.
Did you have any particular question about overlay-boot?

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 did a file-based loopback device, with vfat and ext and swap partitions.  None of them have lables, but udisksctl worked properly on them all (except swap which won't mount).
The vfat partition:

udisksctl info --block-device /dev/loop0p1
/org/freedesktop/UDisks2/block_devices/loop0p1:
...
  org.freedesktop.UDisks2.Filesystem:
    MountPoints:        /media/tempo/D5A1-A960
    Size:               0
...

One of the ext4 partitions:

udisksctl info --block-device /dev/loop0p2
/org/freedesktop/UDisks2/block_devices/loop0p2:
...
  org.freedesktop.UDisks2.Filesystem:
    MountPoints:        /media/tempo/fa4de3c0-b3c5-4352-81c6-f3447ad475c6
    Size:               5626658816
...

  In all of these cases, udisksctl unmount worked.

Setting the hostname is the 3rd screen of the installer as documented here https://www.devuan.org/os/documentation … installing
You can set it to whatever you want.

Maybe if you take out the "nofail" option, you might be able to find an error message (in syslog?).

Try the netinstall from https://files.devuan.org/user/tempforever/ - It uses the grub bootloader for efi instead of syslinux, which sometimes has problems.  (Grub sometimes has its own problems too)

OK I asked because on my arm system, display doesn't come up if I plug in hdmi after the system is started up, but if it is plugged in first then it works fine.  Also I'm using one of the arm images from devuan, not debian -> devuan.  That's probably why you're missing config.txt.

Looks like it's at least attempting a 1024x600 mode but that gets rejected (not supported), I'm afraid you'll need someone more knowledgeable than myself to help you.

Strange indeed.  I have the same scanner.  On daedalus, it works fine.

$ lsusb
...
Bus 005 Device 013: ID 03f0:4205 HP, Inc ScanJet G3010
...
$ sane-find-scanner -q
...
found possible USB scanner (vendor=0x03f0 [hewlett packard], product=0x4205 [hp scanjet]) at libusb:005:013
...

But, on excalibur I got the same result as you.  So, I went through /etc/group and added my user to EVERY group there.  Nothing worked...

fcc@fccvm:~$ sane-find-scanner -q
could not open USB device 0x03f0/0x4205 at 001:003: Access denied (insufficient permissions)
could not open USB device 0x80ee/0x0021 at 001:002: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 001:001: Access denied (insufficient permissions)
fcc@fccvm:~$ groups
fcc daemon bin sys adm tty disk lp mail news uucp man proxy kmem dialout fax voice cdrom floppy tape sudo audio dip www-data backup operator list irc src shadow utmp video sasl plugdev staff games users netdev input kvm render Debian-exim ntpd messagebus _ssh plocate scanner rtkit lpadmin bluetooth ssl-cert uuidd avahi pulse pulse-access saned colord polkitd crontab nogroup

... until I added the group "root".   then it worked.

fcc@fccvm:~$ sane-find-scanner -q
could not fetch string descriptor: Operation timed out
could not fetch string descriptor: Operation timed out
found possible USB scanner (vendor=0x03f0, product=0x4205) at libusb:001:003
could not fetch string descriptor: Operation timed out
could not fetch string descriptor: Operation timed out
fcc@fccvm:~$ groups
fcc root daemon bin sys adm tty disk lp mail news uucp man proxy kmem dialout fax voice cdrom floppy tape sudo audio dip www-data backup operator list irc src shadow utmp video sasl plugdev staff games users netdev input kvm render Debian-exim ntpd messagebus _ssh plocate scanner rtkit lpadmin bluetooth ssl-cert uuidd avahi pulse pulse-access saned colord polkitd crontab nogroup

A little more info.
Daedalus (working)

$ getfacl /dev/bus/usb/005/013 
getfacl: Removing leading '/' from absolute path names
# file: dev/bus/usb/005/013
# owner: root
# group: root
user::rw-
user:tempo:rw-
group::rw-
group:scanner:rw-
mask::rw-
other::r--

Excalibur (not working)

 $ getfacl /dev/bus/usb/001/003
getfacl: Removing leading '/' from absolute path names
# file: dev/bus/usb/001/003
# owner: root
# group: root
user::rw-
group::rw-
other::r--

Just to keep y'all in the loop - freia netinstall 202605080047 *should* complete the installation successfully now.  can be found on files.devuan.org and should hit the iso mirrors shortly.

It seems to be affected by LC_ALL (like the sort command).

LC_ALL=  /usr/bin/pcmanfm

is slightly different than

LC_ALL=C /usr/bin/pcmanfm

LC_COLLATE (which you set) also affects it.

These two locale settings (LC_ALL, LC_COLLATE) also affect the output of ls
I'm not sure what all locales you have generated on your system.  You could try something like:

LC_ALL=en_GB.UTF-8 /usr/bin/pcmanfm

Thank you for the report.  These are both known issues and fixed in an upcoming 6.1.1 installer iso set.

In the meantime, to fix your already-installed sddm background, run this (as root):

  cd /usr/share/sddm/themes/debian-breeze
  sed -i -e 's,^background=,#background=,g' theme.conf
  echo "background=/usr/share/images/desktop-base/desktop-lightdm-background" >> theme.conf

(or just edit the file /usr/share/sddm/themes/debian-breeze/theme.conf to set your own background)

To manually fix plasma-discover, see this post https://dev1galaxy.org/viewtopic.php?pid=63245#p63245