nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Dropbox Daemon error on every boot on OpenSUSE Tumbleweed

Area51

The OS is opsnSUSE Tumbleweed Linux, and the desktop environment is KDE Plasma 6 under Wayland. Dropbox has been working flawlessly for years. However, this week I get a constant request to update the daemon on every boot.

I have uninstalled the 3 distro provided packages that use the daemon, the daemon was installed per the Dropbox procedure. I deleted the two hidden Dropbox directories including the ~.dropbox-dist directory. I then rebooted and reinstalled first the dropbox daemon via the Dropbox web site instructions and then the the OS packages. After relogging into the account, I get the same result on every boot.

I did a search of the systemd log and took a screenshot of the errors the Dropbox daemon is reporting during a boot. (I can't copy/paste text from this window.) These seem to be Python errors, particularly Python 3.14. Pythion 3.10 through 3.14 is installed on the system because of application needs and all are current with updates.

The errors screenshot is attached. Any ideas as to what is causing this are appreciated.

Is this a Dropbox daemon bug? Anything I can do here?

TIA.

Dropbox error.png

Find more posts tagged with

Desktop

Error Messages

Linux

Accepted answers

Area51

As a follow-up, this has worked lieerally for years and did work after the error. The fix was to write a shell script to delay the Dropbox launch by 10 seconds and then run the usual dropbox -i command from inside the script. I call the script from the KDE Autostart directory.

So far this has resolved the issue. I don't know what might have changed the booting timing in relation to the Dropbox daemon.

All comments

Hannah

Thanks for letting us know about this, @Area51. 👽️

As a first step, can you take a look at our system requirements and make sure that your computer has the correct setup for the Dropbox app to work?

Let me know and we'll go from there.

Area51

So far this has resolved the issue. I don't know what might have changed the booting timing in relation to the Dropbox daemon.

Megan

Hey @Area51!

Happy to see that your issue is now resolved!

I'll be a post away if you need anything, or if you notice that the behavior reappears. 😎