Package Details: dropbox 55.4.171-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 (yan12125)
Last Packager: yan12125
Votes: 2258
Popularity: 11.246787
First Submitted: 2009-01-22 14:21
Last Updated: 2018-08-15 11:18

Pinned Comments

yan12125 commented on 2018-08-01 11:41

If you can't run the dropbox@ service normally, try to create a read-only directory ~/.dropbox-dist and run again. See for details.

yan12125 commented on 2017-11-06 15:13

Due to more and more comments unrelated to the package itself, I decided to disable AUR comment notifications. If you believe there's really an issue in PKGBUILD and/or relevant packaging scripts, please open an issue at with a title starting with "dropbox:".

Some useful places for Dropbox issues:

  1. Official Dropbox user feedback forum

  2. Arch Linux discussion places:, #archlinux on,

Latest Comments

1 2 3 4 5 6 ... Next › Last »

soderstrom commented on 2018-09-01 14:46


Here is a permanent fix for dropbox service reloading.

Dropbox actually works correctly by forking itself, and it even gives us ~/.dropbox/ so systemd can know which process id to track.

There were some minor issues with dropbox return SIGKILL between process which really doesn't work with restart=on-failure alone. Therefore, SuccessExitStatus for SIGKILL was needed. Finally I also noticed that dropbox doesn't properly clean up (i.e. removing the file from last session) so had to add an ExecStopPost command for that.

You can see all of this here

This way automatic updates works again an you no longer need to make ~/.dropbox-dist read-only.

One concern I have is haven't tested this for only for the, so might be worth checking out.

Also note that, be a journal entry of the form "dropbox@$USER.service: Can't open PID file /home/$USER/.dropbox/ (yet?) after start: No such file or director"

This is because dropbox takes longer than some timeout before creating the file. Essentially it is triggering because of the "yet" part of that message. The line after will be "Started Dropbox" and everything is fine.

At least the ground labor is done now.

Enjoy your day.

yan12125 commented on 2018-08-31 06:08

@mtorromeo: Is it OK for you if I add lilac as a co-maintainer? I'd like to configure the lilac bot [1] to update this package automatically. (I can do that myself as I'm now a trusted user, just ask for approval)


yan12125 commented on 2018-08-01 11:41

If you can't run the dropbox@ service normally, try to create a read-only directory ~/.dropbox-dist and run again. See for details.

JatraMaya commented on 2018-06-20 16:06

@parnmatt & @sl13kp

Just edit the PKGBUILD, find this line and remove the bold text. find "$pkgdir"/opt/dropbox/ -type f -exec chmod 644 {} \; chmod 755 "$pkgdir"/opt/dropbox/dropboxd chmod 755 "$pkgdir"/opt/dropbox/dropbox{,_py3}

a-bostaurus commented on 2018-06-20 16:02

Got the same problem as parnmatt.

parnmatt commented on 2018-06-20 14:45

I'm getting an error with the recent update; are you missing a file?

chmod: cannot access '/var/cache/pacman/pkg/dropbox25812/dropbox/pkg/dropbox/opt/dropbox/dropbox_py3': No such file or directory

sl13kp commented on 2018-06-20 14:00

chmod: impossibile accedere a '/tmp/yaourt-tmp-stefano/aur-dropbox/pkg/dropbox/opt/dropbox/dropbox_py3

afwlehmann commented on 2018-05-23 17:34

If I'm not mistaken then the current pkgrel should be reset to 1 now that pkgver was upgraded to 50.4.71.

yan12125 commented on 2018-05-09 08:00

49.4.68 is announced, anyway.

BTW, @jorgicio, how did you find the new URL before it's announced?

jorgicio commented on 2018-05-08 23:53

In fact, althought no news were published, the 49.4.68 is up. I'm now in Gentoo, I maintain the dropbox package on my overlay, and that version is up.