mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2110] Tor Browser stopped working with firejail after a major update #1428
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1428
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Sep 7, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2110
I am using firejail-0.9.54 on Slackware64 Linux-14.2 and today Tor Browser updated itself from version 7.5.6 to version 8.0. After this Tor Browser doesn't work anymore when launched through firejail. Once the main window starts, it displays the message:
Same happens for any new opened tab. It works fine without firejail.
@smitsohu commented on GitHub (Sep 7, 2018):
Hi @somospocos, we believe this is already fixed for upcoming 0.9.56.
See
defb5a4891and736216cacfGeneral question: Should this go to etc-fixes?
@Nurmagoz commented on GitHub (Sep 8, 2018):
This has been reported against TorProject and FF. because it effects both of them and tested by me:
FF 60:
https://bugzilla.mozilla.org/show_bug.cgi?id=1488078
TBB 8.0:
https://trac.torproject.org/projects/tor/ticket/27407#ticket
@SkewedZeppelin commented on GitHub (Sep 8, 2018):
@TNTBOMBOM
This is not something that upstream Mozilla can/will fix, this is purely an issue with our profiles.
This issue that has been fixed since 0.9.54 for Firefox and derivatives
and is fixed for Tor Browser in master (future 0.9.56).
What version of Firejail are you running?
@Nurmagoz commented on GitHub (Sep 8, 2018):
@SkewedZeppelin 0.9.44.8 from debian stretch stable repo. if firejail have been fixing that why dont u push the changes to Debian Repo ??
@SkewedZeppelin commented on GitHub (Sep 8, 2018):
@TNTBOMBOM 0.9.54 is available via stretch-backports
@Nurmagoz commented on GitHub (Sep 8, 2018):
@SkewedZeppelin saw that , still bad if its a stable version then its better to be pushed for the stable repo.
@Vincent43 commented on GitHub (Sep 8, 2018):
That's not how Debian stable works. They take the last stable firejail version at the point of Debian release and stick with it forever. If you want to have firejail gradually updated to latest version then use backports, testing, unstable or different distro.
Security updates are exception, that's why they keep updating chromium and firefox esr.
@Nurmagoz commented on GitHub (Sep 10, 2018):
@SkewedZeppelin @Vincent43 thats great it worked fine with FF , but sadly it break TBB. any idea how to overcome that?
@Vincent43 commented on GitHub (Sep 10, 2018):
Fixes for tor browser aren't part of 0.9.54, they will be in 0.9.56. For now you may copy profiles manually:
https://github.com/netblue30/firejail/blob/master/etc/start-tor-browser.profile
https://github.com/netblue30/firejail/blob/master/etc/torbrowser-launcher.profile
@HundyK commented on GitHub (Sep 12, 2018):
Is the Tor fix part of 0.9.56~rc1?
I am running into the same problem with the tabs crashing on startup using 0.9.56~rc1.
@SkewedZeppelin commented on GitHub (Sep 12, 2018):
@HundyK the fix for TBB is not in 0.9.56rc1, only master (future 0.9.56 release).
@chiraag-nataraj commented on GitHub (Sep 25, 2018):
Which has now been released! Closing this for now, but please feel free to reopen if you still have this issue after upgrading.
@Nurmagoz commented on GitHub (Oct 2, 2018):
after adding profiles to /etc/firejail/torbrowser-launcher as copy/paste from this link:
https://github.com/netblue30/firejail/blob/master/etc/torbrowser-launcher.profile
result after that, by running
firejail torbrowser-laucherwill give:@chiraag-nataraj please re-open this ticket
@Fred-Barclay commented on GitHub (Oct 2, 2018):
@TNTBOMBOM What version of firejail are you using?
Can you also please run the following and paste the output back here?
firejail --debug torbrowser-launcherThanks!
EDIT: I expect you're using an older version of firejail that doesn't have
/etc/firejail/disable-xdg.inc, but the profile you copied expects it. 😉 . If so, simply removing the lineinclude /etc/firejail/disable-xdg.incfrom your profile should fix this.@Nurmagoz commented on GitHub (Oct 3, 2018):
@Fred-Barclay
Big Thanks!!!
@Zypherspace commented on GitHub (Nov 23, 2018):
Same problem here as TNTBOMBOM
Raw contents of https://github.com/netblue30/firejail/blob/master/etc/torbrowser-launcher.profile were cut/pasted, no file permissions changed. Tried removing the include /etc/firejail/disable-xdg.inc as suggested, same error. Running latest master from git.
@Vincent43 commented on GitHub (Nov 23, 2018):
What system you using?
@Zypherspace commented on GitHub (Nov 24, 2018):
Fedora 29 Cinnamon. It is working on a fresh install of Fed 29 Plasma without any changes to profile.
I've reinstalled Tor-Browser. TB runs correctly outside Firejail.
I see some errors in terminal during TB launch:
@SkewedZeppelin commented on GitHub (Nov 24, 2018):
@Zypherspace please see https://github.com/netblue30/firejail/issues/2038#issuecomment-405096879
@Zypherspace commented on GitHub (Nov 29, 2018):
I tried the full scrub of firejail as detailed in #2038. I followed with a full recursive search and deleted any firejail remnants before reinstalling. Reinstalled with make rpms. Unfortunately I still see the
Gah. Your tab just crashed.code on Tor-browser. Fedora has been updated several versions on the machine it's got a lot of ragtag symlinks, I'll reinstall a fresh release soon.@Futureknows commented on GitHub (Jan 11, 2019):
Commenting out seccomp fixed it for me.