Arch Linux User Repository

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 https://linux.dropbox.com/fedora/rpm-public-key.asc 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]
      1C61A2656FB57B7E4DE0F4C1FC918B335044912E
uid           [ unknown] Dropbox Automatic Signing Key <linux@dropbox.com>

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

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

1. https://www.dropboxforum.com/t5/Desktop-client-builds/bd-p/101003016 Official Dropbox user feedback forum

2. Arch Linux discussion places: https://bbs.archlinux.org/, #archlinux on freenode.net, https://lists.archlinux.org/listinfo/aur-general

warning: could not get file information for opt/dropbox/libdropbox_sqlite_ext.so
warning: could not get file information for opt/dropbox/libdropbox_tprt.so
warning: could not get file information for opt/dropbox/libffi.so.6
warning: could not get file information for opt/dropbox/libicudata.so.42
warning: could not get file information for opt/dropbox/libicui18n.so.42
warning: could not get file information for opt/dropbox/libicuuc.so.42
warning: could not get file information for opt/dropbox/libpopt.so.0
warning: could not get file information for opt/dropbox/librsync.so.1
warning: could not get file information for opt/dropbox/librsyncffi.compiled._librsyncffi.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/linuxffi.gnu.compiled._linuxffi_gnu.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/linuxffi.pthread._linuxffi_pthread.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/linuxffi.resolv.compiled._linuxffi_resolv.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/linuxffi.sys.compiled._linuxffi_sys.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/linuxinfinite.compiled._infinite.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/math.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/mmap.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/nucleus_python.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/parser.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/plugins/platforms/libqxcb.so
warning: could not get file information for opt/dropbox/posixffi.libc._posixffi_libc.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/pyexpat.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/python-packages.zip
warning: could not get file information for opt/dropbox/qt.conf
warning: could not get file information for opt/dropbox/resource.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/resources/resources_images.rcc
warning: could not get file information for opt/dropbox/resources/resources_qml.rcc
warning: could not get file information for opt/dropbox/select.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/sip.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/termios.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/tornado.speedups.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/tprt.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/unicodedata.cpython-37m-x86_64-linux-gnu.so
warning: could not get file information for opt/dropbox/wmctrl
warning: could not get file information for usr/bin/dropbox
warning: could not get file information for usr/lib/systemd/system/dropbox@.service
warning: could not get file information for usr/lib/systemd/user/dropbox.service
warning: could not get file information for usr/share/applications/dropbox.desktop
warning: could not get file information for usr/share/licenses/dropbox/terms.txt
warning: could not get file information for usr/share/pixmaps/dropbox.svg
:: Processing package changes...
(1/1) reinstalling dropbox                                             [---------------------------------------] 100%
error: could not extract /opt/dropbox/libdropbox_nucleus.so (Lzma library error:  No progress is possible)
error: problem occurred while upgrading dropbox
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.

I could not run dropbox, it gives me this error: "thread panicked while processing panic. aborting. Segmentation faul (core image recorded)"

You are right, it's not correct because it's not failing for me. But it is correct because it is as the official guideline describes. It fails if you don't clear your build path. The wiki says you should clean the build path. Clean your build path.

@ranger

Just because it's never failed for you does not mean it is correct. If it fails for other people it's not all those users' responsibility to fix something that you close as "worksforme."

Also this has nothing to do with the --noextract option.

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?

@nyanpasu64,

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.

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?

@ 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.