mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1630] dropbox: program cannot update itself #1094
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#1094
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 @laurento on GitHub (Nov 4, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1630
I've noticed dropbox doesn't update itself while running under firejail. The icon on the tray keeps the blue spinning emblem and the contextual menu the "upgrading..." entry.
If I instead run the dropbox application without using firejail everything works as expected. I've tried to look at the dropbox log messages and to run firejail in debug mode but I didn't see anything strange. Please let me know if I can provide any additional information.
@Fred-Barclay commented on GitHub (Nov 17, 2017):
Hi @laurento
What version of firejail, and what Linux distro, are you running?
I've tried replicating this myself on Ubuntu 17.10, but I can't figure out how to force dropbox to install an old version so I can try updating. 🙁
@laurento commented on GitHub (Nov 17, 2017):
Since I opened the issue here I ran dropbox out the jail to let it upgrade. My current version is v37.4.29 and it has the same issue. I'm running debian testing.
@laurento commented on GitHub (Jan 18, 2018):
I'm using firejail-0.9.52 and dropbox-41.4.80 right now and the issue seems to be gone. I propose to close this bug report.
@Fred-Barclay commented on GitHub (Jan 19, 2018):
Closing, thanks!
@laurento commented on GitHub (Sep 24, 2018):
Aaarg! Brand new installation firajail-0.9.4 on Debian Buster (testing) same issue :(
Shall we reopen this issue?
@Fred-Barclay commented on GitHub (Sep 24, 2018):
Yep, reopening!
@laurento please kill dropbox, download https://raw.githubusercontent.com/netblue30/firejail/master/contrib/jail_prober.py, and run
python3 jail_prober.py dropbox(you may need to change the dropbox executable path or name -- I don't know what it is 😄 ). Then follow the prompts in the terminal -- enter 'y' if dropbox works correctly and 'n' if it doesn't. Paste the output back here.(jail_prober.py is an experimental script I wrote -- it works on my end but apologies in advance if it doesn't work for you!).
@chiraag-nataraj commented on GitHub (May 20, 2019):
Is this still an issue @laurento?
@laurento commented on GitHub (May 21, 2019):
Well, last time I've tried (few months ago) the issue was still there. However, I'm now using dropbox via flatpak so I solved using a different kind of confinement :)
@chiraag-nataraj commented on GitHub (May 21, 2019):
I guess I'll close this for now then - we can always re-open if it's an issue and they wan to stick with firejail :D
@chiraag-nataraj commented on GitHub (May 23, 2019):
Haha I'll re-open it myself since I'm running into the same issue right now 😂
@chiraag-nataraj commented on GitHub (May 23, 2019):
Never mind. I restarted it after it kept spinning and now it says "up to date"...🤷♂️
@chiraag-nataraj commented on GitHub (May 23, 2019):
Sorry for the noise. I figured out that it didn't actually update.
The most annoying thing is that I need to let it sit there a little while each time for it to figure out it needs to update (I don't think there's a way I can manually force an update...).
@chiraag-nataraj commented on GitHub (May 23, 2019):
Workaround: Use the control script here and run the
updateoperation. If it works, I'll add the workaround label and close this again 😜[edit] Unfortunately, it did not work.
[edit2] Ah, okay. The issue is the
is_dropbox_valid()function in the Python script that checks to make sure the download is able to run. I'm going to try hacking the script so it doesn't try to do that...@chiraag-nataraj commented on GitHub (May 24, 2019):
Here's the full workaround:
is_dropbox_valid()function (starts at line254I believe) to alwaysreturn True(you don't even need to do much, just ensure that's the first line of the function and you don't even need to touch the rest).dropboxdinstance.firejail --join=dropboxd ~/path/to/dropbox.py updateI just tested this with a
firejail-eddropboxdand it updated properly! I'm going to close this for now and tag it with the workaround label as stated earlier.@cebas commented on GitHub (Oct 3, 2022):
Hi, this is still happening to me.
I have Kubuntu 22.04 and firejail 0.9.70
Is there any way to fix it with local profiles?
@powerman commented on GitHub (Aug 1, 2025):
Still actual.
As a glance
firejail --join=dropbox dropbox-cli updateand then manual restart works around the issue, but it usually starts spinning after a while after restart, so I'm not 100% sure it is actually fixed now.@kmk3 commented on GitHub (Aug 1, 2025):
What firejail version/distribution name/version?
For debugging, you could try commenting lines in dropbox.profile until it works
to see which ones are causing the issue and then post them here.
@powerman commented on GitHub (Aug 1, 2025):
Gentoo Linux. Using default dropbox profile.
globals.localblacklists a few dirs in${HOME}, completely unrelated to dropbox.Sure, I know. But taking in account it starts spinning after a while after start and there is no way to force it start updating immediately - this kind of debugging may take days, if not weeks. Also it's not clear how to undo successful upgrade to force it upgrade again (just remove all files in .dropbox-dist/?).
@kmk3 commented on GitHub (Aug 1, 2025):
That's unfortunate.
Not sure of a good way to debug it then.
Maybe it would be feasible to analyze the update code and create a separate
script that calls into the update function and/or that allows installing a
specific version.
Similarly to that comment above:
If that works, maybe it could be published in its own repository to help
improve the experience of other dropbox users.
@powerman commented on GitHub (Aug 1, 2025):
Link "this script" in that comment is useless.