We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
beaniew
8 months agoHelpful | Level 5
Ubuntu 23.10 - No menu
Ubuntu there's no menu for Dropbox, when I right click the App indicator in the top bar (see image) › dropbox version Dropbox daemon version: 195.4.4995 Dropbox command-line interface...
- 8 months ago
FeRDNYC
Helpful | Level 6
beaniew That's very strange — without that extension, you shouldn't even have had an icon there. That extension is the thing that provides the system tray itself, for Dropbox to show up in.
I do have that extension installed, on Fedora 40, and the situation is the same as you originally reported — nothing happens when I click the icon. When I deactivate the extension, the Dropbox icon disappears entirely, as I'd expect.
FeRDNYC
6 months agoHelpful | Level 6
HUH! But, turns out RESTARTING the extension (just switching it off and on again) did actually make Dropbox's menu accessible!
- notredruide6 months agoHelpful | Level 5
Thanks all, this does indeed work -- but it's not a satisfactory solution because it looks like I'll have to stop and restart the extension on every boot. That may be trivial for Linux mavens but I am not one of them.
- FeRDNYC6 months agoHelpful | Level 6
No, I agree, and I've already reported the issue to the extension maintainers.
No response yet.
- FeRDNYC6 months agoHelpful | Level 6
One thing that might help, notredruide, is to make sure dropbox is started before the extension. That's how I have it set up on my system, and as a result I don't have to restart the extension every boot, only after I restart dropbox manually.
On my system I've done that by setting up a systemd service to start the daemon, in place of $HOME/.config/autostart/dropbox.desktop. That's a bit technical, but I'll provide the service file definition for anyone interested.
But if you don't want to go that route, by default $HOME/.config/autostart/dropbox.desktop contains an autostart delay:
X-GNOME-Autostart-Delay=10
Deleting that line might help it start up before the extension, in which case you wouldn't need to restart anything.
For anyone who wants to have their systemd user session manage the daemon, instead of relying on autostart, you can delete the autostart file and create a dropbox.service file instead. My service definition, with dropbox installed into /usr/bin/ from the Dropbox RPM repository, is:
[Unit] Description=Dropbox Network Storage Daemon After=network-online.target graphical-session.target gnome-shell.service [Service] Type=forking PIDFile=%h/.dropbox/dropbox.pid ExecStart=/usr/bin/dropbox start -i ExecStop=/usr/bin/dropbox stop Restart=on-failure [Install] WantedBy=default.target
- FeRDNYC6 months agoHelpful | Level 6
FeRDNYC wrote:For anyone who wants to have their systemd user session manage the daemon, instead of relying on autostart, you can delete the autostart file and create a dropbox.service file instead.
Actually, instead of just deleting the autostart file, you should switch off "Start Dropbox on system startup" in the Dropbox preferences. That'll delete the autostart file for you, and won't re-create it later when it notices it's missing.
About Apps and Installations
Have a question about a Dropbox app or installation? Reach out to the Dropbox Community and get solutions, help, and advice from members.
Need more support
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!