[HOME] [DOWNLOAD] [DOCS] [NEWS] [SUPPORT] [TIPS] [ISSUES] [Priority Support]

Whonix 14, fresh install. Browser Seg Faults


#1
user@host:~/.tb/tor-browser/Browser$ ./start-tor-browser --debug                                                                                                                                                                                                                
./start-tor-browser: line 372:  7578 Segmentation fault      TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class "Tor Browser" -profile TorBrowser/Data/Browser/profile.default "${@}" < /dev/null  

This is on a fresh install of Whonix 14 templates in Qubes 3.2


#2

Now reported here.


#3

Workaround documented here so you can continue testing.
https://github.com/QubesOS/qubes-issues/issues/3611#issuecomment-366979230


#4

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


#5

I should have noted that upgrading Whonix 13 to Whonix 14 did not produce these problems. Only from clean install. Which is noted in Issue 3611.

unset XDG_CONFIG_DIRS

We should unset that variable in the TemplateVM correct?

Edit: Nevermind, it works when applied to Whonix 14 TemplateBasedAppVM, not TemplateVM


#6

No, before running torbrowser.


#7

Ah yes. And it’d not persistent.


#8

Deployed.


#9

Confirmed. Clean install of Whonix 14 templates in Qubes 3.2 has TorBrowser working as expected.

Now if we can just find out why OpenBazaar2 Seg faults in Whonix 14 but not Whonix 13. . .


#10

This could be a deeper issue. If one application segfaults because of XDG_CONFIG_DIRS being too long, also other applications may segfault. If that happens, please try

unset XDG_CONFIG_DIRS

before starting the application manually from the same console.

and report back. The issue could be in some C library or so.