Difference between revisions of "Dropbox"

From ArchWiki
Jump to: navigation, search
(Moved systemd-based daemon to the top of the daemon alternatives, and expanded the text with some clarifications.)
m (Using wicd)
(48 intermediate revisions by 18 users not shown)
Line 2: Line 2:
 
[[de:Dropbox]]
 
[[de:Dropbox]]
 
[[it:Dropbox]]
 
[[it:Dropbox]]
 +
[[ru:Dropbox]]
 
[[zh-TW:Dropbox]]
 
[[zh-TW:Dropbox]]
[https://www.dropbox.com Dropbox] is a file sharing system that recently introduced a GNU/Linux client.  Use it to transparently sync files across computers and architectures. Simply drop files into your {{ic|~/Dropbox}} folder, and they will automatically sync to your centralized repository.
+
[https://www.dropbox.com Dropbox] is a file sharing system that recently introduced a GNU/Linux client.  Use it to transparently sync files across computers and architectures. Simply drop files into your {{ic|~/Dropbox}} folder, and they will automatically sync to your centralized repository.
  
==Installation==
+
== Installation ==
  
 
{{AUR|dropbox}} can be installed from the [[Arch User Repository|AUR]]. Alternatively, {{AUR|dropbox-experimental}} is also available.
 
{{AUR|dropbox}} can be installed from the [[Arch User Repository|AUR]]. Alternatively, {{AUR|dropbox-experimental}} is also available.
Line 17: Line 18:
 
For [[KDE]] users, no further steps are required (it is enough to install the above {{AUR|dropbox}} package from the AUR), as KDE saves running applications when logging out and restarts them automatically. Similarly for [[Xfce]] users, dropbox will be restarted automatically next time you login since the {{ic|dropbox.desktop}} file be placed in {{ic|~/.config/autostart}}.
 
For [[KDE]] users, no further steps are required (it is enough to install the above {{AUR|dropbox}} package from the AUR), as KDE saves running applications when logging out and restarts them automatically. Similarly for [[Xfce]] users, dropbox will be restarted automatically next time you login since the {{ic|dropbox.desktop}} file be placed in {{ic|~/.config/autostart}}.
  
===Optional packages===
+
=== Optional packages ===
  
*For a command-line interface, install {{AUR|dropbox-cli}} from the [[Arch User Repository|AUR]].
+
*For a command-line interface, install {{AUR|dropbox-cli}} from the [[AUR]].
 
*For integration with Nautilus, install {{AUR|nautilus-dropbox}} from the AUR. The Nautilus plugin will start Dropbox automatically.
 
*For integration with Nautilus, install {{AUR|nautilus-dropbox}} from the AUR. The Nautilus plugin will start Dropbox automatically.
 
*For integration with Nemo, install {{AUR|nemo-dropbox-git}} from the AUR.
 
*For integration with Nemo, install {{AUR|nemo-dropbox-git}} from the AUR.
Line 25: Line 26:
 
*For [[KDE]] users, there is a KDE client available: {{AUR|kfilebox}} from the AUR.
 
*For [[KDE]] users, there is a KDE client available: {{AUR|kfilebox}} from the AUR.
  
===Automatically Starting Dropbox===
+
=== Automatically starting Dropbox ===
  
Dropbox can be automatically started by adding {{Ic|dropboxd}} to {{ic|~/.xinitrc}} (or {{ic|~/.config/openbox/autostart}}, depending on your setup). Alternatively, you can [[#Daemon|start it as a daemon]].
+
Dropbox can be automatically started by adding {{Ic|dropboxd}} to {{ic|~/.xinitrc}} (or {{ic|~/.config/openbox/autostart}}, depending on your setup). Alternatively, you can [[#Run as daemon with systemd|start it as a daemon]].
  
 
== Alternative to install: use the web interface ==
 
== Alternative to install: use the web interface ==
Line 33: Line 34:
 
If all you need is basic access to the files in your Dropbox, you can use the web interface at https://www.dropbox.com/ to upload and download files to your Dropbox. This can be a viable alternative to running a Dropbox daemon and mirroring all the files on your own machine.
 
If all you need is basic access to the files in your Dropbox, you can use the web interface at https://www.dropbox.com/ to upload and download files to your Dropbox. This can be a viable alternative to running a Dropbox daemon and mirroring all the files on your own machine.
  
==Run as daemon with systemd==
+
== Run as daemon with systemd ==
  
Recent versions of Dropbox come with a systemd service file. Running Dropbox as a daemon does not give you an icon in the system tray, but syncs your files and folders in the background.
+
Recent versions of Dropbox come with a systemd service file. By default running Dropbox as a daemon does not give you an icon in the system tray, but syncs your files and folders in the background. If you want to have tray support, create {{ic|/etc/systemd/system/dropbox@.service}} to override the provided service file and specify the environment variable {{ic|DISPLAY}}:
  
To enable the daemon for your user, so that it will start at login:
+
{{hc|/etc/systemd/system/dropbox@.service|<nowiki>
$ sudo systemctl enable dropbox@<user>.service
+
.include /usr/lib/systemd/system/dropbox@.service
Note that you have to manually start Dropbox the first time after installation, so that it runs through the login and setup screen. The daemon can be used subsequently.
+
[Service]
 +
Environment=DISPLAY=:0
 +
</nowiki>}}
  
==Daemon (initscripts, deprecated)==
+
Finally, to enable the daemon for your user, so that it will start at login:
{{out of date|Initscripts are deprecated; you should use the systemd method mentioned above.}}
+
# systemctl enable dropbox@<user>
 +
Note that you have to manually start Dropbox the first time after installation, so that it runs through the login and setup screen. Further, you need to uncheck the option '''Start Dropbox on system startup''' in order to prevent Dropbox from being started twice. The daemon can then be used subsequently.
  
To run Dropbox as a daemon similarly to {{Ic|sshd}} or {{Ic|vsftpd}}, simply do one of the following:
+
=== Run as a daemon with systemd user ===
  
===dropbox-daemon Method===
+
If you have followed the [[systemd/User]] wiki page, you probably want to start dropbox only when you log in or launch your WM/DE. The solution in that case is to create a service in your home directory instead of using the sysadmin account:
  
Install {{AUR|dropbox-daemon}}
+
{{hc|$HOME/.config/systemd/user/dropbox@.service|<nowiki>
and configure your username in {{ic|/etc/conf.d/dropboxd.conf}}
+
[Unit]
 +
Description=Dropbox as a systemd service
 +
After=xorg.target
  
This allows you to start or stop Dropbox just like any other service.
+
[Service]
 +
ExecStart=/home/your_user/.dropbox-dist/dropbox
 +
ExecReload=/bin/kill -HUP $MAINPID
 +
Environment=DISPLAY=%i
  
# /etc/rc.d/dropboxd start
+
[Install]
# /etc/rc.d/dropboxd stop
+
WantedBy=mystuff.target
# /etc/rc.d/dropboxd restart
+
</nowiki>}}
  
Place {{Ic|dropboxd}} in the DAEMONS array in {{ic|/etc/rc.conf}} for it to start at boot.:
+
They you can start or enable it with:
DAEMONS=(... '''@dropboxd''' ...)
+
  
===Manual Method===
+
$ systemctl --user {start|enable} dropbox@:0.service
  
As root, copy this into a file called {{ic|/etc/rc.d/dropboxd}} and set USER to your username.
+
That way you can easily start it in your main display (likely :0) or in another one, without having to hard code it.
  
{{bc|<nowiki>
+
{{Note|After a lot of trial and error I found that using {{ic|/usr/bin/dropboxd}} didn't start the service and it didn't show any error either (even when running it directly from the terminal worked fine). I believe it has to do that starting it that way systemd doesn't know which user is actually running the daemon.}}
#!/bin/bash
+
  
USER=yourusername
+
== Securing your Dropbox ==
  
. /etc/rc.conf
+
If you want to store sensitive data in your Dropbox, you should encrypt it before. Syncing to Dropbox is encrypted, but all files are (for the time being) stored on the server unencrypted just as you put them in your Dropbox.
. /etc/rc.d/functions
+
  
PID=`pidof -o %PPID /opt/dropbox/dropbox`
+
* Dropbox works with [[TrueCrypt]], and after you initially uploaded the TrueCrypt volume to Dropbox, performance is quite okay, because Dropbox has a working binary diff.
  
case "$1" in
+
* Another possibility is to use [[EncFS]], which has the advantage that all files are encrypted separately, i.e. you do not have to determine in advance the size of the content you want to encrypt and your encrypted directory grows and shrinks while you add/delete/modify files in it. You can also mount an encrypted volume at startup using the {{ic|-S}} option of {{Ic|encfs}} to avoid having to input the passphrase, but note that your encrypted files are not secure from someone who has direct access to your computer.
  start)
+
    stat_busy "Starting Dropbox Service"
+
    LANG=$LOCALE
+
    [ -z "$PID" ] && su -c "/usr/bin/dropboxd &" $USER
+
    if [ $? -gt 0 ]; then
+
      stat_fail
+
    else
+
      add_daemon dropboxd
+
      stat_done
+
    fi
+
    ;;
+
  stop)
+
    stat_busy "Stopping Dropbox Service"
+
    [ ! -z "$PID" ] && kill $PID > /dev/null
+
    if [ $? -gt 0 ]; then
+
      stat_fail
+
    else
+
      rm_daemon dropboxd
+
      stat_done
+
    fi
+
    ;;
+
  restart)
+
    $0 stop
+
    sleep 3
+
    $0 start
+
    ;;
+
  *)
+
    echo "usage: $0 {start|stop|restart}"
+
    ;;
+
esac
+
exit 0
+
</nowiki>}}
+
  
An Organized Way:
+
=== Setup EncFS with Dropbox ===
{{bc|<nowiki>
+
#!/bin/bash
+
  
. /etc/rc.conf
+
Follow the Wiki instructions to install [[EncFS]].
. /etc/rc.d/functions
+
  
USER=yourusername
+
Assuming you have set your Dropbox directory as {{ic|~/Dropbox}}:
DROPBOXD_PATH='/usr/bin/dropboxd'
+
DROPBOX_PATH='/opt/dropbox/dropbox'
+
  
PID=`pidof -o %PPID $DROPBOX_PATH`
+
Create a folder.  Files you want synced to Dropbox will go in here.
 +
$ mkdir ~/Private
  
case "$1" in
+
Run the following and enter a password when asked:
  start)
+
$ encfs ~/Dropbox/Encrypted ~/Private
    stat_busy "Starting Dropbox Service"
+
    if [ $USER = 'yourusername' ]; then
+
        echo "Please edit /etc/rc.d/dropboxd' 'USER' before using this script."
+
        stat_fail
+
    else
+
LANG=$LOCALE
+
        [ -z "$PID" ] && su -c "$DROPBOXD_PATH &" $USER
+
        if [ $? -gt 0 ]; then
+
          stat_fail
+
        else
+
          add_daemon dropboxd
+
          stat_done
+
        fi
+
    fi
+
    ;;
+
  stop)
+
    stat_busy "Stopping Dropbox Service"
+
    [ ! -z "$PID" ] && kill $PID > /dev/null
+
    if [ $? -gt 0 ]; then
+
      stat_fail
+
    else
+
      rm_daemon dropboxd
+
      stat_done
+
    fi
+
    ;;
+
  restart)
+
    $0 stop
+
    sleep 3
+
    $0 start
+
    ;;
+
  *)
+
    echo "usage: $0 {start|stop|restart}"
+
    ;;
+
esac
+
exit 0
+
</nowiki>}}
+
  
Make the file executable with
+
Your secure folder is ready for use; creating any file inside {{ic|~/Private}} will automatically encrypt it into {{ic|~/Dropbox/Encrypted}}, which will then be synced to your cloud storage.
# chmod +x /etc/rc.d/dropboxd
+
  
This allows you to start or stop {{Ic|dropboxd}} just like any other service. For example:
+
To mount your EncFS folder on every boot, follow the instructions in the [[EncFS#User_friendly_mounting|EncFS]] wiki page.
  
# /etc/rc.d/dropboxd start
+
{{Tip|Consider using the {{ic|ENCFS6_CONFIG}} variable and moving the {{ic|.encfs6.xml}} file to another location (like a USB stick), to help ensure that your encrypted data and the means to realistically decrypt it do not exist together online.}}
# /etc/rc.d/dropboxd stop
+
# /etc/rc.d/dropboxd restart
+
  
To start it at boot, add it to your DAEMONS array in rc.conf: {{ic|/etc/rc.conf}}:
+
== Multiple Dropbox instances ==
DAEMONS=(... '''@dropboxd''' ...)
+
  
==Without Nautilus (Another Way)==
+
If you need to separate or distinguish your data, personal and work usage for example, you can subscribe to Dropbox with different email addresses and have multiple directories synced to different instances.
  
Another way to use Dropbox without Nautilus but with another file manager like Thunar or Pcmanfm is described below:
+
The basic principle and general how-to are described in the [http://www.dropboxwiki.com/Multiple_Instances_On_Unix Dropbox Wiki].
  
1. Create a fake Nautilus script that will launch Thunar:
+
{{Note|When dealing with multiple instances you have to select the Dropbox destination folder, which the Dropbox installer asks in the last step; usage examples may be {{ic|/home/dropbox-personal}}, {{ic|/home/dropbox-work}}, and so on.}}
    $ sudo touch /usr/bin/nautilus && sudo chmod +x /usr/bin/nautilus && sudo nano /usr/bin/nautilus
+
  
2. Insert this text into the file, then save and exit:
+
For convenience, here is a script that I use to accomplish the task: just add a dir in the "dropboxes" list to have another instance of Dropbox, referring to the dir, loaded at script startup.
    #!/bin/bash
+
    exec thunar $2
+
    exit 0
+
  
3. Launch Dropbox
+
{{bc|<nowiki>
    $ dropboxd
+
#!/bin/bash
  
4. Click on the Dropbox tray icon to open your Dropbox folder in Thunar.
+
#*******************************
 +
# Multiple dropbox instances
 +
#*******************************
  
{{Note|In this way there is no need to create a Dropbox daemon in {{ic|/etc/rc.d/}} and to start it at boot via {{ic|/etc/rc.conf}} or to make it start via your session manager: just leave the "Start Dropbox on system startup" option flagged in the Preferences window.}}
+
dropboxes=(.dropbox-personal .dropbox-work)
 +
                                                                                                       
 +
for dropbox in ${dropboxes[@]}; do
 +
    if ! [ -d $HOME/$dropbox ];then
 +
        mkdir $HOME/$dropbox
 +
    fi
 +
    HOME=$HOME/$dropbox/ /opt/dropbox/dropbox start -i &
 +
done
 +
</nowiki>}}
  
{{Note|If you already have Nautilus installed but do not want to use it, don't modify the existing file under {{ic|/usr/bin}}, just change the {{ic|/usr/bin}} for {{ic|/opt/dropbox}} in the step 2 above, like this: {{Ic|$ sudo touch /opt/dropbox/nautilus && sudo chmod +x /opt/dropbox/nautilus && sudo nano /opt/dropbox/nautilus}}. Dropbox will look in this path first!}}
+
== Dropbox on laptops ==
  
==Securing Your Dropbox==
+
Dropbox itself is pretty good at dealing with connectivity problems. If you have a laptop and roam between different network environments, Dropbox will have problems reconnecting if you do not restart it. '''Try one of the methods described below first,''' if for some reason the problem remains, you may try one of these hackish solutions: [https://bbs.archlinux.org/viewtopic.php?pid=790905], [https://bbs.archlinux.org/viewtopic.php?pid=1012343#p1012343].
  
If you want to store sensitive data in your Dropbox, you should encrypt it before. Syncing to Dropbox is encrypted, but all files are (for the time being) stored on the server unencrypted just as you put them in your Dropbox.
+
{{Note|When using any of these methods, you need to prevent Dropbox from doing a standard autostart by unchecking ''Dropbox - Preferences - General - Start Dropbox on system startup''. This prevents Dropbox from creating the {{ic|~/.config/autostart/dropbox.desktop}} file and thus from starting twice.}}
  
* Dropbox works with [[TrueCrypt]], and after you initially uploaded the TrueCrypt volume to Dropbox, performance is quite okay, because Dropbox has a working binary diff.
+
=== Using netctl ===
  
* Another possibility is to use [[EncFS]], which has the advantage that all files are encrypted separately, i.e. you do not have to determine in advance the size of the content you want to encrypt and your encrypted directory grows and shrinks while you add/delete/modify files in it. You can also mount an encrypted volume at startup using the {{ic|-S}} option of {{Ic|encfs}} to avoid having to input the passphrase, but note that your encrypted files are not secure from someone who has direct access to your computer.
+
For [[netctl]], use {{ic|ExecUpPost}} and {{ic|ExecDownPre}} respectively in every network profile you use, or for example in {{ic|/etc/netctl/interfaces/wlan0}} to start Dropbox automatically whenever profile on {{ic|wlan0}} is active. Add '|| true' to your command to make sure [[netctl]] will bring up your profile, although Dropbox fails to start.
  
==Multiple Dropbox Instances==
+
ExecUpPost="''any other code''; su -c 'DISPLAY=:0 /usr/bin/dropboxd &' ''your_user'' || true"
 +
ExecDownPre="''any other code''; killall dropbox"
  
If you need to separate or distinguish your data, personal and work usage for example, you can subscribe to Dropbox with different email addresses and have multiple directories synced to different instances.
+
Obviously, {{ic|''your_user''}} has to be edited and {{ic|''any other code'';}} can be omitted if you do not have any. The above will make sure that Dropbox is running only if there is a network profile active.
  
The basic principle and general how-to are described in the [http://www.dropboxwiki.com/Multiple_Instances_On_Unix Dropbox Wiki].
+
=== Using NetworkManager ===
  
{{Note|When dealing with multiple instances you have to select the Dropbox destination folder, which the Dropbox installer asks in the last step; usage examples may be {{ic|/home/dropbox-personal}}, {{ic|/home/dropbox-work}}, and so on.}}
+
If you have connectivity problem with [[NetworkManager]], try using a [[NetworkManager#Network services with NetworkManager dispatcher|dispatcher script]]: {{AUR|networkmanager-dispatcher-dropbox}} or {{AUR|networkmanager-dispatcher-dropbox-systemd}}.
  
For convenience, here is a script that I use to accomplish the task: just add a dir in the "dropboxes" list to have another instance of Dropbox, referring to the dir, loaded at script startup.
+
=== Using wicd ===
  
{{bc|<nowiki>
+
Create /etc/wicd/scripts/postconnect/dropbox:
#!/bin/bash                                                                                            
+
#!/usr/bin/env bash
                                                                                                       
+
  su -c 'DISPLAY=:0 /usr/bin/dbus-launch dropboxd &' your_username
  #*******************************                                                                       
+
# Multiple dropbox instances                                                                           
+
#*******************************                                                                       
+
                                                                                                       
+
dropboxes=(.dropbox-personal .dropbox-work)                                                           
+
                                                                                                       
+
for dropbox in ${dropboxes[@]}                                                                         
+
do                                                                                                     
+
    if ! [ -d $HOME/$dropbox ];then                                                                   
+
        mkdir $HOME/$dropbox                                                                           
+
    fi                                                                                                 
+
    HOME=$HOME/$dropbox/ /usr/bin/dropbox start -i                                                     
+
done 
+
</nowiki>}}
+
  
==Dropbox on Laptops==
+
Create /etc/wicd/scripts/postdisconnect/dropbox:
 +
#!/usr/bin/env bash
 +
killall dropbox
  
Dropbox itself is pretty good at dealing with connectivity problems. If you have a laptop and roam between different network environments, Dropbox will have problems reconnecting if you do not restart it. The easiest way to solve this with [[netcfg]] is to use POST_UP and PRE_DOWN.
+
{{Note|If you use PCManFM as your file manager, Dropbox will use 'xdg-open' calls pcmanfm to open the Dropbox folder.However, without a dbus session, you can not use Trash in PCManFM. You should refer to [[Dbus]] and [[General Troubleshooting#Session permissions]]to edit your ~/.xinitrc based on /etc/skel/.xinitrc to start a D-Bus session before your launch any other program in ~/.xinitrc. Do use 'dbus-launch dropboxd' instead of just 'dropboxd' in wicd postconnect script. otherwise pcmanfm launched by clicking dropbox icon can not use the Trash.}}
  
In every network profile you use (or in the [[Netcfg#Per-interface_configuration]]), add the appropriate commands:
+
== Troubleshooting ==
{{bc|<nowiki>
+
 
POST_UP="any other code; su -c 'DISPLAY=:0 /usr/bin/dropboxd &' your_user"
+
=== Dropbox keeps saying Downloading files ===
PRE_DOWN="any other code; killall dropbox"
+
 
</nowiki>}}
+
But in fact now files are synced with your box. This problem is likely to appear when your Dropbox folder is located on a NTFS partition whose mount path contains spaces, or permissions are not set for that partition. See more in the [[https://bbs.archlinux.org/viewtopic.php?id=153368 forums]]. To resolve the problem pay attention to your entry in {{ic|/etc/fstab}}. Avoid spaces in the mount path and set write permissions with the "default_permissions" option:
Obviously, your_user has to be edited and 'any other code;' can be omitted if you do not have any. The above will make sure that Dropbox is running only if there is a network profile active.
+
  
If you have connectivity problem with [[NetworkManager]], [https://bbs.archlinux.org/viewtopic.php?pid=790905, this thread] on forum should be useful.
+
UUID=01CD2ABB65E17DE0 /run/media/username/Windows ntfs-3g uid=username,gid=users,default_permissions 0 0
  
==Known Issues==
+
=== Change the Dropbox location from the installation wizard ===
===Dropbox keeps saying Downloading files===
+
But in fact now files are synced with your box. This problem is likely to appear when your Dropbox folder is located on a NTFS partition whose mount path contains spaces. See more in the [[https://bbs.archlinux.org/viewtopic.php?id=153368 forums]]. To resolve the problem pay attention to your entry in {{ic|/etc/fstab}}. Avoid spaces in the mount path and set write permissions:
+
  
UUID=01CD2ABB65E17DE0 /run/media/username/Windows ntfs-3g uid=username,gid=users 0 0
+
Some users experience the problem during setting-up Dropbox that they cannot select a Dropbox folder other than {{ic|/home/username/Dropbox}}. In this case when the window for changing the path is shown , hit {{ic|Ctrl+l}}, enter the location (e.g. /mnt/data/Dropbox) and click on the '"Choose" or "Open" button.
  
===Change the Dropbox location from the installation wizard===
+
=== Context menu entries in file manager do not work ===
Some users experience the problem during setting-up Dropbox that they cannot select a Dropbox folder other than {{ic|/home/username/Dropbox}}. In this case when the window for changing the path is shown , hit CTRL+L, enter the location (e.g. /mnt/data/Dropbox) and click on the 'Choose' or 'Open' button.
+
  
===Context menu entries in file manager do not work===
 
 
Several file managers such as Thunar, Nautilus or its fork Nemo come with extensions that provide context menu entries for files and folders inside your Dropbox. Most of them will result in a browser action such as opening the file or folder in dropbox.com or sharing the link. If you experience these entries to not working, then you are likely to have not set the {{ic|$BROWSER}} variable which Dropbox requires. You can check that by  
 
Several file managers such as Thunar, Nautilus or its fork Nemo come with extensions that provide context menu entries for files and folders inside your Dropbox. Most of them will result in a browser action such as opening the file or folder in dropbox.com or sharing the link. If you experience these entries to not working, then you are likely to have not set the {{ic|$BROWSER}} variable which Dropbox requires. You can check that by  
  
  echo $BROWSER
+
  $ echo $BROWSER
  
 
To set your {{ic|$BROWSER}} variable open {{ic|~/.profile}} and replace {{ic|chromium}} with your default browser:
 
To set your {{ic|$BROWSER}} variable open {{ic|~/.profile}} and replace {{ic|chromium}} with your default browser:
  
 
  if [ -n "$DISPLAY" ]; then
 
  if [ -n "$DISPLAY" ]; then
      BROWSER=chromium
+
        BROWSER=chromium
 
  fi
 
  fi
  
===Connecting...===
+
=== Connecting... ===
{{Note|It seems that this issue has been fixed in later versions of dropbox (sometime before 1.6.0-2). It might be reasonable to test before installing one of the following scripts}}
+
It may happen that Dropbox cannot connect successfully because it was loaded before an Internet connection was established. To solve the problem the content of the file {{ic|/opt/dropbox/dropboxd}} needs to be replaced with the following:
+
  
 +
It may happen that Dropbox cannot connect successfully because it was loaded before an internet connection was established. This can happen on wireless connections, or fast loading machines on wired networks. The best solution to this problem, for wired and wireless connections, is [[#Dropbox on laptops]] which will ensure that Dropbox is started only after the connection is established.
  
#!/bin/sh
+
An alternative solution, for those not using netctl or NetworkManager, is to delay the startup of dropbox:
+
# Copyright 2008 Evenflow, Inc., 2010 Dropbox
+
#
+
# Environment script for the dropbox executable.
+
+
start_dropbox() {
+
PAR=$(dirname $(readlink -f $0))
+
OLD_LD_LIBRARY_PATH=$LD_LIBRARY_PATH
+
LD_LIBRARY_PATH=$PAR:$LD_LIBRARY_PATH
+
+
TMP1=`ps ax|grep dropbox|grep -v grep`
+
if [ -n "$TMP1" ]; then
+
  kill -9 $(pidof dropbox) >/dev/null 2>&1
+
fi
+
exec $PAR/dropbox $@ &
+
}
+
+
do_dropbox() {
+
start_dropbox >/dev/null 2>&1
+
while [ 1 ]; do
+
  sleep 5
+
  ERROR="$(net_test)"
+
  if [ -n "$ERROR" ]; then
+
    LAST_ERROR=1
+
  else
+
    if [ -n "$LAST_ERROR" ]; then
+
      # Connection seems to be up but last cycle was down
+
      LAST_ERROR=""
+
      start_dropbox >/dev/null 2>&1
+
    fi
+
  fi
+
done
+
+
}
+
+
net_test() {
+
TMP1="$(ip addr |grep "inet " |grep -v "127.0.0.1")"
+
[ -z "$TMP1" ] && echo "error"
+
}
+
+
do_dropbox
+
 
+
Following is an alternative script that will check for an actual Internet connection by using {{pkg|curl}} to check if any entry in a list of hosts and IP addresses is available.
+
If none of the specified hosts are available, the script will wait and try again (albeit not forever).
+
The way the script increments the waiting time is quite messy, but the logic goes like this:
+
 
+
Start with a wait time of 5 seconds.
+
 
+
Multiply by 1.5.
+
 
+
Do this as long as the wait time is less than 1500 seconds (25 minutes), and the check_net()
+
function returns non-zero values (failure).
+
  
#!/bin/bash
+
* {{ic|cp ~/.config/autostart/dropbox.desktop ~/.config/autostart/dropbox-delayed.desktop}}
+
* Prevent dropbox from doing a standard autostart by unchecking Dropbox - Preferences - General - Start Dropbox on system startup. This removes {{ic|~/.config/autostart/dropbox.desktop}}.
# Copyright 2008 Evenflow, Inc., 2010 Dropbox
+
* Edit {{ic|~/.config/autostart/dropbox-delayed.desktop}} and replace {{ic|1=Exec=dropboxd}} with {{ic|1=Exec=bash -c "sleep ''timeout'' && dropboxd"}}. Tweak the ''timeout'' parameter, the value of {{ic|3}} is a good start.
#
+
# Environment script for the dropbox executable.
+
+
WAIT_TIME=5 #initial time to wait between checking the internet connection
+
#HOSTS="www.google.com www.wikipedia.org 8.8.8.8 208.67.222.222"
+
HOSTS="www.google.com www.wikipedia.org "
+
+
PAR=$(dirname $(readlink -f $0))
+
OLD_LD_LIBRARY_PATH=$LD_LIBRARY_PATH
+
LD_LIBRARY_PATH=$PAR${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH
+
+
#non-zero exit code iff none of the hosts could be reached
+
check_net() {
+
        local ret=1
+
        for i in $HOSTS; do
+
                #ping -w2 -c2 $i > /dev/null 2>&1 && ret=0 && break
+
                curl -o /dev/null $i > /dev/null 2>&1 && ret=0 && break
+
        done
+
        echo $ret
+
}
+
+
#if dropbox is running; kill it. Then start dropbox
+
start_dropbox() {
+
local tmp=`ps ax|grep -E "[0-9] $PAR/dropbox"|grep -v grep`
+
        if [ -n "$tmp" ]; then
+
                kill -9 $(pidof dropbox) > /dev/null 2>&1
+
        fi
+
        exec $PAR/dropbox $@ > /dev/null 2>&1 &
+
}
+
+
#loop over: start dropbox iff check_net returns 0
+
#loop (and with it, the entire script) terminates when dropbox has been restarted,
+
#+ or the waiting time has exeeded 1500 seconds (it grows 50% with each iteration of the loop)
+
attempt_startup() {
+
        while [ $WAIT_TIME -lt 1500  ] ; do
+
                if [ $(check_net) -eq 0 ]; then
+
                        start_dropbox
+
                        exit
+
                fi
+
                sleep $WAIT_TIME
+
                #WAIT_TIME=$(($WAIT_TIME+$WAIT_TIME/2))
+
                let "WAIT_TIME += WAIT_TIME/2"
+
        done
+
}
+
+
start_dropbox
+
attempt_startup &
+
  
{{Tip|When you update Dropbox via your preferred AUR helper, the file will (usually) be reverted to the default one. You can prevent this with {{ic|chattr +i /opt/dropbox/dropboxd}} which will make the file immutable. To reverse this action simply use {{ic|chattr -i /opt/dropbox/dropboxd}}. }}
+
=== Dropbox does not start - "This is usually because of a permission error" ===
  
===Dropbox does not start - "This is usually because of a permission error"===
+
==== Check permissions ====
  
====Check permissions====
 
 
Make sure that you own Dropbox's directories before running the application. This includes
 
Make sure that you own Dropbox's directories before running the application. This includes
 
*{{ic|~/.dropbox}} - Dropbox's configuration directory
 
*{{ic|~/.dropbox}} - Dropbox's configuration directory
Line 384: Line 203:
 
This error could also be caused by {{ic|/var}} being full.
 
This error could also be caused by {{ic|/var}} being full.
  
====Re-linking your account====
+
==== Re-linking your account ====
 +
 
 
[https://www.dropbox.com/help/72 Dropbox's FAQ] suggests that this error may be caused by misconfiguration and is fixed by (re)moving the current configuration folder
 
[https://www.dropbox.com/help/72 Dropbox's FAQ] suggests that this error may be caused by misconfiguration and is fixed by (re)moving the current configuration folder
 
  # mv ~/.dropbox ~/.dropbox.old
 
  # mv ~/.dropbox ~/.dropbox.old
 
and restarting Dropbox.
 
and restarting Dropbox.
  
====Errors caused by running out of space====
+
==== Errors caused by running out of space ====
 +
 
 
A common error that might happen is that there is no more available space on your {{ic|/tmp}} and {{ic|/var}} partitions. If this happens, Dropbox will crash on startup with the following error in its log:
 
A common error that might happen is that there is no more available space on your {{ic|/tmp}} and {{ic|/var}} partitions. If this happens, Dropbox will crash on startup with the following error in its log:
{{bc|
+
 
Exception: Not a valid FileCache file
+
Exception: Not a valid FileCache file
}}
+
 
 
A detailed story of such an occurrence can be found in the [https://bbs.archlinux.org/viewtopic.php?pid=973458 forums]. Make sure there is enough space available before launching Dropbox.
 
A detailed story of such an occurrence can be found in the [https://bbs.archlinux.org/viewtopic.php?pid=973458 forums]. Make sure there is enough space available before launching Dropbox.
  
====Locale caused errors====
+
==== Locale caused errors ====
 +
 
 
Try starting {{Ic|dropboxd}} with this code:
 
Try starting {{Ic|dropboxd}} with this code:
  
Line 405: Line 227:
 
This helps when running from a Bash script or Bash shell where {{ic|/etc/rc.d/functions}} has been loaded
 
This helps when running from a Bash script or Bash shell where {{ic|/etc/rc.d/functions}} has been loaded
  
====Filesystem monitoring problem====
+
==== Filesystem monitoring problem ====
 +
 
 
If you have a lot of files to sync in your Dropbox folder, you might get the following error:
 
If you have a lot of files to sync in your Dropbox folder, you might get the following error:
  
Line 415: Line 238:
 
  fs.inotify.max_user_watches = 100000
 
  fs.inotify.max_user_watches = 100000
  
to {{ic|/etc/sysctl.conf}} and restarting your computer.
+
to {{ic|/etc/sysctl.conf}} and then reload the kernel parameters
 +
 
 +
# sysctl -p
 +
 
 +
=== Proxy settings ===
  
===Proxy Settings===
 
 
The easiest way to set Dropbox's proxy settings is by defining them manually in the Proxies tab of the Preferences window. Alternatively, you can also set it to 'Auto-detect' and then export your proxy server to the http_proxy env variable prior to starting Dropbox (HTTP_PROXY is also usable)
 
The easiest way to set Dropbox's proxy settings is by defining them manually in the Proxies tab of the Preferences window. Alternatively, you can also set it to 'Auto-detect' and then export your proxy server to the http_proxy env variable prior to starting Dropbox (HTTP_PROXY is also usable)
env http_proxy=http://your.proxy.here:port /usr/bin/dropboxd
+
 
 +
{{bc|<nowiki>env http_proxy=http://your.proxy.here:port /usr/bin/dropboxd</nowiki>}}
 +
 
 
or
 
or
export http_proxy=http://your.proxy.here:port
 
/usr/bin/dropboxd
 
  
Take note, Dropbox will only use proxy settings of the form http://your.proxy.here:port, not your.proxy.here:port as some other applications do.
+
{{bc|<nowiki>
 +
export http_proxy=http://your.proxy.here:port
 +
/usr/bin/dropboxd
 +
</nowiki>}}
 +
 
 +
{{Note|Dropbox will only use proxy settings of the form {{ic|<nowiki>http://your.proxy.here:port</nowiki>}}, not {{ic|<nowiki>your.proxy.here:port</nowiki>}} as some other applications do.}}
 +
 
 +
== Alternatives ==
  
==Alternatives==
+
* [[Ubuntu One]] - {{Pkg|ubuntuone-client}}
*[[Ubuntu One]] - {{Pkg|ubuntuone-client}}
+
* [https://spideroak.com/ Spider Oak] - {{AUR|spideroak}}
*[https://spideroak.com/ Spider Oak] - {{AUR|spideroak}}
+
* [http://kdropbox.deuteros.es/ KFileBox] - {{AUR|kfilebox}}
*[http://kdropbox.deuteros.es/ KFileBox] - {{AUR|kfilebox}}
+
* [https://www.wuala.com/ Wuala] - {{AUR|wuala}}
*[https://www.wuala.com/ Wuala] - {{AUR|wuala}}
+

Revision as of 19:00, 11 September 2013

Dropbox is a file sharing system that recently introduced a GNU/Linux client. Use it to transparently sync files across computers and architectures. Simply drop files into your ~/Dropbox folder, and they will automatically sync to your centralized repository.

Installation

dropboxAUR can be installed from the AUR. Alternatively, dropbox-experimentalAUR is also available.

  1. After installing the package, you can start Dropbox from your application menu or run dropboxd from the command-line. The client icon will appear in the system tray.
  2. A pop-up will notify you that Dropbox is running from an unsupported location. Click on Don't ask again since you know that you have installed it from AUR rather than from the official homepage.
  3. Eventually a pop-up will ask you to log in to your Dropbox account or create a new account. Enter your credentials.
  4. After some time you will see a "Welcome to Dropbox" pop-up, which will give you the opportunity to view a short tour of Dropbox.
  5. Press the "Finish and go to My Dropbox".

For KDE users, no further steps are required (it is enough to install the above dropboxAUR package from the AUR), as KDE saves running applications when logging out and restarts them automatically. Similarly for Xfce users, dropbox will be restarted automatically next time you login since the dropbox.desktop file be placed in ~/.config/autostart.

Optional packages

  • For a command-line interface, install dropbox-cliAUR from the AUR.
  • For integration with Nautilus, install nautilus-dropboxAUR from the AUR. The Nautilus plugin will start Dropbox automatically.
  • For integration with Nemo, install nemo-dropbox-gitAUR from the AUR.
  • For integration with Thunar, install thunar-dropboxAUR from the AUR.
  • For KDE users, there is a KDE client available: kfileboxAUR from the AUR.

Automatically starting Dropbox

Dropbox can be automatically started by adding dropboxd to ~/.xinitrc (or ~/.config/openbox/autostart, depending on your setup). Alternatively, you can start it as a daemon.

Alternative to install: use the web interface

If all you need is basic access to the files in your Dropbox, you can use the web interface at https://www.dropbox.com/ to upload and download files to your Dropbox. This can be a viable alternative to running a Dropbox daemon and mirroring all the files on your own machine.

Run as daemon with systemd

Recent versions of Dropbox come with a systemd service file. By default running Dropbox as a daemon does not give you an icon in the system tray, but syncs your files and folders in the background. If you want to have tray support, create /etc/systemd/system/dropbox@.service to override the provided service file and specify the environment variable DISPLAY:

/etc/systemd/system/dropbox@.service
.include /usr/lib/systemd/system/dropbox@.service
[Service]
Environment=DISPLAY=:0

Finally, to enable the daemon for your user, so that it will start at login:

# systemctl enable dropbox@<user>

Note that you have to manually start Dropbox the first time after installation, so that it runs through the login and setup screen. Further, you need to uncheck the option Start Dropbox on system startup in order to prevent Dropbox from being started twice. The daemon can then be used subsequently.

Run as a daemon with systemd user

If you have followed the systemd/User wiki page, you probably want to start dropbox only when you log in or launch your WM/DE. The solution in that case is to create a service in your home directory instead of using the sysadmin account:

$HOME/.config/systemd/user/dropbox@.service
[Unit]
Description=Dropbox as a systemd service
After=xorg.target

[Service]
ExecStart=/home/your_user/.dropbox-dist/dropbox
ExecReload=/bin/kill -HUP $MAINPID
Environment=DISPLAY=%i

[Install]
WantedBy=mystuff.target

They you can start or enable it with:

$ systemctl --user {start|enable} dropbox@:0.service

That way you can easily start it in your main display (likely :0) or in another one, without having to hard code it.

Note: After a lot of trial and error I found that using /usr/bin/dropboxd didn't start the service and it didn't show any error either (even when running it directly from the terminal worked fine). I believe it has to do that starting it that way systemd doesn't know which user is actually running the daemon.

Securing your Dropbox

If you want to store sensitive data in your Dropbox, you should encrypt it before. Syncing to Dropbox is encrypted, but all files are (for the time being) stored on the server unencrypted just as you put them in your Dropbox.

  • Dropbox works with TrueCrypt, and after you initially uploaded the TrueCrypt volume to Dropbox, performance is quite okay, because Dropbox has a working binary diff.
  • Another possibility is to use EncFS, which has the advantage that all files are encrypted separately, i.e. you do not have to determine in advance the size of the content you want to encrypt and your encrypted directory grows and shrinks while you add/delete/modify files in it. You can also mount an encrypted volume at startup using the -S option of encfs to avoid having to input the passphrase, but note that your encrypted files are not secure from someone who has direct access to your computer.

Setup EncFS with Dropbox

Follow the Wiki instructions to install EncFS.

Assuming you have set your Dropbox directory as ~/Dropbox:

Create a folder. Files you want synced to Dropbox will go in here.

$ mkdir ~/Private

Run the following and enter a password when asked:

$ encfs ~/Dropbox/Encrypted ~/Private

Your secure folder is ready for use; creating any file inside ~/Private will automatically encrypt it into ~/Dropbox/Encrypted, which will then be synced to your cloud storage.

To mount your EncFS folder on every boot, follow the instructions in the EncFS wiki page.

Tip: Consider using the ENCFS6_CONFIG variable and moving the .encfs6.xml file to another location (like a USB stick), to help ensure that your encrypted data and the means to realistically decrypt it do not exist together online.

Multiple Dropbox instances

If you need to separate or distinguish your data, personal and work usage for example, you can subscribe to Dropbox with different email addresses and have multiple directories synced to different instances.

The basic principle and general how-to are described in the Dropbox Wiki.

Note: When dealing with multiple instances you have to select the Dropbox destination folder, which the Dropbox installer asks in the last step; usage examples may be /home/dropbox-personal, /home/dropbox-work, and so on.

For convenience, here is a script that I use to accomplish the task: just add a dir in the "dropboxes" list to have another instance of Dropbox, referring to the dir, loaded at script startup.

#!/bin/bash

 #*******************************
 # Multiple dropbox instances
 #*******************************

 dropboxes=(.dropbox-personal .dropbox-work)
                                                                                                         
 for dropbox in ${dropboxes[@]}; do
     if ! [ -d $HOME/$dropbox ];then
         mkdir $HOME/$dropbox
     fi
     HOME=$HOME/$dropbox/ /opt/dropbox/dropbox start -i &
 done

Dropbox on laptops

Dropbox itself is pretty good at dealing with connectivity problems. If you have a laptop and roam between different network environments, Dropbox will have problems reconnecting if you do not restart it. Try one of the methods described below first, if for some reason the problem remains, you may try one of these hackish solutions: [1], [2].

Note: When using any of these methods, you need to prevent Dropbox from doing a standard autostart by unchecking Dropbox - Preferences - General - Start Dropbox on system startup. This prevents Dropbox from creating the ~/.config/autostart/dropbox.desktop file and thus from starting twice.

Using netctl

For netctl, use ExecUpPost and ExecDownPre respectively in every network profile you use, or for example in /etc/netctl/interfaces/wlan0 to start Dropbox automatically whenever profile on wlan0 is active. Add '|| true' to your command to make sure netctl will bring up your profile, although Dropbox fails to start.

ExecUpPost="any other code; su -c 'DISPLAY=:0 /usr/bin/dropboxd &' your_user || true"
ExecDownPre="any other code; killall dropbox"

Obviously, your_user has to be edited and any other code; can be omitted if you do not have any. The above will make sure that Dropbox is running only if there is a network profile active.

Using NetworkManager

If you have connectivity problem with NetworkManager, try using a dispatcher script: networkmanager-dispatcher-dropboxAUR or networkmanager-dispatcher-dropbox-systemdAUR.

Using wicd

Create /etc/wicd/scripts/postconnect/dropbox:

#!/usr/bin/env bash
su -c 'DISPLAY=:0 /usr/bin/dbus-launch dropboxd &' your_username

Create /etc/wicd/scripts/postdisconnect/dropbox:

#!/usr/bin/env bash
killall dropbox
Note: If you use PCManFM as your file manager, Dropbox will use 'xdg-open' calls pcmanfm to open the Dropbox folder.However, without a dbus session, you can not use Trash in PCManFM. You should refer to Dbus and General Troubleshooting#Session permissionsto edit your ~/.xinitrc based on /etc/skel/.xinitrc to start a D-Bus session before your launch any other program in ~/.xinitrc. Do use 'dbus-launch dropboxd' instead of just 'dropboxd' in wicd postconnect script. otherwise pcmanfm launched by clicking dropbox icon can not use the Trash.

Troubleshooting

Dropbox keeps saying Downloading files

But in fact now files are synced with your box. This problem is likely to appear when your Dropbox folder is located on a NTFS partition whose mount path contains spaces, or permissions are not set for that partition. See more in the [forums]. To resolve the problem pay attention to your entry in /etc/fstab. Avoid spaces in the mount path and set write permissions with the "default_permissions" option:

UUID=01CD2ABB65E17DE0 /run/media/username/Windows ntfs-3g uid=username,gid=users,default_permissions 0 0

Change the Dropbox location from the installation wizard

Some users experience the problem during setting-up Dropbox that they cannot select a Dropbox folder other than /home/username/Dropbox. In this case when the window for changing the path is shown , hit Ctrl+l, enter the location (e.g. /mnt/data/Dropbox) and click on the '"Choose" or "Open" button.

Context menu entries in file manager do not work

Several file managers such as Thunar, Nautilus or its fork Nemo come with extensions that provide context menu entries for files and folders inside your Dropbox. Most of them will result in a browser action such as opening the file or folder in dropbox.com or sharing the link. If you experience these entries to not working, then you are likely to have not set the $BROWSER variable which Dropbox requires. You can check that by

$ echo $BROWSER

To set your $BROWSER variable open ~/.profile and replace chromium with your default browser:

if [ -n "$DISPLAY" ]; then
        BROWSER=chromium
fi

Connecting...

It may happen that Dropbox cannot connect successfully because it was loaded before an internet connection was established. This can happen on wireless connections, or fast loading machines on wired networks. The best solution to this problem, for wired and wireless connections, is #Dropbox on laptops which will ensure that Dropbox is started only after the connection is established.

An alternative solution, for those not using netctl or NetworkManager, is to delay the startup of dropbox:

  • cp ~/.config/autostart/dropbox.desktop ~/.config/autostart/dropbox-delayed.desktop
  • Prevent dropbox from doing a standard autostart by unchecking Dropbox - Preferences - General - Start Dropbox on system startup. This removes ~/.config/autostart/dropbox.desktop.
  • Edit ~/.config/autostart/dropbox-delayed.desktop and replace Exec=dropboxd with Exec=bash -c "sleep timeout && dropboxd". Tweak the timeout parameter, the value of 3 is a good start.

Dropbox does not start - "This is usually because of a permission error"

Check permissions

Make sure that you own Dropbox's directories before running the application. This includes

  • ~/.dropbox - Dropbox's configuration directory
  • ~/Dropbox - Dropbox's download directory (default)

You can ensure this by changing their owner with chown -R.

This error could also be caused by /var being full.

Re-linking your account

Dropbox's FAQ suggests that this error may be caused by misconfiguration and is fixed by (re)moving the current configuration folder

# mv ~/.dropbox ~/.dropbox.old

and restarting Dropbox.

Errors caused by running out of space

A common error that might happen is that there is no more available space on your /tmp and /var partitions. If this happens, Dropbox will crash on startup with the following error in its log:

Exception: Not a valid FileCache file

A detailed story of such an occurrence can be found in the forums. Make sure there is enough space available before launching Dropbox.

Locale caused errors

Try starting dropboxd with this code:

LANG=$LOCALE
dropboxd

(You can also use a different value for LANG; it must be in the format "en_US.UTF-8") This helps when running from a Bash script or Bash shell where /etc/rc.d/functions has been loaded

Filesystem monitoring problem

If you have a lot of files to sync in your Dropbox folder, you might get the following error:

Unable to monitor filesystem
Please run: echo 100000 | sudo tee /proc/sys/fs/inotify/max_user_watches and restart Dropbox to correct the problem.

This can be fixed easily by adding

fs.inotify.max_user_watches = 100000

to /etc/sysctl.conf and then reload the kernel parameters

# sysctl -p

Proxy settings

The easiest way to set Dropbox's proxy settings is by defining them manually in the Proxies tab of the Preferences window. Alternatively, you can also set it to 'Auto-detect' and then export your proxy server to the http_proxy env variable prior to starting Dropbox (HTTP_PROXY is also usable)

env http_proxy=http://your.proxy.here:port /usr/bin/dropboxd

or

export http_proxy=http://your.proxy.here:port
/usr/bin/dropboxd
Note: Dropbox will only use proxy settings of the form http://your.proxy.here:port, not your.proxy.here:port as some other applications do.

Alternatives