mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #357] Firejail Breaking Firefox Menu, Wiping All Settings, And Breaking Audio in FF & Chromium #253
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#253
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 @bitnom on GitHub (Mar 7, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/357
I started using firejail/firetools and was very happy with it. I then read that someone was using it in conjunction with apparmor so I loaded up apparmor profiles for FF and Chromium along with using firejail. As soon as I did that and started up Firefox with Firetools, all of my settings/bookmarks/addons/entire profile had been reset and firefox acted like it's a new install and pressing the main settings button in FF didn't work. I quickly disabled apparmor by uninstalling the apparmor profiles and resetting its cache and reloading it (Also a reboot).
I deleted my ~/.mozilla directory and started Firefox again, reconfigured firefox (Mostly via sync), closed it, and ran it using firetools. Same behaviour. My browser gets reset and even running FF without firejail after this happens my browser is reset. I also noticed that no sound works while running in firejail now and this is happening across browsers. If I'm watching a video in Chromium/firejail and then try running FF using firejail the audio cuts out in both browsers immediately. I tried reinstalling all the firejail tools to no avail. No matter how many times I reset my mozilla profile I can't get it back to normal. Apparmor is no longer running so I don't see why this is still happening. I could really use help because I was very excited to be using firejail. Here's a firejail debug I just did when running FF: http://hastebin.com/arexonayey
@bitnom commented on GitHub (Mar 7, 2016):
I keep trying different things but nothing works. I tried apt-get purge for firejail/firetools. I tried deleting my mozilla profile folder, starting FF as normal, setting up, and then using firejail. I tried using firejail from the very start (Which causes a ~/.mozilla directory to never be created). No matter what I do, firejail causes my firefox to completely reset. I'm on kubuntu 15.10 btw.
@bitnom commented on GitHub (Mar 7, 2016):
Please let me know if there's any info I can give that will help. I don't want to do a full reinstall just to use this software but I will if I have to because I was impressed by it until this happened. I don't know if using apparmor was the cause. I have it completely off now but still the same problem.
@chiraag-nataraj commented on GitHub (Mar 7, 2016):
Can you try starting
firejail --noprofile firefoxto see if anything changes? Also, can you post the contents of/etc/firejail/firefox.profile,/etc/firejail/disable-mgmt.profile,/etc/firejail/disable-secret.profile,/etc/firejail/disable-common.profile,/etc/firejail/disable-devel.profile, and/etc/firejail/whitelist-common.profile? I want to make sure they match what I have in those files on my end.Assuming the problem isn't firejail though, there are a couple of things that could be going on. Try making sure your apparmor is completely disabled because it seems that's what screwed it up in the first place (although it shouldn't?). Let's first try getting firefox to work normally without firejail - then we can worry about firejail.
@bitnom commented on GitHub (Mar 7, 2016):
Firefox does work normally without firejail. It's only when I use it with firejail that it resets. I'll collect the infos. First I'll backup my current profile and then post the results.
@bitnom commented on GitHub (Mar 7, 2016):
"firejail --noprofile firefox" starts up firefox as though there is no current ~/mozilla. directory (All settings lost). If I then start firefox without firejail, it doesn't start over to where it asks me if I want to import settings from chrome but everything else is reset (I can test by something as simple as removing a toolbar entry) and every time I start firefox using firejail it will reset to this state again.
"/etc/firejail/firefox.profile": http://hastebin.com/egovuraquw.hs
"/etc/firejail/disable-mgmt.profile": No such file or directory (But I do see what I think you meant...)
"/etc/firejail/disable-mgmt.inc": http://hastebin.com/zavecayuni.hs
And the same with the rest you requested, they exist as .inc files...
"/etc/firejail/disable-secret.inc": http://hastebin.com/zoritenoru.hs
"/etc/firejail/disable-common.inc": http://hastebin.com/uhoqozudog.rb
"/etc/firejail/disable-devel.inc": http://hastebin.com/ofobibavix.hs
"/etc/firejail/whitelist-common.inc": http://hastebin.com/veyemuxidu.avrasm
@bitnom commented on GitHub (Mar 7, 2016):
I'm using firejail_0.9.38_1_amd64 installed via .deb
@bitnom commented on GitHub (Mar 7, 2016):
Here's another dump from "firejail --debug firefox" where I ran it and then closed it: http://hastebin.com/uzosucosux.vhdl
As usual, all settings are gone and then when I run firefox without firejail, all settings seem to be wiped or reset.
@netblue30 commented on GitHub (Mar 7, 2016):
Disable apparmor then reboot. Start firefox several times, set some bookmarks and see if it keeps the changes between restarts. Then you bring in firejail and test if the changes survive a restart.
I've heard bout people having problems with apparmor+firejail. Some of them managed to get it running. I'll look at it when 16.04 comes up. There seem to be some problems in with firejail and apparmor profiles stepping on each other.
@bitnom commented on GitHub (Mar 7, 2016):
I just discovered the solution before coming back here. I had to do: "apparmor --teardown"
I then rebooted and apparmor started up. Same problem until I did apparmor --teardown again and stopped apparmor. Even though I had previously done apt-get remove apparmor-profiles, I still see:
/etc/apparmor.d/usr.bin.firefox
/etc/apparmor.d/local/usr.bin.firefox
I'm going to try deleting those (The Chromium ones if they exist as well), reboot, and then using firejail again. If that doesn't work I'll completely remove apparmor but I suspect it will work.
@netblue30 commented on GitHub (Mar 7, 2016):
Let me know how it goes, I guess I'll have to put a note on the website to stop people from turning apparmor on, at least until 16.04 is out.
@bitnom commented on GitHub (Mar 7, 2016):
Well, at least warn them to not load conflicting profiles. I'm not even sure that chromium had a problem. It was only when I ran firefox with firejail that the audio cut out in both browsers. Chomium never lost its settings. Firefox had the big issue (Of course a lot of people probably find firejail looking to jail firefox).
@bitnom commented on GitHub (Mar 7, 2016):
Running one final test with all my FF data synced to a new ~/mozilla...
@bitnom commented on GitHub (Mar 7, 2016):
Confirmed... Unloading the apparmor firefox profile via "apparmor --teardown", and deleting the apparmor firefox profiles (There's a main one and an override file) solves the issue and allows firejail to function with firefox. I would love to have used both apparmor and firejail together with firefox and will surely be willing to test that in the future on my build. Let me know if you need any help in the future with testing them together.
@netblue30 commented on GitHub (Mar 9, 2016):
Thanks!
@bitnom commented on GitHub (Mar 31, 2016):
Has this been resolved yet in any way?