We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
autostart doesn't work on kubuntu 22.04
I'm using dropbox on kubuntu 22.04, and recently autostart stopped working. I've been using it without much trouble for years before, on prior versions of kubuntu. I think the autostart function also...
Thanks again for your reply! I now ended up calling `dropboxd` directly, via this desktop file:
❯ cat .config/autostart/dropboxd.desktop
[Desktop Entry]
Exec=/home/jonas/.dropbox-dist/dropboxd
Icon=
Name=dropboxd
Path=
Terminal=False
Type=ApplicationThat seems to work! I hope nothing bad can happen when I call dropboxd direclty, and not via /usr/bin/dropbox!
Unfortunately Dropbox doesn't provide a way to access application logs (I least I don't know for a such). Don't ask me why. Such access would give many useful information, but... 🤷
You case seems similar to one issue of mine; in spite not the same the solution may work for you too. The pseudo script there represents just the idea; you may implement it in completely different way, but keep the name the same and make sure your script resides earlier in your PATH (earlier than the Dropbox control script)!
Good luck.
Thanks again for your reply! I now ended up calling `dropboxd` directly, via this desktop file:
❯ cat .config/autostart/dropboxd.desktop
[Desktop Entry]
Exec=/home/jonas/.dropbox-dist/dropboxd
Icon=
Name=dropboxd
Path=
Terminal=False
Type=Application
That seems to work! I hope nothing bad can happen when I call dropboxd direclty, and not via /usr/bin/dropbox!
Hi jonas11,
Your solution rather confirm my doubts for race condition. The worst thing that can happen is application stop (like before), nothing else. Actually only Dropbox can fix this in their code, nobody else. This is bug that can happen depending on timing conditions. We can only try to decrease probability such thing to happen, no way t prevent it completely. There is no universal workaround that can work everywhere, because on different places (different machine speed, etc.) different timing may be the best choice. In you case shortening launching time seems does the trick. 😉 To decrease further probability remove the dropboxauto.desktop (if you haven't yet) and turn off the application's embedded auto launch features (uncheck the checkbox in Preferences, again if you haven't done it yet). Less tries to launch lead to less likely conflict (remain only your dropboxd.desktop launcher and the application's auto relaunch KDE embedded features). Let's hope Dropbox will fix this issue, but rather don't rely on (the problem is very old).
Wish you never met such an issue again.
