Package Details: dropbox 220.4.4126-1

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.72
First Submitted: 2009-01-22 14:21 (UTC)
Last Updated: 2025-03-26 08:13 (UTC)

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

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>

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):

  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

Latest Comments

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 97 Next › Last »

fra-san commented on 2018-10-16 13:19 (UTC) (edited on 2018-10-16 13:19 (UTC) by fra-san)

I'm really interested in keeping dropbox running smoothly, so I kept playing with the patches proposed by soderstrom and yan12125.
I found an issue with systemd units that use Type=forking: if you opt out from Dropbox's "Early releases" program (i.e. from using beta and experimental version) and you install the latest stable version, then at startup dropbox can't find a new version and doesn't fork, making the systemd service hit a timeout and fail. The service, then, restarts itself, times out again, and... you know.
It looks like Type=simple with disabled automatic updates is the only configuration that works in the most common scenarios.

fra-san commented on 2018-10-09 18:00 (UTC) (edited on 2018-10-10 09:18 (UTC) by fra-san)

@soderstrom
Just one point: it might be useful to point out that your proposal requires ~/.dropbox-dist to be writable, otherwise the start job fails and dropbox is caught in a restart loop. I don't completely like the idea of having unavoidable automatic updates, but if it's ok for other users I'll live with it.

EDIT: Sorry, I should have been more precise. I can only confirm the aforementioned error if ~/.dropbox-dist is created with permissions = 000 as suggested in https://wiki.archlinux.org/index.php/Dropbox. Not sure about a read-only ~/.dropbox-dist with something inside it.

johannes87 commented on 2018-10-06 17:08 (UTC)

The current version is 58.4.92. Updating worked on my x86_64 computer by updating pkgver and sha256sums_x86_64 in PKGBUILD

yan12125 commented on 2018-10-03 13:11 (UTC) (edited on 2018-10-09 18:14 (UTC) by yan12125)

I'd like to drop dropbox@.service in favor of dropbox.service to fix https://gitlab.com/yan12125/aur/issues/23. Please leave comments there if you object.

<del>I'll carry out the change if no one objects in two weeks.</del>

UPDATE: as mentioned by Francesco Sanesi, dropping dropbox@.service might break multi-user scenarios. I'll postpone the original plan.

soderstrom commented on 2018-09-01 14:46 (UTC) (edited on 2018-09-01 23:21 (UTC) by soderstrom)

@yan12125

Here is a permanent fix for dropbox service reloading.

Dropbox actually works correctly by forking itself, and it even gives us ~/.dropbox/dropbox.pid so systemd can know which process id to track.

There were some minor issues with dropbox return SIGKILL between process which really doesn't work with restart=on-failure alone. Therefore, SuccessExitStatus for SIGKILL was needed. Finally I also noticed that dropbox doesn't properly clean up (i.e. removing the dropbox.pid file from last session) so had to add an ExecStopPost command for that.

You can see all of this here

https://github.com/soderstrom-rikard/arch-linux-package-dropbox/commit/1c0db3a058091bb4fae9f36859f05845c7d2f191

This way automatic updates works again an you no longer need to make ~/.dropbox-dist read-only.

One concern I have is haven't tested this for default.target only for the multi-user.target, so might be worth checking out.

Also note that, be a journal entry of the form "dropbox@$USER.service: Can't open PID file /home/$USER/.dropbox/dropbox.pid (yet?) after start: No such file or director"

This is because dropbox takes longer than some timeout before creating the dropbox.pid file. Essentially it is triggering because of the "yet" part of that message. The line after will be "Started Dropbox" and everything is fine.

At least the ground labor is done now.

Enjoy your day.

yan12125 commented on 2018-08-31 06:08 (UTC)

@mtorromeo: Is it OK for you if I add lilac as a co-maintainer? I'd like to configure the lilac bot [1] to update this package automatically. (I can do that myself as I'm now a trusted user, just ask for approval)

[1] https://github.com/archlinuxcn/lilac

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.

JatraMaya commented on 2018-06-20 16:06 (UTC) (edited on 2018-06-20 16:10 (UTC) by JatraMaya)

@parnmatt & @sl13kp

Just edit the PKGBUILD, find this line and remove the bold text. find "$pkgdir"/opt/dropbox/ -type f -exec chmod 644 {} \; chmod 755 "$pkgdir"/opt/dropbox/dropboxd chmod 755 "$pkgdir"/opt/dropbox/dropbox{,_py3}

a-bostaurus commented on 2018-06-20 16:02 (UTC)

Got the same problem as parnmatt.

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 .. 97 Next › Last »