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

@fra-san Ah, sorry, I was not aware that it was already proposed.

So, it looks like currently, no easy solution for all setups is possible. It could maybe be solved by a wrapper script, but really the starting process should be standardized upstream.

The %h is on me. I didn't test it with the system unit. I used it because homes can be in other locations than /home/$USER. It seems like there is no easy solution for instantiated units for that case.

And I forgot, that I symlinked .dropbox to .local/share/dropbox.

So next time I will think longer and search harder, before I post here.

@jomority Something like that has been proposed in late 2018, see this comment by soderstrom.

Unfortunately it doesn't work in some configurations, as I pointed out back then. The dropbox process only forks if it can find a new version online. This is usually true if you haven't opted out from the "Early releases" program. If a new version cannot be found, the process does not fork, systemd assumes something went wrong (when a timeout is hit), kills it and starts a new instance. In a loop. This issue may be possibly worked out, but any solution will have to be thoroughly tested before it can be added to the package.

As an aside: %h in system units (dropbox@) resolves to /root; (at least on my system) the pid file's full path has to be /home/%I/.dropbox/dropbox.pid.

I have another solution for using the dropbox service (referencing the pinned comment of yan12125 from 2018-08-01). Override the unit with:

[Service]
# Fix successful start not detected
SuccessExitStatus=SIGKILL
# Fix stopping and detection of running status and main process
Type=forking
PIDFile=%h/.local/share/dropbox/dropbox.pid

You can override this with systemctl --user edit dropbox or sudo systemctl edit dropbox@ depending on if you are using the user service.

Maybe the package sources could also be updated.

I'm also constantly having that message about using -f in gendesk. I know very little about PKGBUILD files, but I can assure that I only have this issue with this Dropbox build file, and it happens everytime I update Dropbox. The rest of the packages I have installed don't complains about using -f with gendesk or need any kind of special attention. I really appreciate the work of the maintainers of this package, but having to update it in a different way than others is not user friendly. Some users like myself would prefer to simplify everything as much as possible when update their systems.

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.