Dropbox cannot work properly on Gnome 42. The icon on the top bar is not clickable so the preferences cannot be managed.
Search Criteria
Package Details: dropbox 150.4.5000-1
Package Actions
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: | 2370 |
Popularity: | 4.34 |
First Submitted: | 2009-01-22 14:21 (UTC) |
Last Updated: | 2022-06-11 16:07 (UTC) |
Dependencies (14)
- dbus (dbus-elogind, dbus-git, dbus-nosystemd-minimal-git, dbus-nosystemd, dbus-selinux, dbus-x11, dbus-xdg-docs)
- fontconfig (fontconfig-srb, fontconfig-minimal-git, fontconfig-git, fontconfig-ubuntu)
- libsm
- libxcomposite
- libxdamage
- libxmu
- libxrender
- libxslt (libxslt-git)
- libxxf86vm
- gendesk (make)
- libappindicator-gtk3 (libappindicator-bzr) (optional) – make tray icons themed under some desktop environments like KDE plasma
- perl-file-mimeinfo (optional) – opening dropbox folder on some desktop environments
- ufw-extras (optional) – ufw rules for dropbox
- xdg-utils (mimi-git, busking-git, xdg-utils-git, linopen, xdg-utils-handlr, xdg-utils-slock, mimi-bachoseven-git, xdg-utils-symlink-fix, mimejs-git, xdg-utils-mimeo, xdg-utils-lxqt, opener) (optional) – for "Launch Dropbox Website" and file manager integration
Required by (18)
- caja-dropbox (optional)
- dropbox-cli
- dropbox-fix
- dropbox-fix2
- dropbox-index-svn
- dropbox-kde-systray-icons
- dropbox-light-icons-git
- dropbox-plasma-dark-icons-git
- dropbox-plasma-light-icons-git
- nautilus-dropbox
- nemo-dropbox
- nemo-dropbox-git
- nitrotasks (optional)
- python-git-remote-dropbox-git
- python2-git-remote-dropbox-git
- spacefm-dropbox-plugin
- thunar-dropbox-git
- ynab4 (optional)
Sources (8)
- dropbox.service
- dropbox@.service
- DropboxGlyph_Blue.svg
- https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86-150.4.5000.tar.gz
- https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86-150.4.5000.tar.gz.asc
- https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86_64-150.4.5000.tar.gz
- https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86_64-150.4.5000.tar.gz.asc
- terms.txt
Latest Comments
bob418 commented on 2022-04-13 23:24 (UTC)
chovy commented on 2021-12-08 03:24 (UTC)
-> Flagged Out Of Date AUR Packages: dropbox
i716 commented on 2021-12-04 09:45 (UTC) (edited on 2021-12-16 09:35 (UTC) by i716)
Update to the latest version of dropbox has failed. dropbox 135.4.4221-1 (131.4.3968-1) AUR
==> Verifying source file signatures with gpg... dropbox-lnx.x86_64-135.4.4221.tar.gz ... cat: write error: Broken pipe FAILED ==> ERROR: One or more PGP signatures could not be verified!
The key has already been imported when dropbox was first installed. Therefore trying to re-add it doesn't change anything.
wget https://linux.dropbox.com/fedora/rpm-public-key.asc
gpg --import ~/Downloads/rpm-public-key.asc ✔ gpg: key FC918B335044912E: "Dropbox Automatic Signing Key linux@dropbox.com" not changed gpg: Total number processed: 1 gpg: unchanged: 1
FIXED: Sorry, my mistake, I was trying to build w/ sudo. Ran again as normal user and problem solved.
jhossbach commented on 2021-11-30 10:36 (UTC)
@mtorromeo: Could you add the argument -f to the gendesk so that previous .desktop files are overwritten? That solves @jfly's problem.
jfly commented on 2021-11-30 02:49 (UTC) (edited on 2021-11-30 02:51 (UTC) by jfly)
Anyone else seeing this error when installing?
==> Starting prepare()...
[dropbox] Generating desktop file... no
dropbox.desktop already exists. Use -f as the first argument to overwrite it.
==> ERROR: A failure occurred in prepare().
I've worked around this for now by commenting out the prepare
block.
Edit: Sorry, I didn't look back in the history! I see this was mentioned way back in 2020: https://aur.archlinux.org/packages/dropbox/?O=20&PP=10#comment-754071
jhossbach commented on 2021-09-09 20:12 (UTC)
@acyment: The dropbox-lnx.x86_64-130.4.4978.tar.gz
file didn't pass the validity check. Try pulling the AUR repo again, run makepkg again, see if that works.
If not, run makepkg --geninteg
and compare the sha256sums with the ones in the PKGBUILD.
acyment commented on 2021-09-09 13:09 (UTC) (edited on 2021-09-09 13:10 (UTC) by acyment)
Similar to what others have commented, I am now getting this error:
dropbox@.service ... Passed
==> Validating source_x86_64 files with sha256sums...
dropbox-lnx.x86_64-130.4.4978.tar.gz ... FAILED
dropbox-lnx.x86_64-130.4.4978.tar.gz.asc ... Skipped
==> ERROR: One or more files did not pass the validity check!
Error: Failed to build dropbox
moormaster commented on 2021-06-22 18:58 (UTC) (edited on 2021-06-22 18:59 (UTC) by moormaster)
gpg --keyserver hkp://pgp.mit.edu --recv-keys FC918B335044912E
works for me as suggested here https://forum.endeavouros.com/t/dropbox-install-from-aur/1871
StormEngineer commented on 2021-05-10 00:39 (UTC)
This is still an issue today: https://aur.archlinux.org/packages/dropbox/?O=20&PP=10#comment-754071
xavierbaez commented on 2021-05-03 21:08 (UTC)
I think this package needs to be upgraded to version
121.4.4267-1
xavierbaez commented on 2021-05-03 20:44 (UTC)
My dropbox says it's not the latest version I have package dropbox 120.4.4598-1 Dropbox Linux version 96.4.172
ghen commented on 2021-05-03 14:22 (UTC)
The dropbox client is auto-updating in your homedir, see https://wiki.archlinux.org/title/Dropbox#Prevent_automatic_updates
pedrorafael commented on 2021-04-23 13:58 (UTC)
The program does not open on gnome 40.
pedrorafael commented on 2021-04-23 13:58 (UTC)
The program does not open on gnome 40.
xuanruiqi commented on 2020-12-02 15:22 (UTC)
No update?
wooque commented on 2020-10-06 09:05 (UTC)
Same here, had to download and import key manually
pitlochry commented on 2020-10-06 08:51 (UTC)
I can confirm, that (using yay without sudo)
gpg --recv-keys 1C61A2656FB57B7E4DE0F4C1FC918B335044912E
does not work. Only downloading directly from https://linux.dropbox.com/fedora/rpm-public-key.asc and adding with
gpg --import rpm-public-key.asc
works. Can the PKGBUILD be updated with this?
cavernico commented on 2020-10-02 14:44 (UTC) (edited on 2020-10-02 14:51 (UTC) by cavernico)
in several machines the command
gpg --recv-keys 1C61A2656FB57B7E4DE0F4C1FC918B335044912E
wont work...
only downloading directrly from https://linux.dropbox.com/fedora/rpm-public-key.asc and add with:
gpg --import rpm-public-key.asc
Can the PKGBUILD be updated with this?
gothicVI commented on 2020-09-19 06:48 (UTC)
@Kunda download working fine for me. Check any firewall, proxy, VPN settings. Also try the link via browser.
Kunda commented on 2020-09-19 04:05 (UTC)
Building dropbox...
==> Making package: dropbox 105.4.651-1 (Sat 19 Sep 2020 12:02:31 AM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found DropboxGlyph_Blue.svg
-> Found terms.txt
-> Found dropbox.service
-> Found dropbox@.service
-> Downloading dropbox-lnx.x86_64-105.4.651.tar.gz...
** Resuming transfer from byte position 101001773
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 49 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 416
==> ERROR: Failure while downloading https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86_64-105.4.651.tar.gz
Aborting...
Failed to build dropbox
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=20.1
DISTRIB_CODENAME=Mikah
DISTRIB_DESCRIPTION="Manjaro Linux"
gothicVI commented on 2020-09-18 21:09 (UTC)
@idanka: are you using a AUR helper like yay or alike? If so, do not run them as root! Also do import the keys as user not as root.
idanka commented on 2020-09-18 21:05 (UTC)
@ gothicVI I use Manjaro Gnome 20.1 pamac gtk 9.5.10-1/ aur / install dropbox 105 ... / Build error pgp
terminal: sudo -s
gpg --recv-keys 1C61A2656FB57B7E4DE0F4C1FC918B335044912E
gpg: keyserver receive failed: General error
downloads rpm-public-key.asc
gpg --import rpm-public-key.asc
gpg: key FC918B335044912E: "Dropbox Automatic Signing Key linux@dropbox.com" not changed gpg: Total number processed: 1 gpg: unchanged: 1
Sry, but aur error output not Englist.
gothicVI commented on 2020-09-18 20:45 (UTC)
@idanka: how are you trying to install? Provide a bit more information.
idanka commented on 2020-09-18 19:57 (UTC)
yan12125 "Run the following command in case you got errors during "Verifying source file signatures with gpg..."
Sry, but not works "ERROR: One or more files did not pass the validity check! Failed to build dropbox"
dolour commented on 2020-09-14 09:39 (UTC)
Tray icon no longer visible since todays update. Otherwise it seems to run fine tho.
albuntu commented on 2020-09-04 17:05 (UTC) (edited on 2020-09-04 17:06 (UTC) by albuntu)
I have (a) problem(s): Although I imported the key via 'sudo gpg --import rpm-public-key.asc' Dropbox will not be installed: ... ==> Überprüfe Signaturen der Quell-Dateien mit gpg... dropbox-lnx.x86_64-104.4.175.tar.gz ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel FC918B335044912E) ==> FEHLER: Eine oder mehrere PGP-Signaturen konnten nicht überprüft werden! Fehler beim Erstellen von dropbox ... What can I do?
brandon.arnold commented on 2020-08-26 19:23 (UTC)
@wooque I guess the dropbox tray picks up different methods of showing generating the sign in link, then, depending on the environment. For me, it did not work until I installed Qt5, and qt5-base is one method out of quite a few of doing that. I'm sure GTK is also adequate.
wooque commented on 2020-08-26 07:46 (UTC)
I don't have qt5-base neither and I just successfully signed in my account
brandon.arnold commented on 2020-08-26 05:29 (UTC) (edited on 2020-08-26 05:29 (UTC) by brandon.arnold)
I recommend adding qt5-base as a dependency. The Sign In dialog doesn't work without Qt5, which I just learned trying to get this package to work in my i3 system tray.
thebombzen commented on 2020-08-08 14:58 (UTC) (edited on 2020-08-08 14:58 (UTC) by thebombzen)
@eisterman This exact issue has already been explained to the maintainer, who refuses to fix this problem. The maintainer of this package seems to believe, incorrectly, that the -f
flag is not what people want.
yfc commented on 2020-08-08 14:02 (UTC)
@yan12125 and @jerz4evr Finally got Dropbox installed. Thanks so much for your help!
Devastator commented on 2020-07-05 13:39 (UTC) (edited on 2020-07-05 13:42 (UTC) by Devastator)
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 (UTC) (edited on 2020-07-02 00:14 (UTC) by eisterman)
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 (UTC) (edited on 2020-06-17 19:29 (UTC) by varunsbhatta)
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 (UTC)
@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 (UTC) (edited on 2020-06-05 14:51 (UTC) by nthorderindex)
@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: https://github.com/fosskers/aura/blob/master/aura/CHANGELOG.md#311-2020-06-02
gothicVI commented on 2020-06-05 05:34 (UTC) (edited on 2020-06-05 05:34 (UTC) by gothicVI)
@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 (UTC)
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 (UTC) (edited on 2020-05-31 02:39 (UTC) by jerz4evr)
An single command to fix the errors with file signature verification as referenced by yan12125's comment is the following:
curl https://linux.dropbox.com/fedora/rpm-public-key.asc | 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 (UTC)
@Groumpf: Thanks a lot! That actually does the trick...
Groumpf commented on 2020-05-21 15:54 (UTC)
@gothicVI: I accidentally ran pikaur
as root and got your error message. Try running pikaur
as a normal user.
gothicVI commented on 2020-03-30 12:26 (UTC)
Running makepkg
and makepkg --install
on the snapshot did the trick. There seems to be something wrong with pikaur
I'll need to investigate...
gothicVI commented on 2020-03-29 12:35 (UTC)
Hi, the update from version 92.4.382-1 -> 93.4.273-1 fails with:
:: Starte den Buildvorgang:
Job for run-u136.service failed because the control process exited with error code.
See "systemctl status run-u136.service" and "journalctl -xe" for details.
Ausführung des Befehls 'systemd-run --service-type=oneshot --pipe --wait --pty -p DynamicUser=yes -p CacheDirectory=pikaur -E HOME=/tmp -p WorkingDirectory=/var/cache/pikaur/build/dropbox makepkg --force' ist fehlgeschlagen.
:: Versuchen, wiederherzustellen?
[R] Build nochmal versuchen
[p] überspringe PGP-Signaturprüfung
[c] überspringe Checksummen-Prüfung
[i] ignoriere Architektur
[d] entferne Build-Verzeichnis und versuche erneut
[e] edit PKGBUILD
------------------------
[u] überspringe Build dieses Pakets
[a] bauen aller Pakete abbrechen
where
systemctl status run-u136.service
● run-u136.service - /usr/bin/makepkg --force
Loaded: loaded (/run/systemd/transient/run-u136.service; transient)
Transient: yes
Active: failed (Result: exit-code) since Sun 2020-03-29 14:25:47 CEST; 4min 27s ago
Process: 3231 ExecStart=/usr/bin/makepkg --force (code=exited, status=1/FAILURE)
Main PID: 3231 (code=exited, status=1/FAILURE)
Mär 29 14:25:26 ${HOSTNAME} systemd[1]: Starting /usr/bin/makepkg --force...
Mär 29 14:25:47 ${HOSTNAME} systemd[1]: run-u136.service: Main process exited, code=exited, status=1/FAILURE
Mär 29 14:25:47 ${HOSTNAME} systemd[1]: run-u136.service: Failed with result 'exit-code'.
Mär 29 14:25:47 ${HOSTNAME} systemd[1]: Failed to start /usr/bin/makepkg --force.
and
journalctl -xe
Mär 29 14:26:51 ${HOSTNAME} kded5[1357]: Registering "org.kde.StatusNotifierItem-5501-2/StatusNotifierItem" to system tray
Mär 29 14:26:51 ${HOSTNAME} plasmashell[1444]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_391(0x55a649fdff80, parent=0x55a6493beb80, geometry=0,0 0x0) after StatusNotifi>
Mär 29 14:26:52 ${HOSTNAME} systemd[1]: run-u136.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- An ExecStart= process belonging to unit run-u136.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Mär 29 14:26:52 ${HOSTNAME} systemd[1]: run-u136.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- The unit run-u136.service has entered the 'failed' state with result 'exit-code'.
Mär 29 14:26:52 ${HOSTNAME} systemd[1]: Failed to start /usr/bin/makepkg --force.
-- Subject: A start job for unit run-u136.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
--
-- A start job for unit run-u136.service has finished with a failure.
--
-- The job identifier is 2492 and the job result is failed.
Mär 29 14:26:52 ${HOSTNAME} audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=run-u136 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? ad>
Mär 29 14:26:52 ${HOSTNAME} kernel: audit: type=1130 audit(1585484812.965:108): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=run-u136 comm="systemd" exe="/usr/lib/sy>
Mär 29 14:26:54 ${HOSTNAME} wpa_supplicant[1037]: wlo1: WPA: Group rekeying completed with 38:10:d5:32:86:99 [GTK=CCMP]
Mär 29 14:28:25 ${HOSTNAME} kwin_x11[1436]: Could not attach Keys property to: PlasmaQuick::Dialog(0x558b70338c80) is not an Item
Mär 29 14:28:25 ${HOSTNAME} kwin_x11[1436]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 22552, resource id: 37751024, major code: 3 (GetWindowAttributes), minor code: 0
Mär 29 14:28:25 ${HOSTNAME} kwin_x11[1436]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 22553, resource id: 37751024, major code: 14 (GetGeometry), minor code: 0
Mär 29 14:28:25 ${HOSTNAME} kwin_x11[1436]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 22556, resource id: 37751024, major code: 3 (GetWindowAttributes), minor code: 0
Mär 29 14:28:25 ${HOSTNAME} kwin_x11[1436]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 22557, resource id: 37751024, major code: 14 (GetGeometry), minor code: 0
Mär 29 14:28:29 ${HOSTNAME} sudo[2066]: pam_unix(sudo:session): session closed for user root
Mär 29 14:28:29 ${HOSTNAME} kernel: audit: type=1106 audit(1585484909.176:109): pid=2066 uid=0 auid=1000 ses=2 subj==unconfined msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_per>
Mär 29 14:28:29 ${HOSTNAME} kernel: audit: type=1104 audit(1585484909.176:110): pid=2066 uid=0 auid=1000 ses=2 subj==unconfined msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct=>
Mär 29 14:28:29 ${HOSTNAME} audit[2066]: USER_END pid=2066 uid=0 auid=1000 ses=2 subj==unconfined msg='op=PAM:session_close grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/>
Mär 29 14:28:29 ${HOSTNAME} audit[2066]: CRED_DISP pid=2066 uid=0 auid=1000 ses=2 subj==unconfined msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env acct="root" exe="/usr/bin/sudo" ho>
Mär 29 14:29:45 ${HOSTNAME} kwin_x11[1436]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 36756, resource id: 37751044, major code: 20 (GetProperty), minor code: 0
Do you need any additional information?
ordtrogen commented on 2020-02-29 09:03 (UTC)
When I get the error in
Starting prepare()
which has been the case for quite a while, I do
rm src/dropbox.desktop
and since I initiated the process with makepkg -si, I issue that command again. YMMV
nipsky commented on 2020-02-28 20:30 (UTC)
Hi, for the last few versions, I’m getting the following error:
==> Starting prepare()...
[dropbox] Generating desktop file... no
dropbox.desktop already exists. Use -f as the first argument to gendesk to overwrite.
==> ERROR: A failure occurred in prepare().
Aborting...
fra-san commented on 2020-01-24 18:32 (UTC)
@jomority No problem, it would be unreasonable to require everybody to read hundreds of comments before posting anything. Maybe we (I, at least) should add a few notes about the Dropbox startup process to the Wiki.
jomority commented on 2020-01-24 17:17 (UTC) (edited on 2020-01-24 17:20 (UTC) by jomority)
@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.
fra-san commented on 2020-01-24 16:39 (UTC) (edited on 2020-01-24 16:59 (UTC) by fra-san)
@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
.
jomority commented on 2020-01-24 15:35 (UTC)
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.
dlezo commented on 2020-01-11 13:56 (UTC)
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.
friday13 commented on 2019-12-25 14:11 (UTC) (edited on 2019-12-25 14:12 (UTC) by friday13)
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.
servimo commented on 2019-12-12 14:51 (UTC) (edited on 2019-12-19 11:47 (UTC) by servimo)
I could not run dropbox, it gives me this error: "thread panicked while processing panic. aborting. Segmentation faul (core image recorded)"
ranger commented on 2019-12-11 23:39 (UTC)
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.
thebombzen commented on 2019-12-11 23:34 (UTC)
@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.
asakurahao commented on 2019-12-09 23:07 (UTC)
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?
ranger commented on 2019-12-04 09:11 (UTC)
@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.
nyanpasu64 commented on 2019-12-04 05:52 (UTC)
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?
ranger commented on 2019-11-22 19:42 (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.
thebombzen commented on 2019-11-22 14:12 (UTC)
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.
jango commented on 2019-11-18 07:32 (UTC)
If you use dolphin file manager install this addons "dolphin-plugins" to see the folder status
Achilleus commented on 2019-11-13 23:04 (UTC) (edited on 2019-11-13 23:05 (UTC) by Achilleus)
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)
Zwenn76 commented on 2019-11-03 09:28 (UTC)
@ranger Thank you and sorry for posting here. I should have read the archwiki thoroughly.. But yes I can confirm that this workaround works.
ranger commented on 2019-11-03 09:11 (UTC)
@Zwenn76 You have to disable Dropbox auto update.
https://wiki.archlinux.org/index.php/Dropbox#Prevent_automatic_updates
Zwenn76 commented on 2019-11-03 09:07 (UTC)
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?
rohit275 commented on 2019-11-02 00:46 (UTC)
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.
DenisBY commented on 2019-10-08 09:34 (UTC) (edited on 2019-10-08 10:00 (UTC) by DenisBY)
@fra-san Here is a link to deb https://www.dropbox.com/download?dl=packages/ubuntu/dropbox_2019.02.14_amd64.deb Also this page (https://www.dropbox.com/desktop) says that "The new desktop experience will be updated for Dropbox desktop users over the next few weeks." https://help.dropbox.com/installs-integrations/desktop/desktop-application-overview
UPDATE: yes, you are right. it seems it contains "a command-line tool and a Nautilus extension that integrates the Dropbox web service with your GNOME Desktop."
fra-san commented on 2019-10-08 09:05 (UTC) (edited on 2019-10-08 09:06 (UTC) by fra-san)
@DenisBY It looks like 2019.02.04
is the latest version of nautilus-dropbox
, not that of Dropbox itself.
The list of Dropbox builds at https://www.dropboxforum.com/t5/Desktop-client-builds/bd-p/101003016 confirms that the one linked in the "Source" section above (82.4.155
) is the most recent stable one.
DenisBY commented on 2019-10-08 07:06 (UTC) (edited on 2019-10-08 07:07 (UTC) by DenisBY)
There is new version of Dropbox client available (2019.x) https://www.dropbox.com/install Could we expect AUR for this version? Thanks
markxnelson commented on 2019-09-23 01:18 (UTC)
Hi, The tray icon does not work well for me. It does appear, and it changes to the "syncing" icon for a short time, then goes back to normal. I cannot click on it (left/right) - no menu is ever shown, so I cannot interact with the dropbox program.
nTia89 commented on 2019-09-17 08:40 (UTC) (edited on 2019-09-23 07:25 (UTC) by nTia89)
I have an issue with SVG icon provided:
I used to change default icon with the SVG icon for my Dropbox folder.
Since last pacman upgrade file manager is no more able to show the SVG and thus place a blank icon in place of that.
Now, I think SVG we provide has a problem, because opening and saving it with Inkscape or LibreOffice Draw, makes it "working" again.
Now, I am not an expert but size before and after that re-saving changes from 605 Bytes to 4.9 KB and it's strange... maybe we provide a malformed SVG? because also the thumbnail os SVG itself is empty but image viewer opens it correctly!
EDIT: also .desktop icon fails to load: I use gnome-shell and icon disappeared from the launcher (but I can still launch it normally)
EDIT2: here is a screenshot [https://imgur.com/a/0okULXY]
zman0900 commented on 2019-09-13 18:30 (UTC)
If the 'prepare' section is re-ran without first cleaning out the build directory, the gendesk command errors:
dropbox.desktop already exists. Use -f as the first argument to gendesk to overwrite.
Please add the '-f' argument.
interskh commented on 2019-09-10 07:08 (UTC)
Looks like i've got the same thing as @syrenity, but i don't use proxychains
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) [1] 9559 abort sudo dropbox
satriani commented on 2019-09-09 06:50 (UTC) (edited on 2019-09-09 06:50 (UTC) by satriani)
For all who have issue: ImportError: libdropbox_apex.so: cannot open shared object file: No such file or directory
sudo chmod 755 /opt/dropbox/libdropbox_apex.so
https://forum.manjaro.org/t/solved-dropbox-importerror-fatal-python-exception/101922
brownbear404 commented on 2019-09-08 17:49 (UTC)
The "selective sync" button does not seem to do anything. Does someone else face similar issue? Seems to be a problem with the latest builds: https://www.dropboxforum.com/t5/Installs-integrations/The-selective-sync-dialog-doesn-t-show-up-on-Linux/m-p/362822#M76488
chapa commented on 2019-09-08 10:44 (UTC)
If you have message " libdropbox_apex.so: cannot open shared object file: No such file or directory\n'] (error 3)"
Fix it sudo chmod 755 /opt/dropbox/libdropbox_apex.so
ambra commented on 2019-09-07 21:03 (UTC)
You need to:
chmod go+r libdropbox_apex.so
in order to start dropboxd.
Tio commented on 2019-09-07 11:35 (UTC)
@wooque Indeed. Sorry. Ok, it works now. Thank you!
wooque commented on 2019-09-07 11:33 (UTC) (edited on 2019-09-07 11:33 (UTC) by wooque)
as servimo said
sudo chmod 755 /opt/dropbox/libdropbox_apex.so
will fix the issue
Tio commented on 2019-09-07 11:15 (UTC)
I am using Manjaro Gnome. So, what can I do?
servimo commented on 2019-09-07 11:12 (UTC) (edited on 2019-09-07 11:13 (UTC) by servimo)
I just changed the permissions of "libdropbox_apex.so" and it is working. It's permissions was to only root could read or write.
Tio commented on 2019-09-07 11:09 (UTC)
After the last update it doesn't work anymore:
[tio@tio-pc ~]$ dropbox
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-htKc54
dropbox: initializing
dropbox: initializing python 3.7.2
dropbox: setting program path '/opt/dropbox/dropbox'
dropbox: setting home path '/opt/dropbox'
dropbox: setting python path '/opt/dropbox:/opt/dropbox/python-packages-37.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/linuxffi.pthread._linuxffi_pthread.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/cpuid.compiled._cpuid.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/opt/dropbox/apex._apex.cpython-37m-x86_64-linux-gnu.so'
Traceback (most recent call last):
File "dropbox/client/main.pyc", line 18, in <module>
File "dropbox/client/features/catalina_migration/catalina_migration_controller.pyc", line 19, in <module>
File "dropbox/client/features/catalina_migration/catalina_account_context.pyc", line 13, in <module>
File "dropbox/client/features/catalina_migration/alert_dialog.pyc", line 10, in <module>
File "dropbox/client/features/file_locking/base_file_locking_alert.pyc", line 14, in <module>
File "dropbox/client/features/legacy_ui_launcher.pyc", line 21, in <module>
File "dropbox/client/configuration/manager.pyc", line 45, in <module>
File "dropbox/client/configuration/utils.pyc", line 27, in <module>
File "dropbox/client/notifications/loud_notifications/do_not_disturb/model.pyc", line 51, in <module>
File "ui/common/preferences.pyc", line 21, in <module>
File "dropbox/client/authentication/manager.pyc", line 36, in <module>
File "dropbox/client/authentication/control_flow_helpers.pyc", line 3, in <module>
File "dropbox/client/high_trace.pyc", line 53, in <module>
File "dropbox/client/logging/dbxlog_logger.pyc", line 11, in <module>
File "apex/dbxlog.pyc", line 14, in <module>
File "<_bootstrap_overrides>", line 153, in load_module
ImportError: libdropbox_apex.so: cannot open shared object file: No such file or directory
!! dropbox: fatal python exception:
['Traceback (most recent call last):\n', ' File "dropbox/client/main.pyc", line 18, in <module>\n', ' File "dropbox/client/features/catalina_migration/catalina_migration_controller.pyc", line 19, in <module>\n', ' File "dropbox/client/features/catalina_migration/catalina_account_context.pyc", line 13, in <module>\n', ' File "dropbox/client/features/catalina_migration/alert_dialog.pyc", line 10, in <module>\n', ' File "dropbox/client/features/file_locking/base_file_locking_alert.pyc", line 14, in <module>\n', ' File "dropbox/client/features/legacy_ui_launcher.pyc", line 21, in <module>\n', ' File "dropbox/client/configuration/manager.pyc", line 45, in <module>\n', ' File "dropbox/client/configuration/utils.pyc", line 27, in <module>\n', ' File "dropbox/client/notifications/loud_notifications/do_not_disturb/model.pyc", line 51, in <module>\n', ' File "ui/common/preferences.pyc", line 21, in <module>\n', ' File "dropbox/client/authentication/manager.pyc", line 36, in <module>\n', ' File "dropbox/client/authentication/control_flow_helpers.pyc", line 3, in <module>\n', ' File "dropbox/client/high_trace.pyc", line 53, in <module>\n', ' File "dropbox/client/logging/dbxlog_logger.pyc", line 11, in <module>\n', ' File "apex/dbxlog.pyc", line 14, in <module>\n', ' File "<_bootstrap_overrides>", line 153, in load_module\n', 'ImportError: libdropbox_apex.so: cannot open shared object file: No such file or directory\n'] (error 3)
Aborted (core dumped)
commented on 2019-09-07 09:02 (UTC)
Same problem as @wooque. The issue is that apex._apex.cpython-37m-x86_64-linux-gnu.so
depends on libdropbox_apex.so
that cannot be loaded even if it is available in the same directory.
wooque commented on 2019-09-07 08:45 (UTC) (edited on 2019-09-07 08:45 (UTC) by wooque)
Dropbox 80.4.126 fails to start with this error
ImportError: libdropbox_apex.so: cannot open shared object file: No such file or directory !! dropbox: fatal python exception: ['Traceback (most recent call last):\n', ' File "dropbox/client/main.pyc", line 18, in <module>\n', ' File "dropbox/client/features/catalina_migration/catalina_migration_controller.pyc", line 19, in <module>\n', ' File "dropbox/client/features/catalina_migration/catalina_account_context.pyc", line 13, in <module>\n', ' File "dropbox/client/features/catalina_migration/alert_dialog.pyc", line 10, in <module>\n', ' File "dropbox/client/features/file_locking/base_file_locking_alert.pyc", line 14, in <module>\n', ' File "dropbox/client/features/legacy_ui_launcher.pyc", line 21, in <module>\n', ' File "dropbox/client/configuration/manager.pyc", line 45, in <module>\n', ' File "dropbox/client/configuration/utils.pyc", line 27, in <module>\n', ' File "dropbox/client/notifications/loud_notifications/do_not_disturb/model.pyc", line 51, in <module>\n', ' File "ui/common/preferences.pyc", line 21, in <module>\n', ' File "dropbox/client/authentication/manager.pyc", line 36, in <module>\n', ' File "dropbox/client/authentication/control_flow_helpers.pyc", line 3, in <module>\n', ' File "dropbox/client/high_trace.pyc", line 53, in <module>\n', ' File "dropbox/client/logging/dbxlog_logger.pyc", line 11, in <module>\n', ' File "apex/dbxlog.pyc", line 14, in <module>\n', ' File "<_bootstrap_overrides>", line 153, in load_module\n', 'ImportError: libdropbox_apex.so: cannot open shared object file: No such file or directory\n'] (error 3) zsh: abort (core dumped) dropbox
libdropbox_apex is located at /opt/dropbox/libdropbox_apex.so
johnny_boy commented on 2019-09-03 12:36 (UTC)
When I pause syncing, dropbox almost always crashes after a period of time. This has been happening for some time. Anyone else?
dolour commented on 2019-07-24 12:45 (UTC) (edited on 2019-07-24 12:45 (UTC) by dolour)
Dropbox is now spawning 2 tray icons after bootup, and creates another one for every click you perform on any of those icons. And those icons are getting plenteous very quickly...
wooque commented on 2019-07-20 10:45 (UTC)
After 77.4.131-1 update Dropbox is using monospace font for interface, which is ugly
obelix1502 commented on 2019-07-17 15:30 (UTC)
I've the same issue when I try to install firefox-nightly-fr :
$ gpg --recv-keys FC918B335044912E
gpg: connecting dirmngr at '/run/user/1000/gnupg/S.dirmngr' failed: Échec de l'appel IPC connect
gpg: échec de réception depuis le serveur de clefs : Pas de dirmngr
Someone could help me ?
stratosgear commented on 2019-06-14 09:14 (UTC)
Similar to @walkindude:
gendesk: error while loading shared libraries: libgo.so.14: cannot open shared object file: No such file or directory
==> ERROR: A failure occurred in prepare().
Aborting...
Error making: dropbox
walkindude commented on 2019-06-06 20:18 (UTC)
gendesk: error while loading shared libraries: libgo.so.13: cannot open shared object file: No such file or directory
getzze commented on 2019-05-17 08:43 (UTC)
For the systemd service to be working correctly (stop and restart commands), you need to change the type from simple
to forking
:
[Service]
Type=forking
jessymilare commented on 2019-05-17 03:29 (UTC) (edited on 2019-05-17 03:29 (UTC) by jessymilare)
I get the same error as @acdw. Adding '-f' to gendesk in PKGCONFIG worked, although I had also to install dropbox-filesystem-fix from https://github.com/dark/dropbox-filesystem-fix
Thaodan commented on 2019-05-01 16:39 (UTC)
Why libappindicator-gtk3 for plasma? Plasma supports the StatusNotifer spec out of the box and dropbox is no GTK app.
PRafael commented on 2019-04-26 15:42 (UTC)
Thank you for your time. Grat job.
Regards Paulo
jahismighty commented on 2019-04-19 14:43 (UTC)
@acdw: as a hacky workaround you can modify PKGBUILD and add the specified flag (-f) to the gendesk command in the prepare() function.
Morganamilo commented on 2019-04-11 20:36 (UTC)
mksrcinfo
is old and defunct but still being used on this package. This means some fields like pgp keys don't show up in the srcinfo even though they should.
Please use makepkg --printsrcinfo
instead.
acdw commented on 2019-04-11 12:27 (UTC)
I get the following error when trying to install:
dropbox.desktop already exists. Use -f as the first argument to gendesk to overwrite.
It's during the prepare() stage of installation. It aborts the install.
michaldybczak commented on 2019-04-05 18:54 (UTC)
Thanks, now it works :).
mtorromeo commented on 2019-04-04 20:46 (UTC)
Download issue fixed
figue commented on 2019-04-04 20:35 (UTC)
Here you have my forked package as I said before:
https://github.com/figue/aur/tree/master/dropbox-latest
The other one is not maintained by me.
michaldybczak commented on 2019-04-04 20:00 (UTC)
Not possible to install, something is wrong with the download link:
==> ERROR: Error during download https://uc3Przerywam135348e74c66f0669fcde8300.dl.dropboxusercontent.com/cd/0/get/AeYRisQv-6SKLfc95CgynP5ZP_DyMV9YC331Th6iimSA9YFsQiTzZl3lg_osmwitILJ5H9MPDlgVpfI0O2CzvZUEGcJdyA7jfEiX6cckYH7W4Q/file?_download_id=385426155243517642556452976793408572138269034287425082593540433136&_notify_domain=www.dropbox.com&dl=1 Aborting... :: Unable to build dropbox - makepkg exited with code: 1
rcrath commented on 2019-04-04 19:41 (UTC)
Not installing: get error as follows.
curl: (22) The requested URL returned error: 403 ==> ERROR: Failure while downloading https://uc3135348e74c66f0669fcde8300.dl.dropboxusercontent.com/cd/0/get/AeYRisQv-6SKLfc95CgynP5ZP_DyMV9YC331Th6iimSA9YFsQiTzZl3lg_osmwitILJ5H9MPDlgVpfI0O2CzvZUEGcJdyA7jfEiX6cckYH7W4Q/file?_download_id=385426155243517642556452976793408572138269034287425082593540433136&_notify_domain=www.dropbox.com&dl=1 Aborting... ==> ERROR: Makepkg was unable to build dropbox.
figue commented on 2019-04-04 10:51 (UTC)
@wooque I wrote some time ago a fork of this package that always download the latest version of Dropbox, unfortunately it was removed from AUR and I can't find it on my work PC. But, I found this project in github that use the same idea. With it, you can install always the latest version:
wooque commented on 2019-04-03 12:11 (UTC)
@mtorromeo is there a chance that package will be updated
vader23 commented on 2019-03-28 15:55 (UTC)
The simplest and best way: https://www.dropbox.com/install-linux
yan12125 commented on 2019-03-18 04:01 (UTC)
Disowning this package as I haven't used Dropbox for a long time.
yan12125 commented on 2019-03-18 03:53 (UTC) (edited on 2019-03-18 04:02 (UTC) by yan12125)
@leonardof The last file is already removed in commit 3db0f6a54245
. That's one of reasons I suggest people to clean AUR package repos before building packages.
leonardof commented on 2019-03-16 21:08 (UTC)
Thanks for the answer, @yan12125. I never knew extra-x86_64-build
existed, let alone that it was the recommended command for building packages from AUR.
With regard to copying, I just presumed the file on outside src/
was a copy because there is another one inside:
$ find . -name dropbox.desktop
./pkg/dropbox/usr/share/applications/dropbox.desktop
./src/dropbox.desktop
./dropbox.desktop
yan12125 commented on 2019-03-16 15:57 (UTC)
The best way is extra-x86_64-build
. If you want to stick with makepkg, clean the folder first. For example, git pull && git clean -dfx && makepkg
.
By the way, dropbox.desktop is generated by gendesk. I'm not sure what you mean by "copying over the file from within src/".
leonardof commented on 2019-03-16 13:21 (UTC)
I don't use any AUR helper: I have a clone of <https://aur.archlinux.org/dropbox.git>
where I run git pull
, makepkg
and pacman -U
to update the package. That't the recommended way, right?
For a while now, makepkg
fails because of a leftover dropbox.desktop
. I have to delete the file, which is again copied from src/
by makepkg
, and again I have to delete the file the next time I update.
Please stop copying over the file from within src/
, or at least make it so that the package can be updated without the user manually deleting the file.
Thanks in advance!
yan12125 commented on 2019-03-15 03:15 (UTC)
Sorry for the last unnecessary pkgrel bumping - there's a bug in my script and I've fixed it.
@zman0900: That's a bug of pacaur - report it there. @syrenity: Are you using proxychains with dropbox? If so it's a known issue [1] and I think only Dropbox developers can fix it.
zman0900 commented on 2019-03-14 21:21 (UTC)
Could the gendesk
command be moved to a build() function? Some aur helpers (pacaur at least) do not install makedepends until after prepare() has been ran, so prepare() fails if I don't manually install gendesk first.
syrenity commented on 2019-03-10 09:07 (UTC)
Getting following error on latest version:
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)
The headless version from Dropbox site works fine.
Fenrihr commented on 2019-02-27 00:40 (UTC)
i'm getting the error "Verifying source file signatures with sha256sums..." with dropbox-lnx.x86_64-67.4.83.tar.gz
i import the gpg keys but keep getting the same error
yan12125 commented on 2019-02-25 04:06 (UTC)
@sercans: Thank you very much for the comment! optdepends updated.
sercans commented on 2019-02-22 20:26 (UTC)
@yan12125 kde plasma needs libappindicator-gtk3 to show themed tray icons. libappindicator-gtk3 package can be in optdepends.
i could not make xfce to show themed tray icon with libappindicator-gtk2 or libappindicator-gtk3
yan12125 commented on 2019-02-10 07:14 (UTC)
Sorry for the delay - I was on the Chinese New Year vacation last week :)
anks commented on 2019-02-10 02:58 (UTC)
This package needs an update. Running old version cause high CPU on some setups. @yan12125
arunkhattri commented on 2019-01-26 05:53 (UTC)
How to set the preferences? I am not getting any menu for dropbox as suggested in many wiki's /blogs.
have installed in Dell Vostro 15 3000 series Version: 65.4.177-2 Architecture: x86_64
yan12125 commented on 2019-01-09 03:44 (UTC)
Dropbox 64 fixes tray icon on XFCE, LXDE, MATE and Gnome. I guess more dependencies are necessary as the release note [1] mentions libappindicator. Please tell me if you got the tray icon work with extra packages and I'll add them to optdepends.
[1] https://www.dropboxforum.com/t5/Desktop-client-builds/Stable-Build-64-4-141/m-p/322084#M5164
yan12125 commented on 2019-01-06 10:28 (UTC)
@amatriain: in my experience pgp.mit.edu is unstable. You may want to choose another keyserver or download Dropbox's public key manually (see the updated pinned comment).
amatriain commented on 2019-01-06 09:14 (UTC)
I'm getting an error when importing the gpg key:
$ gpg --recv-keys 1C61A2656FB57B7E4DE0F4C1FC918B335044912E gpg: no valid OpenPGP data found.
Also when I search the key in pgp.mit.edu I get no results. Maybe it's been revoked?
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-12-29 00:42 (UTC)
Thank you @alex.forencich! I made your comment pinned.
alex.forencich commented on 2018-12-28 22:48 (UTC)
Install this package if you need to run dropbox on a non-ext4 filesystem: https://aur.archlinux.org/packages/dropbox-fix/
This should work when running dropbox from the command line and as a service.
alex.forencich commented on 2018-12-28 22:14 (UTC)
Yeah, I suppose that's a good point, it would be possible to make a separate package that provides the .so file, the override wrapper script, and the override systemd unit file.
yan12125 commented on 2018-12-19 08:24 (UTC)
Regarding incompatibility with non-EXT4 filesystems: I don't think using existing "patches" [1][2] requires modifications to this package. Propose your modified PKGBUILD if you believe so.
[1] https://github.com/dark/dropbox-filesystem-fix/ [2] https://github.com/dimaryaz/dropbox_ext4/
Galaxy commented on 2018-12-18 13:59 (UTC)
Would you include this patch to allow it running on other fs ?
yan12125 commented on 2018-12-13 02:15 (UTC)
@netlexer: Thanks for notifying me. That should have been fixed.
netlexer commented on 2018-12-13 01:54 (UTC) (edited on 2018-12-13 01:58 (UTC) by netlexer)
Did a newer version briefly become available via the AUR and then reverted? Yay, my package manager states:
dropbox: local (63.4.100-1) is newer than AUR (62.4.103-1)
which I don't think I've seen before. And if so why?
Is it OK to keep this newer version?
yan12125 commented on 2018-12-02 01:42 (UTC)
@InvisibleRasta: it looks like a wrapper script calling the actual binary. There's nothing to do with this package.
commented on 2018-12-02 00:53 (UTC)
yan12125 commented on 2018-12-01 00:54 (UTC)
@ncage: Awesome!
@InvisibleRasta: which patch did you refer? If the one mentioned by @alex.forencich - it's reported to be broken, and it patches the dropbox-cli package, not this one.
ncage commented on 2018-12-01 00:01 (UTC)
@yan1212 thanks for the reply. After much research i found out its actually a dropbox/gnome issue. It has been broken since gnome 3.28. I spelled out the details at: https://www.dropboxforum.com/t5/Installation-and-desktop-app/Latest-Dropbox-Client-for-Linux-is-broken-for-the-latest-version/m-p/314765#M57918
commented on 2018-11-29 03:01 (UTC)
would it be possible for you to add the unsupported filesystem patch to this
yan12125 commented on 2018-11-13 12:07 (UTC)
@ncage: most likely you need to install optional dependencies of this package - perl-file-mimeinfo and/or xdg-utils. Running dropbox
from a terminal should help you diagnose the problem, too.
ncage commented on 2018-11-13 02:00 (UTC)
Everything is working except when i click "Open Dropbox Folder" menu item. I'm running gnome. Anyone have a clue?
yan12125 commented on 2018-11-10 02:20 (UTC)
@alex.forencich: Did you test it? Looks like it has been broken some time per https://github.com/dimaryaz/dropbox_ext4/issues/2
alex.forencich commented on 2018-11-08 07:33 (UTC)
This should be incorporated in to this package to keep dropbox working on non-ext4 filesystems: https://github.com/dimaryaz/dropbox_ext4 .
t.langlois commented on 2018-10-24 09:34 (UTC)
I'm receiving an advice from Dropbox in order to put the Dropbox folder on an ext4 partition but it is already the case. Is it a glitch in their type of partition detection scheme or are they sending this to all users ? If this is not the right place for this kind of question, tell me.
yan12125 commented on 2018-10-18 11:45 (UTC)
Thanks @fra-san for various test results. I'll keep this package as-is - no dropping dropbox@.service, no changes to dropbox.service.
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
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)
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.
parnmatt commented on 2018-06-20 14:45 (UTC)
I'm getting an error with the recent update; are you missing a file?
chmod: cannot access '/var/cache/pacman/pkg/dropbox25812/dropbox/pkg/dropbox/opt/dropbox/dropbox_py3': No such file or directory
sl13kp commented on 2018-06-20 14:00 (UTC)
chmod: impossibile accedere a '/tmp/yaourt-tmp-stefano/aur-dropbox/pkg/dropbox/opt/dropbox/dropbox_py3
afwlehmann commented on 2018-05-23 17:34 (UTC)
If I'm not mistaken then the current pkgrel
should be reset to 1 now that pkgver
was upgraded to 50.4.71.
yan12125 commented on 2018-05-09 08:00 (UTC)
49.4.68 is announced, anyway.
BTW, @jorgicio, how did you find the new URL before it's announced?
jorgicio commented on 2018-05-08 23:53 (UTC)
In fact, althought no news were published, the 49.4.68 is up. I'm now in Gentoo, I maintain the dropbox package on my overlay, and that version is up.
https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86-49.4.68.tar.gz https://clientupdates.dropboxstatic.com/dbx-releng/client/dropbox-lnx.x86_64-49.4.68.tar.gz
yan12125 commented on 2018-05-08 10:12 (UTC)
jorgicio flagged dropbox out-of-date on 2018-05-06 for the following reason:
Version 49.4.68 was just released.
After two days, there are still no news about 49.4.68 on https://www.dropboxforum.com/t5/Desktop-client-builds/bd-p/101003016, and https://www.dropbox.com/download?plat=lnx.x86_64 still points to 48.4.58. I guess Dropbox engineers do not consider 49.4.68 ready yet, so unflag out-of-date.
yan12125 commented on 2018-03-25 07:39 (UTC) (edited on 2018-06-05 05:54 (UTC) by yan12125)
Recently I removed !upx from options as support for upx is dropped in pacman-git. If you use upx and get errors, please open a new issue at https://gitlab.com/yan12125/aur or leave a comment in https://gitlab.com/yan12125/aur/issues/20
raumzeitkeks commented on 2018-03-05 13:50 (UTC)
@portaloffreedom Running
QT_QPA_PLATFORM=xcb dropbox
or - using the dropbox-cli package -
QT_QPA_PLATFORM=xcb dropbox-cli start
works for me.
portaloffreedom commented on 2018-03-03 13:04 (UTC)
Dropbox doesn't run on Wayland. Tried to force the xcb platform but it's completely ignoring my commands. Here is my terminal output:
$ dropbox -platform xcb
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-xwNXiB
dropbox: initializing
dropbox: initializing python 2.7.11
dropbox: setting program path '/opt/dropbox/dropbox'
dropbox: setting home path '/opt/dropbox'
dropbox: setting python path '/opt/dropbox:/opt/dropbox/python-packages-27.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._constant_time.so'
dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._openssl.so'
dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._padding.so'
dropbox: load fq extension '/opt/dropbox/psutil._psutil_linux.so'
dropbox: load fq extension '/opt/dropbox/psutil._psutil_posix.so'
dropbox: load fq extension '/opt/dropbox/linuxffi.pthread._linuxffi_pthread.so'
dropbox: load fq extension '/opt/dropbox/tornado.speedups.so'
dropbox: load fq extension '/opt/dropbox/cpuid.compiled._cpuid.so'
dropbox: load fq extension '/opt/dropbox/linuxffi.resolv.compiled._linuxffi_resolv.so'
dropbox: load fq extension '/opt/dropbox/posixffi.libc._posixffi_libc.so'
dropbox: load fq extension '/opt/dropbox/librsyncffi.compiled._librsyncffi.so'
dropbox: load fq extension '/opt/dropbox/linuxffi.sys.compiled._linuxffi_sys.so'
dropbox: load fq extension '/opt/dropbox/PyQt5.QtWebKit.so'
dropbox: load fq extension '/opt/dropbox/PyQt5.QtCore.so'
dropbox: load fq extension '/opt/dropbox/PyQt5.QtNetwork.so'
dropbox: load fq extension '/opt/dropbox/PyQt5.QtGui.so'
dropbox: load fq extension '/opt/dropbox/PyQt5.QtWebKitWidgets.so'
dropbox: load fq extension '/opt/dropbox/PyQt5.QtWidgets.so'
dropbox: load fq extension '/opt/dropbox/PyQt5.QtPrintSupport.so'
!! (Qt:Fatal) This application failed to start because it could not find or load the Qt platform plugin "wayland".
Available platform plugins are: xcb.
Reinstalling the application may fix this problem.
Alexpin commented on 2018-02-01 13:10 (UTC)
@gj545rndmu take a look at the pinned comment:
[...] If you believe there's really an issue in PKGBUILD and/or relevant packaging scripts, please open an issue at https://github.com/yan12125/aur with a title starting with "dropbox:".
gj545rndmu commented on 2018-02-01 10:45 (UTC)
Stupid question, but what do you mean with the last commit message "correct dependencies (closes #16)"? Is there something like a bugtracker?
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
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