Package Details: dropbox 100.4.409-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: 2324
Popularity: 10.42
First Submitted: 2009-01-22 14:21
Last Updated: 2020-06-27 19:26

Dependencies (14)

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

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

Devastator commented on 2020-07-05 13:39

Something wrong with /usr/bin/dropbox symlink, but i have no idea whats wrong. I get error:

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)
Aborted (core dumped)

When i launch from /opt/dropbox/dropbox then no errors.

eisterman commented on 2020-07-02 00:14

In PKGBUILD, prepare(), if it already finds the existing dropbox.desktop file, rather than overwriting because it already exists, it raise an error, which often happens if an installation has abnormally crashed before.

In particular, line 45 should be replaced with gendesk -f --pkgname="$pkgname" --pkgdesc="$pkgdesc" --categories=Network PKGBUILD adding the flag -f to overwrite the dropbox.desktop file during preparation.

varunsbhatta commented on 2020-06-17 19:28

Build is failing with the following log.

==> Validating source files with sha256sums...
    DropboxGlyph_Blue.svg ... Passed
    terms.txt ... Passed
    dropbox.service ... Passed
    dropbox@.service ... Passed
==> Validating source_x86_64 files with sha256sums...
    dropbox-lnx.x86_64-99.4.501.tar.gz ... FAILED
    dropbox-lnx.x86_64-99.4.501.tar.gz.asc ... Skipped
==> ERROR: One or more files did not pass the validity check!
Failed to build dropbox

I have the imported the right keys (as mentioned in the pinned comment). Any help?

ranger commented on 2020-06-05 14:55

@nthorderindex, maybe you should try to install without any aur helpers? To see if the problem is with your system or with the aur helper

nthorderindex commented on 2020-06-05 14:48

@gothicVI I'm using aura, which needs to be run as root when installing packages. I've installed this package before using aura without an issue, I'm just trying to upgrade (97.4.467-1 -> 98.4.158-1). I tried using pikaur instead and the check passed, so it does seem to be an issue with aura though and not actually with this package.

EDIT: In case anyone else has this problem, it's solved by using sudo -E rather than just sudo. Explanation in the aura changelog here:

gothicVI commented on 2020-06-05 05:34

@nthorderindex what's the exact command you're using to install dropbox in the first place?

If you're running, e.g., pikaur or yay do not run them as root.

nthorderindex commented on 2020-06-04 21:00

Not sure what to make of this — I've imported the key (and it shows up in the output of gpg -k) but am currently getting a "PGP signatures could not be verified" error:

==> Verifying source file signatures with gpg...
    dropbox-lnx.x86_64-98.4.158.tar.gz ... FAILED
==> ERROR: One or more PGP signatures could not be verified!

jerz4evr commented on 2020-05-31 02:30

An single command to fix the errors with file signature verification as referenced by yan12125's comment is the following:

curl | gpg --import

This is especially helpful if you keep getting the following error when trying to use gpg --recv-keys 1C61A2656FB57B7E4DE0F4C1FC918B335044912E:

gpg: keyserver receive failed: Server indicated a failure

gothicVI commented on 2020-05-21 21:48

@Groumpf: Thanks a lot! That actually does the trick...

Groumpf commented on 2020-05-21 15:54

@gothicVI: I accidentally ran pikaur as root and got your error message. Try running pikaur as a normal user.