2 added 50 characters in body
source | link

I've seen this behaviour for quite some time. It seems that arch and gentoo dropbox packages work differently than expected: they are basically wrappers, initial versions that are able to download the most current binary to your $HOME/.dropbox-dist/ and run that, instead. Usually if you simply run dropbox, it launches $HOME/.dropbox-dist/dropboxd and kills the original process. Have you checked ps -ef | grep dropbox after launching? Here's what I usually see:

$ strace dropbox .... clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fd144c329d0) = 1530 close(6) = 0 read(5, "", 50000) = 0 close(5) = 0 wait4(1530, <unfinished ...> +++ killed by SIGKILL +++ Killed $ ps -ef | grep dropbox me 1530 1 99 09:05 pts/6 00:00:32 /home/me/.dropbox-dist/dropbox-lnx.x86_64-16.3.27/dropbox /newerversion

$ strace dropbox
....
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fd144c329d0) = 1530
close(6)                                = 0
read(5, "", 50000)                      = 0
close(5)                                = 0
wait4(1530,  <unfinished ...>
+++ killed by SIGKILL +++
Killed
$ ps -ef | grep dropbox
me   1530     1 99 09:05 pts/6    00:00:32 /home/me/.dropbox-dist/dropbox-lnx.x86_64-16.3.27/dropbox /newerversion

RE: dropbox-status returning Dropbox isn't running!: that is a conundrum that would refute my hypothesis, and if I had enough rep to comment instead of answer, to make sure you're running ps, I would have done so instead.

I've seen this behaviour for quite some time. It seems that arch and gentoo dropbox packages work differently than expected: they are basically wrappers, initial versions that are able to download the most current binary to your $HOME/.dropbox-dist/ and run that, instead. Usually if you simply run dropbox, it launches $HOME/.dropbox-dist/dropboxd and kills the original process. Have you checked ps -ef | grep dropbox after launching? Here's what I usually see:

$ strace dropbox .... clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fd144c329d0) = 1530 close(6) = 0 read(5, "", 50000) = 0 close(5) = 0 wait4(1530, <unfinished ...> +++ killed by SIGKILL +++ Killed $ ps -ef | grep dropbox me 1530 1 99 09:05 pts/6 00:00:32 /home/me/.dropbox-dist/dropbox-lnx.x86_64-16.3.27/dropbox /newerversion

RE: dropbox-status returning Dropbox isn't running!: that is a conundrum that would refute my hypothesis, and if I had enough rep to comment instead of answer, to make sure you're running ps, I would have done so instead.

I've seen this behaviour for quite some time. It seems that arch and gentoo dropbox packages work differently than expected: they are basically wrappers, initial versions that are able to download the most current binary to your $HOME/.dropbox-dist/ and run that, instead. Usually if you simply run dropbox, it launches $HOME/.dropbox-dist/dropboxd and kills the original process. Have you checked ps -ef | grep dropbox after launching? Here's what I usually see:

$ strace dropbox
....
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fd144c329d0) = 1530
close(6)                                = 0
read(5, "", 50000)                      = 0
close(5)                                = 0
wait4(1530,  <unfinished ...>
+++ killed by SIGKILL +++
Killed
$ ps -ef | grep dropbox
me   1530     1 99 09:05 pts/6    00:00:32 /home/me/.dropbox-dist/dropbox-lnx.x86_64-16.3.27/dropbox /newerversion

RE: dropbox-status returning Dropbox isn't running!: that is a conundrum that would refute my hypothesis, and if I had enough rep to comment instead of answer, to make sure you're running ps, I would have done so instead.

1
source | link

I've seen this behaviour for quite some time. It seems that arch and gentoo dropbox packages work differently than expected: they are basically wrappers, initial versions that are able to download the most current binary to your $HOME/.dropbox-dist/ and run that, instead. Usually if you simply run dropbox, it launches $HOME/.dropbox-dist/dropboxd and kills the original process. Have you checked ps -ef | grep dropbox after launching? Here's what I usually see:

$ strace dropbox .... clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x7fd144c329d0) = 1530 close(6) = 0 read(5, "", 50000) = 0 close(5) = 0 wait4(1530, <unfinished ...> +++ killed by SIGKILL +++ Killed $ ps -ef | grep dropbox me 1530 1 99 09:05 pts/6 00:00:32 /home/me/.dropbox-dist/dropbox-lnx.x86_64-16.3.27/dropbox /newerversion

RE: dropbox-status returning Dropbox isn't running!: that is a conundrum that would refute my hypothesis, and if I had enough rep to comment instead of answer, to make sure you're running ps, I would have done so instead.