Package Details: dropbox 112.4.321-1

Git Clone URL: (read-only, click to copy)
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
Submitter: mtorromeo
Maintainer: mtorromeo
Last Packager: mtorromeo
Votes: 2344
Popularity: 4.54
First Submitted: 2009-01-22 14:21
Last Updated: 2020-12-22 08:34

Sources (8)

Pinned Comments

yan12125 commented on 2019-01-05 16:39

Run the following command in case you got errors during "Verifying source file signatures with gpg..."

gpg --recv-keys 1C61A2656FB57B7E4DE0F4C1FC918B335044912E

Alternatively, you can download Dropbox's public key from and import it with:

gpg --import rpm-public-key.asc

You can check whether keys are successfully imported or not using the output of gpg -k. You should find something like this:

pub   rsa2048 2010-02-11 [SC]
uid           [ unknown] Dropbox Automatic Signing Key <>

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.

yan12125 commented on 2017-11-06 15:13

Some useful places for issues about Dropbox itself (not the package):

  1. Official Dropbox user feedback forum

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

asakurahao commented on 2019-12-09 23:07

Similar to @rohit275, my dropbox was running pretty well until last weak. Now it is showing "connecting". I know it is not the network because I'm running other two "clouds" in the same computer and I have the dropbox in a windows computer at the "same network". Could someone help me, please?

ranger commented on 2019-12-04 09:11


The PKGBUILD as it is now, without what you call "the obvious fix" has never failed for me.

It's the user that has to take care of this, not the PKGBUILD. For example, if you add "the obvious fix" it will be impossible to use the --noextract option while building. Using the -c option is what the wiki suggests.

nyanpasu64 commented on 2019-12-04 05:52

overwriting generated files shouldn't be in the PKGBUILD, because not everyone wants this. If you want to run makekpg again and overwrite the files use makepkg --cleanbuild

When doing the obvious thing to upgrade dropbox, makepkg fails with an error. If you don't want to add the obvious fix, can you catch this particular error message and suggest running makepkg --cleanbuild or makepkg -src instead?

ranger commented on 2019-11-22 19:42

@ thebombzen,

overwriting generated files shouldn't be in the PKGBUILD, because not everyone wants this. If you want to run makekpg again and overwrite the files use makepkg --cleanbuild

Or even better, run makepkg -src when every time you run build a package, so you won't have any leftover files.

thebombzen commented on 2019-11-22 14:12

Can we add the -f argument to gendesk located in prepare() of PKGBUILD? If you run makepkg more than once, gendesk will refuse to overwrite the previously generated desktop file and exit with failure, causing the build to abort. Using -f will just tell it to overwrite the file if it exists.

jango commented on 2019-11-18 07:32

If you use dolphin file manager install this addons "dolphin-plugins" to see the folder status

Achilleus commented on 2019-11-13 23:04

dropbox: locating interpreter !! dropbox: can't trust path, fall back on working directory (relative)! !! dropbox: failed to resolve program path (No such file or directory)! !! dropbox: no executable path! (error 1) Przerwane (zrzut pamięci)

Zwenn76 commented on 2019-11-03 09:28

@ranger Thank you and sorry for posting here. I should have read the archwiki thoroughly.. But yes I can confirm that this workaround works.

ranger commented on 2019-11-03 09:11

@Zwenn76 You have to disable Dropbox auto update.

Zwenn76 commented on 2019-11-03 09:07

It seems like as soon as there is a new version and this package gets flagged out of date I am having trouble with my installed version. My CPU is running high and htop shows that in /.dropbox-dist/dropbox-lnx.x86_64-84.4.170 there are several version of /newversion running. So it seems that dropbox is aware that there is a newer version and starts complaining. I can only stop the daemon than. Is anyone facing the same issue?