k3b problem on antiX-19.5_386-base

  • This topic has 3 replies, 2 voices, and was last updated May 8-5:42 am by Len E..
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #76846
    Member
    Len E.

      After installation of k3b on antiX-19.5_386-base,
      immediately after invoking the application, an
      error message appears, “optical drive not found”.

      I found that unlike antiX-21, antiX-17.5, and
      antiX-19.3, all of which use standard debian versions
      of k3b AND xfburn which function normally, antiX-19.5
      does not.

      antiX-19.5 has an upgrade from the standard xfburn version,
      0.5.5-2, to a modified version, 0.6.2-1.0antix1.

      Does this mean that k3b requires a modified version
      also to accommodate the latest restructuring in antiX-19.5 ??

      Len E.

      #77335
      Member
      Len E.
        Helpful
        Up
        0
        ::

        As my original text has been rejected as spam, I’m attaching
        it as file K3bworkaround4.txt.

        Len E.

        Attachments:
        #77429
        Moderator
        Brian Masinick
          Helpful
          Up
          0
          ::

          Len E. “Original post”:

          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.

          --
          Brian Masinick

          #82813
          Member
          Len E.
            Helpful
            Up
            0
            ::

            An opinion: a good solution to this problem, (and one I’m absolutely
            incapable of creating) is to follow the approach used by Devuan to create
            two transitional packages:
            udev, pointing directly to eudev, and
            libudev1, pointing directly to libeudev1.

            In this manner, all package customization to eliminate systemd dependencies is
            confined to lower-level packages, enabling the retention of standard Debian 10
            packages for all user-level applications such as k3b, xfburn and xserver-xorg-
            core.

            Len E.

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.