[SOLVED]: Failed antiX-22 on HD can’t run VeraCrypt – start over?

Forum Forums Official Releases antiX-21/22 “Grup Yorum” [SOLVED]: Failed antiX-22 on HD can’t run VeraCrypt – start over?

  • This topic has 7 replies, 4 voices, and was last updated Apr 5-4:35 am by scruffyeagle.
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #94293
    Member
    scruffyeagle

      I tried to set up an entirely new partition containing antiX-22. I don’t know what I did wrong, but it flopped miserably. I’ve chosen zzz-Icewm desktop. But, this problem extends into other desktops too.

      Setting up VeraCrypt seemed to proceed normally – until I tried to actually run the program. I set up a launcher on the desktop, as I normally do – but, clicking on that launcher doesn’t run the program. Instead, it creates a file on my desktop, with a name that’s mainly non-displayable characters.

      I’m not sure if I should simply try to start over, or try to fix this installation. I was thinking that perhaps I should try to install VeraCrypt onto the antiX-22 Live flashdrive, and then perform the HD install cloning the flashdrive’s setup?

      I’m going to try to attach 3 .jpg’s to display what’s going on. One of them simply shows the permissions for VeraCrypt. The other 2 are to show what I’m seeing with the undisplayable file name.

      Here’s the output of inxi -Fxxxrz:
      ————————————-

      $ inxi -Fxxxrz
      System:
      Kernel: 4.9.0-326-antix.1-486-smp arch: i686 bits: 32 compiler: gcc
      v: 10.2.1 Desktop: IceWM v: 3.0.1 dm: slimski v: 1.5.0
      Distro: antiX-22_386-full Grup Yorum 18 October 2022
      base: Debian GNU/Linux 11 (bullseye)
      Machine:
      Type: Portable System: Dell product: Latitude E6400 v: N/A
      serial: <superuser required> Chassis: type: 8 serial: <superuser required>
      Mobo: Dell model: 0U692R serial: <superuser required> BIOS: Dell v: A34
      date: 06/04/2013
      Battery:
      ID-1: BAT0 charge: 76.4 Wh (102.0%) condition: 74.9/76.4 Wh (98.1%)
      volts: 12.1 min: 11.1 model: Panasonic DELL FU44196 type: Li-ion
      serial: <filter> status: full
      CPU:
      Info: dual core model: Intel Core2 Duo P8600 bits: 32 type: MCP
      smt: <unsupported> arch: Penryn Yorkfield rev: A cache: L1: 128 KiB
      L2: 3 MiB
      Speed (MHz): avg: 1200 high: 1600 min/max: 800/2401 boost: enabled cores:
      1: 800 2: 1600 bogomips: 9576
      Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx
      Graphics:
      Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell
      driver: i915 v: kernel arch: Gen5 ports: active: LVDS-1
      empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, VGA-1 bus-ID: 00:02.0
      chip-ID: 8086:2a42 class-ID: 0300
      Display: server: X.Org v: 1.20.11 driver: X: loaded: modesetting
      unloaded: fbdev,vesa gpu: i915 display-ID: :0.0 screens: 1
      Screen-1: 0 s-res: 1280×800 s-dpi: 96 s-size: 338x211mm (13.31×8.31″)
      s-diag: 398mm (15.69″)
      Monitor-1: LVDS-1 model: Seiko Epson 0x5441 res: 1280×800 hz: 60 dpi: 107
      size: 303x190mm (11.93×7.48″) diag: 358mm (14.1″) modes: 1280×800
      OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express (CTG)
      v: 2.1 Mesa 20.3.5 direct render: Yes
      Audio:
      Device-1: Intel 82801I HD Audio vendor: Dell driver: snd_hda_intel
      v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e class-ID: 0403
      Sound Server-1: ALSA v: k4.9.0-326-antix.1-486-smp running: yes
      Network:
      Device-1: Intel 82567LM Gigabit Network vendor: Dell driver: e1000e
      v: 3.2.6-k port: efe0 bus-ID: 00:19.0 chip-ID: 8086:10f5 class-ID: 0200
      IF: eth0 state: down mac: <filter>
      Device-2: Intel WiFi Link 5100 driver: iwlwifi v: kernel bus-ID: 0c:00.0
      chip-ID: 8086:4232 class-ID: 0280
      IF: wlan0 state: down mac: <filter>
      RAID:
      Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
      v: 3.0 port: 6ea0 bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A
      class-ID: 0104
      Drives:
      Local Storage: total: 232.89 GiB used: 3.99 GiB (1.7%)
      ID-1: /dev/sda vendor: Toshiba model: MK2561GSYN size: 232.89 GiB
      speed: 3.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 0C scheme: MBR
      Partition:
      ID-1: / size: 28.67 GiB used: 3.99 GiB (13.9%) fs: ext4 dev: /dev/sda6
      Swap:
      ID-1: swap-1 type: partition size: 9.77 GiB used: 0 KiB (0.0%) priority: -1
      dev: /dev/sda3
      Sensors:
      System Temperatures: cpu: 44.0 C mobo: N/A sodimm: SODIMM C
      Fan Speeds (RPM): cpu: 0
      Repos:
      Packages: apt: 1577
      Active apt repos in: /etc/apt/sources.list.d/antix.list
      1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/bullseye bullseye main nosystemd nonfree
      Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list
      1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
      Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
      1: deb http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free
      Active apt repos in: /etc/apt/sources.list.d/debian.list
      1: deb http://ftp.us.debian.org/debian/ bullseye main contrib non-free
      2: deb http://security.debian.org/ bullseye-security main contrib non-free
      No active apt repos in: /etc/apt/sources.list.d/various.list
      Info:
      Processes: 151 Uptime: 9m wakeups: 3 Memory: 3.41 GiB
      used: 277.8 MiB (8.0%) Init: SysVinit v: 2.96 runlevel: 5 default: 5
      Compilers: gcc: 10.2.1 alt: 10 Shell: Bash v: 5.1.4 running-in: roxterm
      inxi: 3.3.19
      spirit@antix22:~
      $

      • This topic was modified 1 month ago by Brian Masinick. Reason: Solved
      #94302
      Member
      PPC
        Helpful
        Up
        0
        ::

        Because I do like security, I tested VeraCrypt, on my antiX 21, 64 bits.
        It installed fine, and worked flawlessly.
        I created a tutorial for it, over at https://www.antixforum.com/forums/topic/tip-using-encryption-with-veracrypt/#post-94300
        Please check it that helps you, installing and using V.C.

        P.

        #94467
        Member
        scruffyeagle
          Helpful
          Up
          0
          ::

          Because I do like security, I tested VeraCrypt, on my antiX 21, 64 bits.
          It installed fine, and worked flawlessly.
          I created a tutorial for it, over at https://www.antixforum.com/forums/topic/tip-using-encryption-with-veracrypt/#post-94300
          Please check it that helps you, installing and using V.C.

          P.

          Thanks, PPC!
          That’s different than what I’ve done in the past, and did w/ a22 this time. What I’ve always done, is dl’ the generic VC file, extract from that, and then install what was extracted. In this case, the file I used was veracrypt-1.25.9-setup.tar.bz2. I’ve never used the .deb file, or used click-and-drag. But, I’ll take what you wrote as being instructions, and follow the instructions.

          #94469
          Member
          scruffyeagle
            Helpful
            Up
            0
            ::

            Because I do like security, I tested VeraCrypt, on my antiX 21, 64 bits.
            It installed fine, and worked flawlessly.
            I created a tutorial for it, over at https://www.antixforum.com/forums/topic/tip-using-encryption-with-veracrypt/#post-94300
            Please check it that helps you, installing and using V.C.

            P.

            I tried to follow directions, but wasn’t able to.
            The file manager didn’t allow me to click-and-drag. Instead, the click-and-drag maneuver created a selection rectangle on the screen.

            My solution was to type in the filename manually.
            I tried it twice. The first time, I used the full path.
            The second time, I made sure I was in the directory containing the .deb file, and simply named the file to be installed.
            Both efforts flopped.

            I took a screenshot, to show what happened:

            #94481
            Member
            olsztyn
              Helpful
              Up
              0
              ::

              From what I see in your terminal you need to prefix the file name with ‘./’. So it should be ./veracrypt…

              Live antiX Boot Options (Previously posted by Xecure):
              https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

              #94488
              Member
              PPC
                Helpful
                Up
                1
                ::

                My solution was to type in the filename manually.

                And you managed to do it correctly – entering the full path to the .deb (the drag and drop suggestion is just to avoid you the trouble of typing a long command).

                When you tried to run the command that points to the full path of the deb file you didn’t make any mistake. the OS tried to install the file but was unable to install some dependencies. Assuming that you did grab the correct .deb file for your antiX version AND that you are connected to the network, my best guess is that you never performed any update in that system. It’s always advisable to do so before trying to install anything, so the latest version of any needed dependecy does get installed. So, befor running the command again, try this (and enter your password if asked to):

                sudo apt update

                it should update the database of all Debian packages available in the repos, allowing you to correctly install VC.

                Note1: your inability to drag and drop from the File Manager was probably due to you using Rox-filer as FM. Try doing the same in ZZZfm- it’s more intuitive, to most users.

                Note2: also if you are trying to drag and drop using a touch-pad, you have to double tap the thing you want to drag, move to where you want to drop it and only then lift your finger from the touch-pad.

                Note3: while in the same folder as the file you want to use, like @olsztyn said, to use a file that’s inside the current folder, its name has to be preceded by “./” (it’s a Linux convention- this means “I’m talking about the file with this name, in this current folder”). Otherwise the OS probably tries to run a file with that name that’s in your Path, it finds nothing, because there’s no such file in your path and then reports the error you got. Also: to refer to a file that is in your home folder, you can simply use the prefix “~/” (it’s the same as typing /home/[user_name]/ before the name of the file. Do not use spaces between ./ or ~/ and the file name, it’s all part of the place where the file is, on single “word” (and in case the file has spaces, it has to be inside simple quotation marks, so the OS know that even having spaces, it’s still the same file name, not another command).

                When I migrated from Windows, I had to learn all this the hard way (by trial and error and by searching on-line), so I’m saving you that trouble. Most of that info is in my “Newbie Guide”, in the sticky posts – please, take a read, it will save you some pain, in the future- I tried to make it as easy to read as possible, and also as informative as possible. I’ll probably include a section about using the terminal on it…

                P.

                • This reply was modified 5 months, 1 week ago by PPC.
                • This reply was modified 5 months, 1 week ago by PPC.
                #94490
                Moderator
                caprea
                  Helpful
                  Up
                  0
                  ::

                  Is the flashdrive updated? The unmet depencies are avalaible packages on antiX22, if it is updated.
                  Uups, PPC wrote it already.

                  • This reply was modified 5 months, 1 week ago by caprea.
                  #104085
                  Member
                  scruffyeagle
                    Helpful
                    Up
                    0
                    ::

                    This thread should be marked “solved”, because I found the solution.

                    * Extract the tarball into a convenient place.
                    * Verify that the file to be installed is marked executable.
                    * Open a terminal as ROOT, into the expanded directory.
                    (Or, open a terminal into the directory, and use “su” to become root.)
                    * Type the filename as a command, using the “./”prefix.
                    * Select to install.
                    * Press Enter repeatedly, to read the license.
                    * Agree to be bound by the license (“y”).
                    * Watch it finish installing.

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