From ArchWiki
Jump to navigation Jump to search

Hack To Stop Auto-Update

I have concerns about this section of the article mainly because I just installed Dropbox from the AUR and I have no .dropbox-dist directory (I have seen it in the past however). I am wondering if this is something that has changed in a more recent version of Dropbox and perhaps this directory no longer applies and renders this section of the Archi Wiki entry out of date for the moment. Taliesin (talk) 01:52, 26 August 2014 (UTC)

Wait until the auto-update kicks in. The auto-updater assumes that the ~/.dropbox-dist/ directory is the installation path (and when using the upstream installer instead of AUR, it indeed is), so it just extracts the downloaded tarball into this path. For the record, the AUR package uses /opt/dropbox/ as the installation path. -- Lahwaacz (talk) 07:02, 26 August 2014 (UTC)

This hack saved my rear end a couple of weeks ago when Dropbox 3 was pushed (with regressions). The only other place that seemed to hint at that trick was on Dropbox's old forum, which as far as I know was deleted. So, I just wanted to say thanks for documenting the undocumented feature. KlipperKyle (talk) 05:46, 30 December 2014 (UTC)

Run as a daemon with systemd user

The configs in section "Run as a daemon with systemd user" do not work for me. Getting an "Failed to get D-Bus connection: Verbindungsaufbau abgelehnt" error when executing "sudo systemctl --user start dropbox@:0.service". Configs of section "Run as a daemon with systemd user" do work however. Bkk (talk) 10:10, 12 February 2015 (UTC)

I have Dropbox successfully running using systemd user with a system tray icon. I updated that section with the steps I used to get it working
Silverhammermba (talk) 20:59, 15 February 2015 (UTC)
Thanks for your help! Unfortunately the changes do not work for me ("start request repeated too quickly for dropbox.service" even though I waited quite some time):
Feb 15 23:01:43 bkk-V5 systemd[731]: Starting Dropbox...
Feb 15 23:01:43 bkk-V5 systemd[731]: start request repeated too quickly for dropbox.service
Feb 15 23:01:43 bkk-V5 systemd[731]: Failed to start Dropbox.
Feb 15 23:01:43 bkk-V5 systemd[731]: Unit dropbox.service entered failed state.
Feb 15 23:01:43 bkk-V5 systemd[731]: dropbox.service failed.
So far, only starting dropbox via terminal "dropbox" does work for me. --Bkk (talk) 22:08, 15 February 2015 (UTC)
The dropbox service is configured to restart when it fails, but it looks like it's always failing for you so it gets into a loop. What does journalctl --user --unit=dropbox.service say? Or systemctl --user status dropbox? Can you run other user services successfully?
Silverhammermba (talk) 01:38, 16 February 2015 (UTC)

Right click does not show the menu

If right clicking the dropbox icon does not show the menu as it should, or shows the applet menu (Cinnamon, maybe others) try ending Dropbox and running it with: dbus-launch dropbox

Koassim (talk) 10:49, 18 March 2016 (UTC)

Is this another symptom of user buses? -- Alad (talk) 11:45, 18 March 2016 (UTC)
Maybe? I don't know. Sorry. Koassim (talk) 18:07, 19 March 2016 (UTC)

The part about networkmanager does not apply anymore

The networkmanager scripts are not available on the AUR anymore, so I guess the functionality has been included elsewhere? Anyone knows that?