mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2657] Dropbox will not start with default profile Kubuntu Ubunutu 18.10 firejail version 0.9.54 #1674
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#1674
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 @Mothsdroyp on GitHub (Apr 17, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2657
Dropbox will not start after sudo firecfg on Kubuntu Ubunut 18.10 firejail version 0.9.54.
It seems that the error is due to in the supplied profile below the "include /etc/firejail/disable-interpreters.inc". Dropbox needs python to run as far as I can tell.
I edited the profile supplied with the firejail version simply by commenting out the include interpreters line and placing the edited profile in ~/.config/firejail/dropbox.profile
I am unsure if this is the optimal solution, but it seems to work for the time being!
@Mothsdroyp commented on GitHub (Apr 17, 2019):
Sorry about the unusual text size in part of the bug report -- unsure why that happened
@ghost commented on GitHub (Apr 17, 2019):
When you name the file ~/.config/firejail/dropbox
.localinstead, firejail is smart enough to automatically pick up any options in there and will use them to override whatever is in the system-wide /etc/firejail/dropbox.profile. By naming it with a .profile suffix under your ${HOME} dir, you're actually replacing the one in /etc/firejail and you will have to track potential changes to the profile yourself. To avoid all that, you can tackle the python problem in a ~/.config/firejail/dropbox.local file while leaving the rest intact:That will override what's in /etc/firejail/disable-interpreters.inc more selectively, no need to comment it out completely. It still keeps unneeded interpreters inaccessable, which is considered safer/more secure/less insecure depending on who you ask 😄
Use the toolbar options just above the input box to avoid copy-pasted code to mess with the styling.
@chiraag-nataraj commented on GitHub (May 21, 2019):
This seems to have been resolved, so I'll go ahead and close this. @Mothsdroyp, please feel free to re-open if you have more questions.
@chiraag-nataraj commented on GitHub (May 21, 2019):
Should we modify the shipped dropbox profile to not blacklist python2 or whatever?
@Mothsdroyp commented on GitHub (Apr 22, 2020):
The following lines are also needed in addition to the above noblacklist {HOME}/.dropbox* and noblacklist {HOME}/Dropbox* is also needed.
With these additional lines firejail provides excellent security by preventing inadvertent sharing / uploading of files
@rusty-snake commented on GitHub (Apr 22, 2020):
noblacklist ${HOME}/Dropbox*is not needed because there is noblacklist ${HOME}/Dropbox*.