solution partially worked for me: limit the number of virtual CPUs to 1 in Virtualbox settings for Workstation. With this crashes less often.
Also there is an another bug here when Firefox crashes and crash the xorg xserver too. It occurs on some sites that use webgl with the latest extesnions like shaders or so. Seems the problem is in video adapter driver which doesn’t implement these extensions. The last bug occurs both on old real hardware adapters too
My setup: Linux OS (jammy jellyfish) - Oracle VM - Whonix (where i use tor browser) Linux version: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy I have all the lastest software version for the software that I’m using. (I’ve checked)
The problem - My tor browser started crashing displaying a exit node zero error:
“ERROR: Tor Browser ended with non-zero (error) exit code! Tor Browser was started with: /home/user/.tb/tor-browser/Browser/start-tor-browser --verbose --allow-remote . Tor Browser exited with code: 139”
I’ve searched for a while and the only answer i’ve found is to degrade my kernel version but since security is my focus this wouldn’t make any sense:
“ This issue happens after a Linux host kernel upgrade. Common symptoms of this issue are: • APT showing hashsum mismatch. • other kernel issues • Tor Browser crashes
It is happening because VirtualBox does not support yet that kernel version. [5] This wiki chapter was written on 19 July 2022 and might be improved later perhaps with better options as they become available. The only known workaround for now is to downgrade to Debian Linux kernel version 5.10.0-14. Obviously this is a bad solution. “
Can you help me find any other alternative? Or at least let me know if I should wait for an upgrade? Thanks in advance.
Note: after upgrading the VirtualBox host version, this can cause issues with the guest VMs such as broken VM size adjustment (full screen) [2] unless the VirtualBox guest additions are also upgraded inside your virtual machine (which is not covered in these instructions).
Can you give me a more simplified guide to do the correct instalation? or put here the link to access the original guide? Given that this forum interface is kinda weird to understand at first…
The already as simple as I could get it after a few hours of work version is this:
It doesn’t get much simpler anytime soon.
Cause of issue: Software not developed by third parties (meaning not Whonix) (i.e. Linux kernel; VirtualBox) got updated and is now incompatible. And your Linux distribution Ubuntu not providing an up to date VirtualBox version either.
Abstract task: get a newer version of VirtualBox.
The issue is unspecific to Whonix.
This means you don’t need necessarily depend on instructions from the Whonix website. These are supplementary. If you find the supplemental instructions on the Whonix website useful, that’s great. These always maximize security as far as that’s reasonably possible (not asking for highly unlikely stuff such as downloading the VirtualBox source code and auditing it by yourself).
If you find instructions elsewhere such as on the VirtualBox website, you can use them. Maybe the instructions can be as simple as a one liner but it would be less secure. So making the instructions simpler while not compromising on security is very hard.
But even if extrepo, it would still be quite a few commands to copy/paste.
The only way to make it really easy would be to provide first class integration of VirtualBox into a Linux distribution. That might happen under the Kicksecure project and/or Whonix-Host. But that will take a long time until it’s there and obviously asking to change the host linux distribution is also a big ask.
This is now easy to fix at least for Debian users since the version of VirtualBox available from Debian fasttrack does not have this issue. In other words, this is fixed in recent VirtualBox versions.