Virtualbox installers stopped working

Yesterday i had no problem with the installer that was recommended, but today I span brand new clean VM which i always do when i test new setups for when things break like this. And I tested 8 methods of installing 7 of which produced errors. I had to remove all the links so it might be a bit unintelligible. If you want o read with links the pastebin is XC638Aku

Method’s 1, 2, 3 and 4 produced the same Error:
[sysmaint ~]% bash ./virtualbox-installer-clivirtualbox-installer-cli:
[ERROR]: Directory doesn’t exist: ‘/home/user’virtualbox-installer-cli:
[ERROR]: Aborting.virtualbox-installer-cli:
[NOTICE]: Executed script, function, command executed: ‘./virtualbox-installer-cli’ ‘die’ ‘exit “${1}”’virtualbox-installer-cli:
[ERROR]: Installer exited with code: ‘1’zsh: exit 1 bash ./virtualbox-installer-cli
(Same Directory doesn’t exist: ‘/home/user’ etc)

Method: 1
kicksecure-lxqt-installer-cli
kicksecure-lxqt-installer-cli --onion

Method 2
curl --tlsv1.3 --output virtualbox-installer-cli --url kicksecure. /dist-installer-clibash ./virtualbox-installer-cli

Method 3:
curl --tlsv1.3 --output kicksecure-lxqt-installer-cli --url kicksecure /dist-installer-cli
bash ./virtualbox-installer-cli --onion

Method 4:
bash ./virtualbox-installer-cli --oracle-repo

Method 5:
sudo apt update
sudo apt install --no-install-recommends virtualbox-qt
sudo adduser $(whoami) vboxusers

Producess Error:
Unsatisfied dependencies:
virtualbox-qt : Depends: virtualbox (= 7.2.2-dfsg-2) but it is not installable
Error: Unable to correct problems, you have held broken packages.
Error: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:

  1. virtualbox-qt:amd64=7.2.2-dfsg-2 is selected for install
  2. virtualbox-qt:amd64 Depends virtualbox (= 7.2.2-dfsg-2)
    but none of the choices are installable:
    [no choices]
    zsh: exit 100 sudo apt install --no-install-recommends virtualbox-qt

Method 6 :

sudo apt update && sudo apt full-upgrade

sudo apt install --no-install-recommends extrepo

sudoedit /etc/extrepo/config.yaml

  • contrib
  • non-free

sudo extrepo enable virtualbox

sudo apt update

sudo apt install virtualbox-7.2 linux-headers-$(uname -r)

Produces error: The file does not exist. And doesnt let me save the changes

Method 7:
Paste the whole text:

echo “Types: deb
URIs:
Suites: $(lsb_release -sc)
Components: contrib
Enabled: yes
Signed-By: /usr/share/keyrings/virtualbox-archive-keyring.asc” | sudo tee /etc/apt/sources.list.d/virtualbox.sources

curl --tlsv1.3 --remote-name --tlsv1.2

gpg --keyid-format long --import --import-options show-only --with-fingerprint oracle_vbox_2016.asc

Verify the fingerprint.
The most important check is confirming the key fingerprint exactly matches the output below.
Key fingerprint = B9F8 D658 297A F3EF C18D 5CDF A2F6 83C5 2980 AECF

sudo cp oracle_vbox_2016.asc /usr/share/keyrings/virtualbox-archive-keyring.asc

sudo apt update

sudo apt install virtualbox-7.2 linux-headers-$(uname -r)

Produces Error:
Get:1 trixie InRelease [4,440 B]
Err:1 trixie InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring “/usr/share/keyrings/virtualbox-archive-keyring.asc” Caused by: 0: Reading “/usr/share/keyrings/virtualbox-archive-keyring.asc”: Permission denied (os error 13) 1: Permission denied (os error 13)
Hit:2 tor+://deb.kicksecure. trixie InRelease
Hit:3 tor+://fasttrack.debian .net/debian-fasttrack trixie-fasttrack InRelease
Hit:4 tor+://fasttrack.debian. net/debian-fasttrack trixie-backports-staging InRelease
Hit:5 tor+://deb.debian. org/ debian trixie InRelease
Hit:6 tor+://deb.debian. org/debian trixie-updates InRelease
Hit:7 tor+://deb.debian .org/debian trixie-backports InRelease
Hit:8 tor+://deb.debian .org/debian-security trixie-security InRelease
Warning: OpenPGP signature verification failed: trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring “/usr/share/keyrings/virtualbox-archive-keyring.asc” Caused by: 0: Reading “/usr/share/keyrings/virtualbox-archive-keyring. asc”: Permission denied (os error 13) 1: Permission denied (os error 13)
Error: The repository ‘ trixie InRelease’ is not signed.
Notice: Updating from such a repository can’t be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
zsh: exit 100 sudo apt update
The links were removed so i can post but they ware towards debian repository

Method 8: Is the only one that works for me for now

$ sudo apt install curl wget gnupg2 lsb-release -y
$ curl -fsSL gpg --dearmor -o /etc/apt/trusted.gpg.d/vbox.gpg
$ curl -fsSL gpg --dearmor -o /etc/apt/trusted.gpg.d/oracle_vbox.gpg

$ echo “deb [arch=amd64] $(lsb_release -cs) contrib” | sudo tee /etc/apt/sources.list.d/virtualbox.list

$ sudo apt update
$ sudo apt install linux-headers-$(uname -r) dkms -y
$ sudo apt install virtualbox-7.2 -y

$ sudo usermod -aG vboxusers $USER
$ newgrp vboxusers

$ wget download.virtualbox./virtualbox/7.2.4/Oracle_VirtualBox_Extension_Pack-7.2.4.vbox-extpack

$ sudo vboxmanage extpack install Oracle_VirtualBox_Extension_Pack-7.2.4.vbox-extpack

vboxmanage --version
sudo apt remove --purge virtualbox-7.2
sudo apt autoremove
sudo apt autoremove virtualbox

Success

1 forum thread = 1 issue only please. In this case, 1 forum thread = 1 method only please. So I’ll only focus on the installer method.

For other methods such as manually adding the VirtualBox repository, using extrepo (which does the same), if still relevant, please open a separate forum thread.

Otherwise this will get too confusing.

I was able to reproduce this. It can happen when you only used sysmaint session so far. In other words, this can happen if you never started a user session yet. In result, account user has never logged in. However, the home directly of account user is only created upon its first login.

So the solution is: Boot into user session at least once. Then you can reboot into a sysmaint session and the installer should be functional.

A more helpful error message pointing that out will be added in a future release.

This is “largely” not a different method. virtualbox-installer-cli and kicksecure-lxqt-installer-cli share the very same source code. So if virtualbox-installer-cli, there is no need to try any of the other Linux installers by Kicksecure (or Whonix).

To fix:

sudo chmod o+r /usr/share/keyrings/virtualbox-archive-keyring.asc

[1]

This step was missing in the documentation. Added just now.


[1] This is due to umask.