Tor Browser segfault in whonix-ws qubes-template-whonix-ws-4.0.0-201801270342

[adrelanos]

Qubes OS version:

R3.2

Affected TemplateVMs:

whonix-ws 14 from #3484 (comment)

---

Steps to reproduce the behavior:

user@host:~/.tb/tor-browser$ ./start-tor-browser.desktop --debug
Launching './Browser/start-tor-browser --detach --debug'...
./Browser/start-tor-browser: line 372: 15433 Segmentation fault      TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class "Tor Browser" -profile TorBrowser/Data/Browser/profile.default "${@}" < /dev/null
user@host:~/.tb/tor-browser$ ./start-tor-browser.desktop --debug --log
Launching './Browser/start-tor-browser --detach --debug --log'...
Logging Tor Browser debug information to tor-browser.log
user@host:~/.tb/tor-browser$ cat tor-browser.log 
user@host:~/.tb/tor-browser$ 
user@host:~/.tb/tor-browser$ 
user@host:~/.tb/tor-browser$ 
user@host:~/.tb/tor-browser$ 
user@host:~/.tb/tor-browser$ ./Browser/firefox --class "Tor Browser" -profile TorBrowser/Data/Browser/profile.default
Segmentation fault

Expected behavior:

Tor Browser working.

Actual behavior:

Segfaulting.

General notes:

• This is a blocking bug for the release of Qubes-Whonix 14.
• Not happening with Non-Qubes-Whonix 14.
• Therefore something that Qubes is doing is triggering this issue.
• Dunno if a Qubes bug and/or Tor Browser bug.
• Happening with both, Tor Browser 7.5 and 8.0a1.
• Happening with the pre-installed Tor Browser as well as re-installed after boot Tor Browser.

Any idea?

[adrelanos]

• It never happened to me in Whonix 13 -> Whonix 14 upgraded builds. So something that happens during the qubes-builder building process, some change there may be triggering this.

[adrelanos]

• It never happened to me in Whonix 13 -> Whonix 14 upgraded builds. So something that happens during the qubes-builder building process, some change there may be triggering this.

[adrelanos]

unset XDG_CONFIG_DIRS

torbrowser

Does the trick. So I guess a too long string length of the value of the XDG_CONFIG_DIRS environment variable is the trigger.

[adrelanos]

unset XDG_CONFIG_DIRS

torbrowser

Does the trick. So I guess a too long string length of the value of the XDG_CONFIG_DIRS environment variable is the trigger.

[adrelanos]

We had a similar issue previously which was related to jemalloc:

• https://phabricator.whonix.org/T651
• https://trac.torproject.org/projects/tor/ticket/21804

[adrelanos]

We had a similar issue previously which was related to jemalloc:

• https://phabricator.whonix.org/T651
• https://trac.torproject.org/projects/tor/ticket/21804

[adrelanos]

Tor Browser refuses to start / XDG_CONFIG_DIRS environment variable segfaults Tor Browser
https://trac.torproject.org/projects/tor/ticket/25305

[adrelanos]

Tor Browser refuses to start / XDG_CONFIG_DIRS environment variable segfaults Tor Browser
https://trac.torproject.org/projects/tor/ticket/25305

[adrelanos]

Will also be fixed in updates (soon) as well as next build.

Whonix/tb-starter@cc61baf

[adrelanos]

Will also be fixed in updates (soon) as well as next build.

Whonix/tb-starter@cc61baf