| Git Clone URL: | https://aur.archlinux.org/dropbox.git (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: | https://www.dropbox.com |
| Licenses: | custom |
| Submitter: | mtorromeo |
| Maintainer: | mtorromeo |
| Last Packager: | mtorromeo |
| Votes: | 2378 |
| Popularity: | 1.79 |
| First Submitted: | 2009-01-22 14:21 (UTC) |
| Last Updated: | 2025-03-26 08:13 (UTC) |
@ 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.
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.
If you use dolphin file manager install this addons "dolphin-plugins" to see the folder status
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)
@ranger Thank you and sorry for posting here. I should have read the archwiki thoroughly.. But yes I can confirm that this workaround works.
@Zwenn76 You have to disable Dropbox auto update.
https://wiki.archlinux.org/index.php/Dropbox#Prevent_automatic_updates
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?
I have been struggling with all the tips on the Arch Wiki as well as comments in this thread and have been unable to start my dropbox installation on a fresh Arch install. Previously was running into the same issues on Manjaro, where dropbox used to work fine before recent updates. The program seems to be eternally "connecting" even with a fresh install on a new arch install, and I am never able to log in or interact with the program at all. Has anyone else been having these issues? So far no solution has worked for me.
Pinned Comments
yan12125 commented on 2019-01-05 16:39 (UTC) (edited on 2019-02-27 08:11 (UTC) by yan12125)
Run the following command in case you got errors during "Verifying source file signatures with gpg..."
Alternatively, you can download Dropbox's public key from https://linux.dropbox.com/fedora/rpm-public-key.asc and import it with:
You can check whether keys are successfully imported or not using the output of
gpg -k. You should find something like this:yan12125 commented on 2018-08-01 11:41 (UTC) (edited on 2020-01-24 15:13 (UTC) by yan12125)
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 (UTC) (edited on 2019-03-18 03:50 (UTC) by yan12125)
Some useful places for issues about Dropbox itself (not the package):
https://www.dropboxforum.com/t5/Desktop-client-builds/bd-p/101003016 Official Dropbox user feedback forum
Arch Linux discussion places: https://bbs.archlinux.org/, #archlinux on freenode.net, https://lists.archlinux.org/listinfo/aur-general