I tried looking into this myself but I couldn’t really find much about this error. The only solutions I could find didn’t work for me. The first one was to use mokutil but at the point where I was supposed to run sudo mokutil --import MOK.der it gives me the error message “Failed to get file status, MOK.der” even though I did everything it told me to do. The other one was to disable secure boot and then run sudo '/sbin/vboxconfig' but even though it looked like it worked, I’m still getting the error message. I have re-enabled secure boot, so you don’t have to worry about that.

Is there something else I can try or does VirtualBox not work in Linux Mint for some reason?

  • Noble Shift@lemmy.world
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    1 year ago

    Reboot the machine

    sudo apt remove virtualbox-dkms

    sudo apt-get install make gcc build-essential linux-headers-uname -r dkms

    sudo apt install virtualbox-dkms

    Reboot the machine

    Test

    • vortexal@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      That doesn’t work for me as they give me error messages:

      j@j-HP-Notebook:~$ sudo apt remove virtualbox-dkms
      [sudo] password for j:  
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      Package 'virtualbox-dkms' is not installed, so not removed
      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      j@j-HP-Notebook:~$ sudo apt-get install make gcc build-essential linux-headers-'uname -r' dkms
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      E: Unable to locate package linux-headers-uname -r
      j@j-HP-Notebook:~$ sudo apt install virtualbox-dkms
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      The following packages were automatically installed and are no longer required:
        libqt5help5 libqt5sql5 libqt5sql5-sqlite libqt5xml5 libsdl-ttf2.0-0
      Use 'sudo apt autoremove' to remove them.
      The following additional packages will be installed:
        libgsoap-2.8.117 liblzf1 libvncserver1 virtualbox virtualbox-qt
      Suggested packages:
        vde2 virtualbox-guest-additions-iso
      The following packages will be REMOVED:
        virtualbox-7.0
      The following NEW packages will be installed:
        libgsoap-2.8.117 liblzf1 libvncserver1 virtualbox virtualbox-dkms virtualbox-qt
      0 upgraded, 6 newly installed, 1 to remove and 0 not upgraded.
      Need to get 0 B/46.5 MB of archives.
      After this operation, 43.0 MB disk space will be freed.
      Do you want to continue? [Y/n] y
      debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
      (Reading database ... 642834 files and directories currently installed.)
      Removing virtualbox-7.0 (7.0.12-159484~Ubuntu~jammy) ...
      debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
      dpkg: error processing package virtualbox-7.0 (--remove):
       installed virtualbox-7.0 package pre-removal script subprocess returned error exit status 1
      dpkg: too many errors, stopping
      vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.
      
      There were problems setting up VirtualBox.  To re-start the set-up process, run
        /sbin/vboxconfig
      as root.  If your system is using EFI Secure Boot you may need to sign the
      kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
      them. Please see your Linux system's documentation for more information.
      Errors were encountered while processing:
       virtualbox-7.0
      Processing was halted because there were too many errors.
      E: Sub-process /usr/bin/dpkg returned an error code (1)
      
      • kuneho@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        edit-2
        1 year ago

        I guess the “uname -r” part should be $(uname -r) but this isn’t the problem with vbox IMO

        • vortexal@lemmy.mlOP
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          I’m not sure what you mean but it doesn’t matter because VirtualBox still isn’t working and I’ve decided to uninstall it and try some alternatives that people have mentioned.