Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Ubuntu headless install not working
I'm trying to do the Linux headless install as described at https://www.dropbox.com/install on an Ubuntu 16.04 workstation. It works until I get to the point in the instructions that say "If you're...
Assuming that this is not caused by an antivirus, firewall or VPN/proxy setting on this specific machine, I'll need to ask: have you downloaded the Python script from that page as well tn3?
If possible, could you change your default browser and try again too?
PS: For a list of all the system requirements take a look below:
https://www.dropbox.com/help/desktop-web/system-requirements
Waw... To be honest, that wasn't expected. I thought, you has made alias of your Dropbox install. Seems this isn't the case. The only possibility, I can think of, is home directory alias (error prone choice for setup). Let's try:
echo "Declared home: $HOME"; echo "Real home: $(readlink -e $HOME)"
What's the result? Are the two paths different?
david@ivdweb:5$: echo "Declared home: $HOME"; echo "Real home: $(readlink -e $HOME)"
Declared home: /home/david
Real home: /home/bitnami
david@ivdweb:6$:
The HOME for david is a symlink to the system generated /home/bitnami to make some of the Lightsail setup easier. Wouldn't expect it to cause a problem. Been doing things like that for years - and I've been a Unix sysadmin since 1983. I would expect software to find $HOME once at startup and then just use the inode.
Do I assume Dropbox doesn't like this?
David
DavidLedger wrote:
... I would expect software to find $HOME once at startup and then just use the inode.Do I assume Dropbox doesn't like this?
...Don't make assumptions, which are not confirmed! As a sysadmin you have to know that! 😱 Seems you have known the problem in advance. I suppose you know what follows (as a sysadmin). 😜
Be more careful in future. Have a nice evening!
As a sysadmin with an understanding of system internals I'm surprised that it causes a problem. There's no reason why it should. Obviously I was aware of the link, but not that Dropbox would object. I'll flip the link and see if that fixes it.
Flipped the link, but still the same problem. This time 15 loops of the sleep script.
david@ivdweb:3$: echo "Declared home: $HOME"; echo "Real home: $(readlink -e $HOME)"
Declared home: /home/david
Real home: /home/david
david@ivdweb:4$:Would Dropbox have to be re-installed from scratch to complete the fix (assuming that was the problem)?
DavidLedger wrote:
...Would Dropbox have to be re-installed from scratch to complete the fix (assuming that was the problem)?
Could be? Or re-link, at least. Try. Using following, for example:
dropbox stop rm -rf ~/.dropbox dropbox start
If no joy, try following:
dropbox stop rm -rf ~/.dropbox ~/.dropbox-dist dropbox start -i
As a last resort, remove the Dropbox directory too.
Good luck.
