mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3140] Problem with firefox nightly auto-update #1974
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#1974
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 @CodeArtisan00 on GitHub (Jan 12, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3140
On Manjaro(KDE) firefox-nightly & firefox-beta don't get auto update if running inside firejail. Can you suggest any work-around? Btw, without firejail, firefox can auto update.
On Manjaro auto update looks like
@rusty-snake commented on GitHub (Jan 12, 2020):
https://i.imgur.com/1RAD6wm.jpg
How do you install firefox?
@CodeArtisan00 commented on GitHub (Jan 12, 2020):
Downloaded d tar file from firefox & extracted it to /opt & made a launcher that's it.
@CodeArtisan00 commented on GitHub (Jan 17, 2020):
Without apparmor, auto update works properly. So, when I have to update I use,
firejail --ignore=apprmor /path/firefox@Vincent43 commented on GitHub (Jan 17, 2020):
In general profiles are developed with assumption that apps are installed through package managers like apt. If you download binaries yourself and put it in some arbitrary directory then some things may stop working. I think we can't really help other than propose above workaround.
@rusty-snake commented on GitHub (Jan 17, 2020):
@Vincent43 since your the AppArmor expert here, allows the apparmor profile writing in /opt?
@Neo00001 as @Vincent43 said, we can't do really more here.
@Vincent43 commented on GitHub (Jan 17, 2020):
AppArmor blocks writing in
/opt. Usually files in/optare owned & writable only by root but I guess in this case firefox folder was copied with user ownership and permissions. AppArmor profile also blocks execution from writable directories so allowing writing to/optwould violate this rule.@CodeArtisan00 commented on GitHub (Jan 17, 2020):
@rusty-snake & @Vincent43 thanks for clarifying. & I was just looking for a work-around. blocking writing to /opt is preferable