Dropbox downloads its new version, fails to install it, and tries again.

   To be clear, I am not referring to the updating of the files in the Dropbox-in-the-cloud, nor the files in the Dropbox-on-my-computer as I mess around with them: their updating is satisfactory. This problem concerns the Dropbox installation on my computer downloading a new version of its code (about 110MB), failing to install it, and then trying again. This process can't be stopped (as with "Pause Syncing") except by killing the Dropbox task. While I spent an hour concentrating on a data problem, Dropbox made three failed downloads. This soon makes a big hole in my metered data account (USB cellphone link)

   I am running a GNU/Linux Mint 21 system, 64-bit, and the Dropbox version identified via "Preferences" was 165.4.4300, which succeeded on the 24'th Jan from version 164.4.7914, itself succeeding on the 6'th Jan from version 158.4.4564, etc. All of those advances involved many failed downloads before one succeeded, only too soon being superseded and the floundering resumes.

  Alas, Dropbox doesn't partake of the Linux Mint software update scheme. It would help if the update problem were fixed, but I have no idea what is going wrong, nor do I see any messages.

 

   By referring to the https://www.dropbox.com/install page, I see some arcana for "headless" Linux users. Taking on faith the gibberish shown, I opened a console window and via copy &paste from the 64-bit option,

cd ~ && wget -O - "https://www.dropbox.com/download?plat=lnx.x86_64" | tar xzf -

caused the download of another 110MB, and then

~/.dropbox-dist/dropboxd

did something, and I hope it didn't leave a mess behind. Dropbox appeared to activate its icon (I had killed the task) and now the "Preferences" showed version 166.4.2920, and Dropbox is not showing any attempt at downloading another version. For now.

 

   It would help if the webpage showed the version codes of "the latest versions" so that I can know whether to attempt this sequence afresh. Even better would be an update process that worked. Justifying compulsory updating on grounds of "security" is all very well, but if the compulsory update fails, no improvement in security has been made.

  So far as I know, my system has no strange arrangements - other than it being a dual-boot with windows xp...