I got an error "Dropbox unexpectedly quit" on Ubuntu

[matd]

Using ubuntu 19.10 and followed this installation located there:
https://help.dropbox.com/installs-integrations/desktop/advanced-reinstall

I did uninstall few times and reinstall but always get the same issue. The application seems to be stuck on "syncing" until the "Dropbox unexpectedly quit" is appearing.

Even my other computer using ubuntu 19.10 gets the same issue. To be noted, I am using pyenv to support multiple version.

Here is the log using the dropbox cli:

mathieu@NUC-linux:~$ ~/.dropbox-dist/dropboxd start
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-Wad0XS
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/dropbox'
dropbox: setting python path '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307:/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtNetwork.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'
NUCLEUS PANICKING -- "Too many conflicts?" at "src/libcore/option.rs":1166
dropbox: locating interpreter
dropbox: logging to /tmp/dropbox-antifreeze-mmMUf8
dropbox: initializing
dropbox: initializing python 3.7.5
dropbox: setting program path '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/dropbox'
dropbox: setting python path '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307:/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/python-packages.zip'
dropbox: python initialized
dropbox: running dropbox
dropbox: setting args
dropbox: applying overrides
dropbox: running main script
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/cryptography.hazmat.bindings._constant_time.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/cryptography.hazmat.bindings._openssl.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/cryptography.hazmat.bindings._padding.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/psutil._psutil_linux.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/psutil._psutil_posix.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/apex._apex.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/tornado.speedups.cpython-37m-x86_64-linux-gnu.so'
Segmentation fault (core dumped)
mathieu@NUC-linux:~$ dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtCore.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtGui.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtNetwork.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtWidgets.cpython-37m-x86_64-linux-gnu.so'
dropbox: load fq extension '/home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-90.4.307/PyQt5.QtDBus.cpython-37m-x86_64-linux-gnu.so'

[Здравко]

Dropbox uses proprietary python version built-in application itself, so standard tools don't affect it. Why you're putting at the end 'start'?! You are trying run daemon directly, without using control script. The commands have to be used with control script, like: 'dropbox start', for example! Daemon, you are running, don't care for the start at the end. If you want direct daemon run, remove all parameters, i.e. '~/.dropbox-dist/dropboxd' only.

[matd]

I am getting the exact same issue when using:

dropbox start

[Здравко]

Exactly the same!? In your previous post could be seen 2 run tries (while single command is typed). Is it the same? What is the result from:

ps `ps x -o comm,pid | grep dropbox | sed s/dropbox//`
dropbox status

ADD: Try also:

ps `cat ~/.dropbox/dropbox.pid`

[matd]

$ ps `ps x -o comm,pid | grep dropbox | sed s/dropbox//`
  PID TTY      STAT   TIME COMMAND
30953 pts/0    Sl+    1:19 /home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-91.4.5
$ dropbox status

Command 'dropbox' not found, but can be installed with:

sudo apt install nautilus-dropbox

$ ps `cat ~/.dropbox/dropbox.pid`
  PID TTY      STAT   TIME COMMAND
30953 pts/0    Sl+    2:24 /home/mathieu/.dropbox-dist/dropbox-lnx.x86_64-91.4.548/dropbox

This is when I relaunched dropbox

[Здравко]

---

@matd wrote:

I am getting the exact same issue when using:

dropbox start

---

And... on such background follows:

---

@matd wrote:

.....
$ dropbox status

Command 'dropbox' not found, but can be installed with:
....

This is when I relaunched dropbox

---

Can you clarify, how you had make 'dropbox start' (the first cite) without dropbox control script being installed (the second cite)?!

Ok, seems the Dropbox application actually works. What's wrong actually? If you want control by CLI, just install the control script either by hand or using the debian package.

[matd]

After running around 15minutes, dropbox always, always always raises this windows

[matd]

Problem is that whichever way I install and run dropbox, it always end up generating that dialog after several minutes...

[Здравко]

Ah.. That's something new (the screenshot). That message doesn't come from the control script, but the daemon. Stop any dropbox application instance. If you have installed the script, just run 'dropbox stop'. If not, run in a terminal following command:

kill `ps x -o comm,pid | grep dropbox | sed s/dropbox//`

Repeat the command execution till the moment of receiving error message of incorrect use (means that there isn't anything more to kill - no more dropbox instances, if there are more than one). Next, in the terminal run the daemon:

~/.dropbox-dist/dropboxd

Don't close the terminal and wait (according your words - several minutes) till the moment of the unexpected quit. Put in your next reply here, in a code block (</>), entire terminal output from launching daemon's command (including) to the end. Let's hope there will be some extra exception info, describing what's going on in your case.

[matd]

When looking at the system tray icon, it seems to be stuck at indexing.

Is there a way to verbose the deamon steps?