It's the nature of Debian however that anything and everything may be packaged while someone is willing to package it and then maintain it.

It is also the nature of Debian that, with very few exceptions, no new versions of "upstream" software are introduced after the "freeze". Note: I'm not defending this model, just explaining the basics of how it works.

Around 15 - 20 years ago, this manifested itself most publicly, in the multitudes of "I want the latest firefox" rant threads. This was where users who were running Debian stable, e.g. 1.5 years into a release, were still at easily a 2 year old firefox release (rebranded to "iceweasel" due to licence and trademark issues).

The obvious answer was to just go to mozilla and download it, but many still complained and felt entitled to the latest version. Unlike the example in this thread, Iceweasel did receive backported security patches, but functionality wise could be 2+ years behind.

This situation is similar - few will be happy with the packaged version, so it is indeed pointless.

on this laptop using devuan freia or maybe unstable

with kde plasma x11.

normally receive fairly daily upgrades , however tody chose to upgrade via "discover" which alwasys remind up impending update/upgrades but then does not finish seem to finish them mostly due to errors. there were lots of packages propeosed , maybe 600+.

since then have now this error here like

source ~/.bashrc 
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.

locate libgtk3-nocsd.so.0
/usr/lib/i386-linux-gnu/libgtk3-nocsd.so.0
/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0

but when i look inside this folder "/usr/lib/x86_64-linux-gnu" it seems the file object

is not present?

sorry if i made anerror.

Anyhow, i have just installed a Debian 13 (trixie) system, to test the ‘apfs-dkms’ package and to try and reproduce the problem under Debian proper.

Result: Under Debian 13, mounting and unmounting an APFS partition on a disk dump file using the ‘udisksctl’ utility works fine; I presume, then, that under Devuan 6 (excalibur), it will also work (since that is based on Debian 13). I therefore consider the problem solved.

P.S.: I don't really like Debian 13 (trixie), since it won’t let me remove GRUB without installing ‘systemd-boot’. Who came up with that idea? I want neither GRUB, nor systemd-boot, since I don’t want Debian (or any other system, for that matter) to mess with my EFI System Partition; I'm prepared to clean up the ESP right after a system (e.g., Devuan) insists on setting up GRUB upon initial install, but after that, it should leave my ESP alone; ‘systemd-boot’ in particular is pretty aggressive in that regard, in that it wipes away my /boot/efi/EFI/BOOT/BOOTX64.EFI (as provided by Limine) and replaces it with its own version. YUCK!

I’ll simply dump Debian and replace it with Devuan 6; I already installed it once on an Apple MacBook Air, and it appears to be well-behaved.

UPDATE: I have just tested the ‘udisksctl’ utility to mount and unmount an APFS partition under Devuan 6 (excalibur) and, as expected, it works fine. Problem definitely solved!

UPDATE—QUICK (admittedly, off-topic) NOTE: Even though, by default, Debian 13 (trixie) wouldn’t let me remove GRUB without installing ‘systemd-boot’, I eventually succeeded in avoiding having either boot loader on the system. All I had to do, was to purge the ‘shim-signed’ package first:

# apt purge shim-signed
The following packages were automatically installed and are no longer required:
  mokutil  shim-helpers-amd64-signed  shim-signed-common  shim-unsigned
Use 'apt autoremove' to remove them.

REMOVING:
  shim-signed*

Summary:
  Upgrading: 0, Installing: 0, Removing: 1, Not Upgrading: 0
  Freed space: 1,068 kB

Continue? [Y/n] Y
(Reading database ... 110520 files and directories currently installed.)
Removing shim-signed:amd64 (1.51~1+deb13u1+16.1-2~deb13u1) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.
No DKMS packages installed: not changing Secure Boot validation state.
(Reading database ... 110516 files and directories currently installed.)
Purging configuration files for shim-signed:amd64 (1.51~1+deb13u1+16.1-2~deb13u1) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.
No DKMS packages installed: not changing Secure Boot validation state.

(I have no use for ‘shim-signed’, since I have “Secure” Restricted Boot disabled.)

I then also ran the auto-removal step that the output of the above command suggested:

# apt --purge autoremove
REMOVING:
  mokutil*  shim-helpers-amd64-signed*  shim-signed-common*  shim-unsigned*

Summary:
  Upgrading: 0, Installing: 0, Removing: 4, Not Upgrading: 0
  Freed space: 3,190 kB

Continue? [Y/n] Y
(Reading database ... 110516 files and directories currently installed.)
Removing shim-signed-common (1.51~1+deb13u1+16.1-2~deb13u1) ...
Removing mokutil (0.7.2-1) ...
Removing shim-helpers-amd64-signed (1+16.1+2~deb13u1) ...
Removing shim-unsigned:amd64 (16.1-2~deb13u1) ...
Processing triggers for man-db (2.13.1-1) ...
(Reading database ... 110490 files and directories currently installed.)
Purging configuration files for shim-signed-common (1.51~1+deb13u1+16.1-2~deb13u1) ...
Purging configuration files for shim-helpers-amd64-signed (1+16.1+2~deb13u1) ...

I could subsequently remove GRUB:

# apt purge --allow-remove-essential 'grub*'
.
.
.
The following packages were automatically installed and are no longer required:
  efibootmgr  libefiboot1t64  libefivar1t64
Use 'apt autoremove' to remove them.

REMOVING:
  grub-common*  grub-efi-amd64*  grub-efi-amd64-bin*  grub-efi-amd64-signed*  grub-efi-amd64-unsigned*  grub2-common*  os-prober*

WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  grub-efi-amd64-signed  grub-common (due to grub-efi-amd64-signed)

Summary:
  Upgrading: 0, Installing: 0, Removing: 7, Not Upgrading: 0
  Freed space: 42.6 MB

Continue? [Y/n] Y
(Reading database ... 110490 files and directories currently installed.)
Removing os-prober (1.83) ...
dpkg: warning: while removing os-prober, directory '/var/lib/os-prober' not empty so not removed
Removing grub-efi-amd64 (2.12-9+deb13u2) ...
Removing grub2-common (2.12-9+deb13u2) ...
Removing grub-efi-amd64-bin (2.12-9+deb13u2) ...
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: this is a protected package; it should not be removed
Removing grub-efi-amd64-signed (1+2.12+9+deb13u2) ...
Removing grub-efi-amd64-unsigned (2.12-9+deb13u2) ...
Removing grub-common (2.12-9+deb13u2) ...
Processing triggers for man-db (2.13.1-1) ...
(Reading database ... 109977 files and directories currently installed.)
Purging configuration files for grub2-common (2.12-9+deb13u2) ...
Purging configuration files for grub-common (2.12-9+deb13u2) ...
dpkg: warning: while removing grub-common, directory '/var/lib/grub/ucf' not empty so not removed
Purging configuration files for grub-efi-amd64 (2.12-9+deb13u2) ...
Purging configuration files for grub-efi-amd64-bin (2.12-9+deb13u2) ...

Afterwards, I did a bit of cleanup:

• Reviewed the warnings, i.e., checked and deleted directories ‘/var/lib/os-prober’ and ‘/var/lib/grub/ucf’ (after which  ‘/var/lib/grub’ could also be deleted);

• Marked ‘efibootmgr’ as manually installed—after which no packages remained to be auto-removed;

• Ran ‘efibootmgr’ to clean up the EFI Boot Menu;

• Cleaned up the ESP (“EFI System Partition”), i.e., deleted its ‘debian’ subdirectory;

• Cleaned up the  ‘/boot’ directory, i.e., deleted its ‘grub’ subdirectory.

Done!

But then I could never get a handle on James Joyce either . . . LOL!

;lol:

Okay now that's funny!