[HOME] [DOWNLOAD] [DOCS] [NEWS] [SUPPORT] [TIPS] [ISSUES] [CONTRIBUTE] [DONATE]

Tor Browser crashing in Whonix VirtualBox since upgrade to Host Linux Kernel version 5.10.0-15

@redex
Yes, running Xorg and no, not hardened kernel.

Thank you so much for solving my problem! I tried it just now and it worked.

Well, I have tried on the host machine 3 different kernels with no luck:

  1. linux510 5.10.126-1
  2. linux515 5.15.50-1
  3. linux517 5.17.15-1

I have up-to-date Manjaro 21.3.2, latest VirtualBox 6.1.34 and latest Whonix 16.0.5.3. Do you have any tips?

cant reproduce here on debian, but as a side request can you try Whonix

  • KVM and see if it has any errors?

skincare3201 via Whonix Forum:

(Whonix is based on Kicksecure.)

Found these posts as I had same reported Tor browser crashing (and noise/artifacts prior to crashes) the other day in Virtualbox on updated to current Pop!_OS 22.04 LTS; this morning I set up qemu using Whonix for KVM on same device and said OS; all issues gone, Whonix and Tor browser acting as they should (tested through using for browsing over four hours, no problems). Hope this is useful.

1 Like

OK, Debian had a new kernel update from 5.10.0-15-amd64 to 5.10.0-16-amd64.

With the new kernel the issue still exists: Tor browser crashing and noise/artifacts prior to crashes.

Still no issues with kernel 5.10.0-14-amd64. Issue only exists with 5.10.0-15 and 5.10.0-16.

Still don’t know if the issue is caused by TOR browser, Whonix, Debian kernel or VirtualBox! I really have not got the machinery or time to test all combinations. I am starting to think that I may switch host distribution (but that is a major undertaking and I would like a guarantee that it works under the new distro before doing so).

The error is as follows:

Fontconfig warning: “/home/user/.tb/tor-browser/Browser/TorBrowser/Data/fontconfig/fonts.conf”, line 85: unknown element “blank”

###!!! [Parent][MessageChannel] Error: (msgtype=0x390142,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv

Fontconfig warning: “/home/user/.tb/tor-browser/Browser/TorBrowser/Data/fontconfig/fonts.conf”, line 85: unknown element “blank”
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
/home/user/.tb/tor-browser/Browser/start-tor-browser: line 362: 3883 Segmentation fault (core dumped) TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class “Tor Browser” -profile TorBrowser/Data/Browser/profile.default “${@}” < /dev/null
[ERROR] [torbrowser] 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

Hope this helps someone! :slight_smile:

1 Like

If a host kernel upgrade breaks something inside VirtualBox VMs such as:

  • Debian
  • Tor Browser in Debian

then these are Linux host kernel and/or VirtualBox host software issues.

Debian stable (buster at time of writing) or Kicksecure is/are the distribution(s) used by developers.

I doubt anyone will give a guarantee. See legal / licenses.

These happened with earlier versions and are therefore likely unrelated. Also most likely happening outside of Whonix. Therefore please check if this was reported upstream and report a bug if not so yet.

This is the actual issue.

If a host kernel upgrade breaks something inside VirtualBox VMs such as:

  • Debian
  • Tor Browser in Debian

then these are Linux host kernel and/or VirtualBox host software issues.

Debian stable (buster at time of writing) or Kicksecure is/are the distribution(s) used by developers.

I doubt anyone will give a guarantee. See legal / licenses.

These happened with earlier versions and are therefore likely unrelated. Also most likely happening outside of Whonix. Therefore please check if this was reported upstream and report a bug if not so yet.

This is the actual issue.

Did you read this forum thread?
The questions and answer will be the same.

This forum thread was about the host kernel issue.
Not VM kernel issue.

Are you using a Linux based host?

Primary answer is still this link:

Potentially it’s a different issue and resolved by above link.

Hopefully not.

Possibly using https://snapshot.debian.org/

https://www.kicksecure.com/wiki/Free_Support_Principle

“Sources.list.d” file is empty

It’s a a folder. Not a file.

I recommend separate questions. Could you please try to learn these skills as per Information Booster might be Available! /
https://www.kicksecure.com/wiki/Free_Support_Principle / in separate forum threads.

It’s a VirtualBox issue:

https://forums.virtualbox.org/viewtopic.php?f=7&t=106272

Kicksecure / Whonix inside VirtualBox is affected but not the root cause

A workaround will be documented probably within the hour and I’ll post again once available.

Hi, this must be a host kernel issue.
Had the same problem, google search lead me here. I’m running tails in kvm, tor browser was crashing with the latest kernels 5.18 and 5.17 on host (even older versions of tails 4.x), after downgrading to kernel version 5.15.55 (probably LTS version) on kvm host, the browser is stable again. My system is gentoo, except the kernel all the relevant versions are up-to-date (at the time of posting).

I am pretty certain this is a Linux host kernel version vs VirtualBox version issue.

This might be related:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012627

(A Linux kernel security patch was backported to the stablized Debian bullseye Linux kernel, which might be the cause for these issues.)

Workaround documented here just now:
Linux Host Kernel versus Tor Browser and other Crashes

Workaround doesn’t solve the issue for me. Both Gateway and Workstation running on 5.10.0-14.

VirtualBox DKMS on Arch.

Only whonix or so as other operating systems inside vbox?

If vbox is hopeless case for you then please use Whonix in KVM version.

Since when does this happen?

In that case it could be a different issue and Tor Browser Crash Errors applies.

Tor Browser Crash Errors was a thing long before this issue kernel issue happened.

I’ve been using Whonix since its early days, updating regularly, and it was flawless until these Tor crashes at the begining of June. As I use it through VB, I thought the solution in this thread would stop them but it’s still unstable.

In my opinion, this issue is rooted in virtualization, the same browser crash is exhibiting on tails running in kvm (see my previous post here), but when I run same tails from usb directly on hardware, tor browser is not crashing. Also, I can consistently reproduce the problem on kvm with host kernels 5.16-5.18, but on 5.15.latest its working fine. My cpu is AMD btw. Still thinking what all these here described details means and what is the common culprit. Something must have been changed in tor browser, which does not like the virtualization, maybe some compile flag, or some specific cpu version, or some unexpected combination of something.

[Imprint] [Privacy Policy] [Cookie Policy] [Terms of Use] [E-Sign Consent] [DMCA] [Contributors] [Investors] [Priority Support] [Professional Support]