Go to Debian an bitch at them ...

No, running the usrmerge installation will become mandatory with Debian 13/Devuan 6. There is NO way to avoid this. Lots of fighting and bitching, but no help, its a Debian project decision, and they are pulling all roots for not merging now during development.

Running with Daedalus on my workstation, I have set up two VMs with Excalibur based on Daedalus cli installations about 6 months ago. My first step before changing the sources to Excalibur was to run usrmerge as it is recommended now in the documentation. And both of them work well.

You may have more luck when installing

# apt install libpolkit-gobject-elogind-1-0 libpolkit-backend-elogind-1-0 

This should remove the consolekit packages and install elogind stuff instead. And that should work.

Well, if you want a stable system with minimum hasle stay with Daedalus.

If you are ready for the unexpected, try Excalibur or Testing, and for the often broken, try Ceres or Unstable. Freshly updated/developed packages first land in Unstable, when they have sort of proven to generally work, they may be forwarded to Testing.

Testing some day becomes Stable, but currently this is about 2 years to go.

You only should use Testing if you are ready to accept uneven ground and if you are willing to contribute to this phase, or if you have a good reason to do so, i.e. you have so new hardware that its supported in Testing only. Something for the experienced user. And Unstable will be even rougher.

Just my two cents ...

I guess you are on amd64, a 64-bit system. Your application is a 32 bit application that requires a 32 bit library. You will need to enable i386 as architecture, if you haven't done so far, and then to install the 32 bit version of libcrypt1. Same procedure as for wine32.

# dpkg --add-architecture i386
# apt update
# apt upgrade
# dpkg -print-foreign-architectures
# apt policy libcrypt1

I am on Firefox 115.9.1 ESR on Daedalus too, and I can't complain about graphics or drawing errors. But I am not on github or substack.

Well, your OS is two releases back. Maybe your issues are related to some outdated libraries, don't know.

In any case you could update from Beowulf to Chimaera and in a second step from Chimaera to Daedalus. There is no reason why it is impossible. I have done as well upgrades as new installations on my end.

Anyhow, read the release notes and the upgrade instructions, make sure your Beowulf is up to date before starting the upgrade, and disable/remove all non-Devuan repos before you start the upgrade. On the top of this page is a link to Devuan.org. There you can track down the release notes and upgrade instructions.

libmcrypt is not libhcrypto!

Affected is Testing, not Stable or older.

Try to install additionally gvfs-backend and gvfs-fuse. You may need to remove jmtpfs.

This should enable that you get you phone shown on the desktop. Worked for me.

At least with the VirtualBox you have to set the mode when configuring the VM. Per default its a legacy VM, only when efi is ticked you have to use efi mechanisms.

To the OP: your setup is quite unusual in my eyes. I always would try it with one encrypted partition.

But your setup should work too. Make sure you have selected /dev/mapper/sda3_crypt, ext4 as file system (or something that is supported), and / as mount point.

Getting these things sorted takes a while. At first I collected lots of web pages and how-to's, and made some sort of notes, and it took several installations to become more or less comfortable with the process without needing notes. Its pretty complex.

The question is what do you really want to achieve? The documentation on the Devuan web page uses the guided partitioning, does possibly not help in this case.
I can describe what I do on my PCs. /home is encrypted but always on its own device and set up after the system installation.

Partitioning beforehand with a gparted life stick:
p1 = ESP 512 MiB VFAT/FAT32 on an EFI system, omitted on legacy with MBR/MSDOS partitioning scheme. It gets a bit complicated when GPT is used.
p2 = /boot 2048 MiB ext4 unencrypted.
p3 = large ext4 volume for encryption and LVM inside, set up in the installer by manual partitioning.

In the installer proceed until partitioning and select manual.
Assign p1 to be used as ESP if applicable.
p2: use as ext4, assign /boot, format. Assign names if you want.
p3: use as Volume for Encryption. Exit and go to "Configure encrypted volumes". Go through this process and exit.

Now you should also have a device called something like /dev/mapper/p3_crypt with ext4 file system. Now you set that into "Physical volume for LVM" instead of ext4. Exit.

Call the "Logical Volume Manager". You are asked to provide a name for the Logical Volume group at first. When that is setup you can define Logical volumes, e.g. 1_root, 2_swap as I do, and 3_home if you like. You will be asked for a size definition. You may use MB, % ... . Exit the "Logical Volume Manager" when you are done.
Now you should find /dev/mapper/1_root .... in the display. Select these devices one by one and assign file system and the mount point. Only when this point is done you can leave the partitioning menu and start the installation.

Topic 8 in https://www.devuan.org/os/documentation … encryption might give some insight how the result about should look alike.