Note:   the workaround described herein is NOT a recommended
            solution.    
It is provided as a clarification of the nature of the problem in the hope of eliciting a proper, rigorous solution for antiX-19.5.

******************************************************************
A method to get k3b working on antiX-19.4+

 1)  Install antiX-19.4 full version.
 2)  Edit the /etc/apt/sources.d/buster-backports.list file, comment out the repo 
      reference.
 3)  Start up synaptic   -   DO NOT reload the package lists.
 4)  Search for elogind - the search should bring up 5 packages:
	-elogind
	-libpam-elogind
	-libelogind0
	-libpolkit-gobject-1-0
	-libpolkit-gobject-elogind0
       Lock all 5 packages
  5)  Search for iso-snapshot-antix, and synaptic itself, lock both packages.
  6)  Go to a terminal command line,  sudo apt-mark hold  the 7 packages just
        mentioned.
  7)  Download the standard Debian Buster packages, libudisks2-0 and udisks2.
  8)  Reboot
  9)  Start up synaptic  -  it should show that the package lists have been updated.
        If they are not,  from a terminal command line, sudo apt-get update.
 10)  From a terminal command line, in the directory containing the downloaded
	Buster packages:  sudo apt install ./libudisks2-0*.deb and 
	sudo apt install ./udisks2*.deb.       sudo apt-mark hold both packages as well.
  11)  From synaptic,  lock the libudisks2-0 and udisks2  packages and install k3b.
	(k3b installation involves about 124 packages.)
  12)  From a terminal command line,  sudo apt-get upgrade.
	(about 195 packages are upgraded; say yes to the 2 script changes, for fluxbox
	 init, and slim .conf file).
*********************************************************************
Len E.