Torbrowser crashes (pinebook pro)

grauzone · 23 April 2022 09:23

Since version 10.0.4 the torbrowser from this website (?) is no longer working
I would LIKE to enter the URL here, but I am not allowed to do so, sorry.

Each tab crashes, I removed google@search.mozilla.org and blockchair@search.mozilla.org from the extension list. Acdcording to the error messages these are “invalid”.
But still the torbrowser starts up, establishes a connection and then the tab crashes and crashes and …
you get the idea.
As a work-around I use tor and the proxy settings in firefox. But this is annoying for most normal websites. (captcha, access denied, …)

Do you know how to fix either the torbrowser or manjaro ARM or another source for a torbrowser for the pinebook pro ?

bogdancovaciu · 23 April 2022 09:28

You mean from here Tor Project | Download ?
Extracted it and run the binary from the extracted folder and fails?

Strit · 23 April 2022 09:29

Also, having some output generated from the crash would be helpful.

Like, launch the application from the terminal, make it crash, and post the entire output from the terminal.

grauzone · 23 April 2022 09:33

The torproject does not support the ARM architecture. So this is not the URL I download from.
I download from sourceforge.net and this directory projects/tor-browser-ports/files/
Perhaps you can then guess the URL I am not allowed to enter here.

grauzone · 23 April 2022 09:36

OK, Here we go:

$ sh start-tor-browser --verbose
console.log: "TorConnect: Init"
console.log: "TorConnect: observed profile-after-change"
console.log: "TorConnect: observing topic 'TorBootstrapStatus'"
console.log: "TorConnect: observing topic 'TorBootstrapError'"
console.log: "TorConnect: observing topic 'TorProcessExited'"
console.log: "TorConnect: observing topic 'TorLogHasWarnOrErr'"
console.log: "TorConnect: observing topic 'torsettings:ready'"
console.log: "TorSettings: observed profile-after-change"
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device has no render node (t=3.28285) [GFX1-]: glxtest: DRM device has no render node
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device has no render node (t=3.28285) |[1][GFX1-]: No GPUs detected via PCI (t=3.28301) [GFX1-]: No GPUs detected via PCI
Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
Apr 23 09:35:05.478 [notice] Tor 0.4.6.10 (git-22fd351cf582aa2b) running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.12, Liblzma N/A, Libzstd N/A and Glibc 2.35 as libc.
Apr 23 09:35:05.479 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Apr 23 09:35:05.479 [notice] Read configuration file "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc-defaults".
Apr 23 09:35:05.479 [notice] Read configuration file "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc".
Apr 23 09:35:05.482 [notice] Opening Control listener on 127.0.0.1:9151
Apr 23 09:35:05.482 [notice] Opened Control listener connection (ready) on 127.0.0.1:9151
Apr 23 09:35:05.482 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
Apr 23 09:35:05.000 [notice] Parsing GEOIP IPv4 file /home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip.
Apr 23 09:35:05.000 [notice] Parsing GEOIP IPv6 file /home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip6.
Apr 23 09:35:05.000 [notice] Bootstrapped 0% (starting): Starting
Apr 23 09:35:05.000 [notice] Starting with guard context "default"
Apr 23 09:35:05.000 [notice] Delaying directory fetches: DisableNetwork is set.
Apr 23 09:35:06.000 [notice] New control connection opened from 127.0.0.1.
console.log: "TorSettings: observed TorProcessIsReady"
console.log: "TorSettings: loadLegacy()"
Apr 23 09:35:07.000 [notice] New control connection opened from 127.0.0.1.
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: observed TorBootstrapStatus topic while in state TorConnectState.Initial"
Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
console.log: "TorConnect: will load after bootstrap => [about:tor]"
Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
Apr 23 09:35:08.000 [notice] New control connection opened from 127.0.0.1.
Apr 23 09:35:08.000 [notice] New control connection opened from 127.0.0.1.

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


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

console.warn: SearchSettings: "get: No settings file exists, new profile?" (new NotFoundError("Could not open the file at /home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Browser/profile.default/search.json.mozlz4", (void 0)))
console.log: "TorSettings: saveToPrefs()"
console.log: "TorConnect: observed torsettings:ready"
console.log: "TorConnect: beginConfigure()"
console.log: "TorConnect: transitioning state from Initial to Configuring"

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

Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
JavaScript error: resource://gre/modules/PromiseWorker.jsm, line 106: Error: Could not get children of file(/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Browser/profile.default/thumbnails) because it does not exist
console.error: "Could not load engine google@search.mozilla.org: Error: Extension is invalid"
console.error: "Could not load engine blockchair-onion@search.mozilla.org: Error: Extension is invalid"
Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "/home/norbert/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"

Darksky · 23 April 2022 12:36

While searching a while back for an issue in firefox I ran across others saying the same with that version. They had to download and revert back to an earlier version.

hobbitus · 23 April 2022 20:30

I have a similar experience with the Tor Browser

$ sh start-tor-browser --verbose
console.log: "TorSettings: loadFromPrefs()"
console.log: "TorConnect: Init"
console.log: "TorConnect: observed profile-after-change"
console.log: "TorConnect: observing topic 'TorBootstrapStatus'"
console.log: "TorConnect: observing topic 'TorBootstrapError'"
console.log: "TorConnect: observing topic 'TorProcessExited'"
console.log: "TorConnect: observing topic 'TorLogHasWarnOrErr'"
console.log: "TorConnect: observing topic 'torsettings:ready'"
console.log: "TorSettings: observed profile-after-change"
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device has no render node (t=0.727095) [GFX1-]: glxtest: DRM device has no render node
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM device has no render node (t=0.727095) |[1][GFX1-]: No GPUs detected via PCI (t=0.72725) [GFX1-]: No GPUs detected via PCI
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
Apr 23 20:08:22.455 [notice] Tor 0.4.6.10 (git-22fd351cf582aa2b) running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.12, Liblzma N/A, Libzstd N/A and Glibc 2.35 as libc.
Apr 23 20:08:22.455 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Apr 23 20:08:22.455 [notice] Read configuration file "~/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc-defaults".
Apr 23 20:08:22.455 [notice] Read configuration file "~/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc".
Apr 23 20:08:22.462 [notice] Opening Control listener on 127.0.0.1:9151
Apr 23 20:08:22.462 [notice] Opened Control listener connection (ready) on 127.0.0.1:9151
Apr 23 20:08:22.462 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
Apr 23 20:08:22.000 [notice] Parsing GEOIP IPv4 file ~/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip.
Apr 23 20:08:22.000 [notice] Parsing GEOIP IPv6 file ~/tor-browser_en-US/Browser/TorBrowser/Data/Tor/geoip6.
Apr 23 20:08:22.000 [notice] Bootstrapped 0% (starting): Starting
Apr 23 20:08:23.000 [notice] Starting with guard context "default"
Apr 23 20:08:23.000 [notice] Delaying directory fetches: DisableNetwork is set.
Apr 23 20:08:23.000 [notice] New control connection opened from 127.0.0.1.
console.log: "TorSettings: observed TorProcessIsReady"
console.log: "TorSettings: applySettings()"
console.log: "TorConnect: will load after bootstrap => [about:tor]"
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
Apr 23 20:08:24.000 [notice] New control connection opened from 127.0.0.1.
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: observed TorBootstrapStatus topic while in state TorConnectState.Initial"
Apr 23 20:08:24.000 [notice] New control connection opened from 127.0.0.1.
Apr 23 20:08:24.000 [notice] New control connection opened from 127.0.0.1.
Apr 23 20:08:24.000 [notice] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
console.log: "TorConnect: observed torsettings:ready"
console.log: "TorConnect: beginBootstrap()"
console.log: "TorConnect: transitioning state from Initial to Bootstrapping"
Apr 23 20:08:25.000 [notice] Opening Socks listener on 127.0.0.1:9150
Apr 23 20:08:25.000 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9150
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: Bootstrapping 0% complete (Starting)"
Apr 23 20:08:25.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
Apr 23 20:08:25.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay

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

Apr 23 20:08:25.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
console.error: "Could not load engine google@search.mozilla.org: Error: Extension is invalid"
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: Bootstrapping 5% complete (Connecting to a Tor relay)"
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: Bootstrapping 10% complete (Connected to a Tor relay)"
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: Bootstrapping 14% complete (Negotiating with a Tor relay)"
Apr 23 20:08:26.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
Apr 23 20:08:26.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
Apr 23 20:08:26.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
Apr 23 20:08:26.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: Bootstrapping 15% complete (Finished negotiating with a Tor relay)"
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: Bootstrapping 75% complete (Finished loading relay information)"
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: Bootstrapping 90% complete (Building circuits: Finished negotiating with a Tor relay)"
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: Bootstrapping 95% complete (Building circuits: Establishing a Tor circuit)"
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 161: TypeError: Cc[aContract] is undefined
console.error: "Could not load engine blockchair-onion@search.mozilla.org: Error: Extension is invalid"
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"
Apr 23 20:08:26.000 [notice] Bootstrapped 100% (done): Done
console.log: "TorConnect: observed TorBootstrapStatus"
console.log: "TorConnect: Bootstrapping 100% complete (Connected to the Tor network!)"
console.log: "TorConnect: bootstrapComplete()"
console.log: "TorConnect: transitioning state from Bootstrapping to Bootstrapped"
JavaScript error: , line 0: uncaught exception: Object
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 37: Use of ambiguous path in <dir> element. please add prefix="cwd" if current behavior is desired.
Fontconfig warning: "~/tor-browser_en-US/Browser/TorBrowser/Data/fontconfig/fonts.conf", line 85: unknown element "blank"

I guess that it is because the Tor Browser is based on the 91.8.0esr version of Firefox and not the 98+ which is working fine?

hobbitus · 28 May 2022 07:12

The Tor Browser works without any issue on x86-64 Manjaro as well as ARM port of Debian.

Therefore, the issue is presumably with ARM version of Manjaro.

petaramesh · 26 September 2022 17:01

Version 11.5.2 of the aarch64 Tor Browser from this port still has its tabs crashing immediately on latest Manjaro, on a Pinebook Pro.

I haven’t been able to find any solution or workaround so far.

hobbitus · 4 October 2022 14:12

It looks like the issue is due to glibc since 2.32-2 on Manjaro ARM.
glibc is required for Firefox and TorBrowser 11.5.2 is based on the ESR 91.13 version.
You may have notice that the TorBrowser will connect with the latest version of glibc, but the web browser (Firefox) tab will crash. This issue is only on Manjaro ARM, not Manjaro x64 or any other ARM Linux distro.

Anyone can easily test it by running TorBrowser 11.5.2 on Manjaro ARM image (e.g. 21.12) with glibc 2.32-2 which works fine and the web (Firefox) browser tab would not crash. Update of glibc only to the latest 2.35-5.1, nothing else, would result in the crash of the tab.

I do not anticipate that anyone will try to find out what is the difference or problem with the glibc in Manjaro ARM. Thus, you can either use another ARM Linux distro, old Manjaro ARM without glibc update, or wait for the next TorBrowser 12 which is based on the latest Firefox ESR version 102 which may resolve the issue.

Strit · 4 October 2022 14:58

If the problem is because of the glibc update, then Arch Linux ARM will also be affected by this as they have the exact same version of glibc.

And you claim that no other ARM distro has this issue. So it must be a configuration issue.

petaramesh · 4 October 2022 18:38

Could this be just a matter of recompiling the Tor Browser port with the current glibc ?
(Well I guess that compiling this on a Pinebook Pro would be somehat dreadful )

hobbitus · 4 October 2022 20:48

I didn’t try Arch Linux ARM, but I had no problem on Postmarket OS. According to the person who provides the builds it apparently works on Fedora, OpenSuSE, Debian on various ARM devices and nobody else mentioned any another issues.
I do not know if it is related to the version of glibc as such, as far as I know the source for the x64 version is exactly the same and it clearly works.
I do not know how to find out what exactly could be different or how to compare it. I did consider compiling the packages but didn’t have enough time

petaramesh · 19 October 2022 06:47

I just tested the latest 11.5.4 tor-browser ARM port and its tabs immediately crashes both on Manjaro or Armbian (which is an Ubuntu 22.04 LTS derivative).

So the issue is definitely not Manjaro-specific.

I’m currently trying to recompile it from sources on a Pi4 running Manjaro… But well it has been compiling for about 20 hours now, so it’s still in the oven

I’m actually doubtful that it will solve the issue, as I see that the build process gets done into an LXC container that pulls from Debian and Ubuntu repos, so I guess that even though I build on Manjaro, I might end up with a “compiled on Debian” set of binaries.

So I wonder if another solution wouldn’t be trying to run it inside a Debian docker image…?

Strit · 19 October 2022 09:59

The AUR package just seems to download pre-compiled tarballs and unpacking them in the filesystem.

petaramesh · 19 October 2022 10:05

Yep, but the AUR packages download 32-bit and 64-bit x86 binaries, not ARM binaires.
It can’t be used on ARM as there are no official ARM tor-browser build, only the Unofficial ports, and these are the ones that crash.

petaramesh · 19 October 2022 13:31

After some more thorough research for tor-browser precompiled binaries working on Manjaro-ARM, I found out that the lastest 10.5.10 versions from Tor Browser Ports are actually working.

Only the latest 11.x branch are crashing.

Of course using an older version of the Tor Browser might have some security implications, but at least these are working.

Just get the ARM file appropriate for your architecture (“arm64” for Pinebook Pro) and language, check the SHA256 checksum with the “sha256sums-unsigned-build.txt” and its “sha256sums-unsigned-build.txt.asc” gpg signature, uncompress the tarball in your home directory, i.e :

cd
tar -xJf Downloads/tor-browser-linux-arm64-10.5.10_fr.tar.xz

You get a tor-brower dir.

cd into it and start : ./start-tor-browser.desktop

Once happy that it (finally) works, you can create a application entry in your apps menu by just running : ./start-tor-browser.desktop --register-app

Et voilà.

Now you have a working Tor Browser, albeit not the latest one.

I emailed the ports developper about the issue in the 11.x branch, waiting for his reply.

petaramesh · 22 October 2022 10:51

After some more tests, I can furthermore confirm that the Tor-Brower 11.5.4 ARM aarch64 port :

Does not work (Tab crashes) on :

Manjaro (Pinebook Pro or Pi 4)
Armbian (Pinebook Pro)
Ubuntu 22.10 (Pi 4)

But does work on :

Rasberry Pi OS (Debian 11 Bullseye) on Raspberry Pi 3B+ or 4

So that’s not a specific Manjaro issue, and is not a specific Pinebook Pro issue either.

It’s basically crashing on all recent non-vanilla-Debian distros I have tested.

Strit · 22 October 2022 10:53

Could just be that Raspberry Pi OS enables something in a package, the rest do not?

petaramesh · 22 October 2022 10:56

AFAIK Raspberry Pi OS, except for the kernel, boot config Pi specifics etc, and desktop environment customization, only uses vanilla Debian ARM packages…

(And once installed it just identifies itself as Debian 11 Bullseye)