Package Details: dropbox 15.4.22-1

Git Clone URL: (read-only)
Package Base: dropbox
Description: A free service that lets you bring your photos, docs, and videos anywhere and share them easily.
Upstream URL:
Licenses: custom
Conflicts: dropbox-experimental
Submitter: mtorromeo
Maintainer: mtorromeo
Last Packager: mtorromeo
Votes: 2145
Popularity: 18.549096
First Submitted: 2009-01-22 14:21
Last Updated: 2016-11-30 12:51

Dependencies (5)

Sources (7)

Pinned Comments

mtorromeo commented on 2016-02-24 10:27

STOP wasting my time and spamming everyone's mailboxes with useless requests to change the download URLs.
The cloudfrount links ARE OFFICIAL release locations.

Latest Comments

severoraz commented on 2016-12-09 18:54

Should this package mention somewhere that it does not have a signature so the "error: dropbox: missing required signature" message is expected?

Edit 1: and perhaps also mention or link to the safest way to work around this

mtorromeo commented on 2016-10-18 12:06

13.3.20 is a testing version.

Dropbox uses the following versioning scheme:
X.3.X = testing
X.4.X = stable

doron.behar commented on 2016-10-17 21:18

Has anyone tried to actually use the `dropbox.service` unit? I get this weird behavior when starting the service:
After running `systemctl --user start dropbox.service`, It is being started and restarted 3-5 times by systemd for some reason and afterwards you can see dropbox is running O.K but systemd thinks the service has failed. In the process of it being started and stopped you can actually see the tray icon showing up and down. I couldn't find very useful information with `journal -xe --user-unit=dropbox.service`.
I guess it is something with the unit file itself? I tried to change some Directives in the [service] section but it didn't work out.

I downloaded the new version (13.3.20) as mentioned by [@AJSlye]( and it was all fixed without changing the service file. **The problem was** with the `dropbox` binary - For some reason they made it fork itself or something and exiting with code 1 (very unusual). That's why systemd thought the command failed so it tried again and again for a few times and in the end dropbox was running ok.

Very Important to Update the package exactly if you are using the systemd `dropbox.service`.

AJSlye commented on 2016-10-15 06:59

New version available:

Alexpin commented on 2016-09-16 20:38

The urls are NOT official, they host user-created content. See:

jeroni commented on 2016-09-01 09:35

Has anyone issues when opening dropbox folder from tray icon's context menu in gnome? all gnome desktop icons disappear and have to kill nautilus and re-open it in order to appear again.
Another annoying thing is the tiny font on tray icon's context menu.

SuperIce97 commented on 2016-08-19 22:59

Can you use the dl.dropbox URLs instead? Those are the official release URLs on the site ( for instance). I really don't trust the cloudfront links

EDIT: I trust the cloudfront links as those are officially given in the forums, but I would prefer the other link because it is much easier to identify. The AUR can be dangerous and it's nice to check the links to make sure it's not malicious. It's much easier to see dropbox/u/17 and understand that it's safe, but seeing everythime is somewhat worrying and I always have to check the dropbox forums to make sure that is indeed the correct/safe link.

Notavi commented on 2016-08-09 10:34

Doesn't appear to work properly with Wayland desktops, although this can easily be worked around when starting dropbox manually by setting QT_QPA_PLATFORM="xcb".

Can the package be updated to avoid having to manually do this? Especially as people will probably not want this environment variable set for other applications (it forces Qt to use X11 instead of Wayland, so it's more of a compatibility fix than anything else).

darkvenger commented on 2016-07-12 09:09

@wfraser, or you could use the known hack to stop Dropbox from updating itself automatically ( and update it only through AUR.

wfraser commented on 2016-07-11 21:57

For me at least, the first thing the client does is download a newer version into my home directory, and on subsequent runs, it switches to that version, which then KILLS (literally, with SIGKILL) the one in /usr/bin/dropbox that I originally executed. This doesn't play nicely with things like systemd units which expect the original process to stay around.

Might I suggest changing /usr/bin/dropbox from a symlink to /opt/dropbox/dropbox, to something like the following:

dist="$HOME/.dropbox-dist/dropboxd" # this is where dropbox puts the updated version
if [ -x $dist ]; then
exec $dist
exec /opt/dropbox/dropbox

All comments