Your workflow is unique 👨💻 - tell us how you use Dropbox here.
New installation of the desktop app on Fedora remains on Starting...
Application Affected Dropbox deamon for Linux System Operating System: Fedora Linux 43 KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 Kernel Version: 6.18.7-200.fc43.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen AI 9 HX 370 w/ Radeon 890M Memory: 32 GiB of RAM (30.6 GiB usable) Graphics Processor: AMD Radeon 890M Graphics Manufacturer: Framework Product Name: Laptop 16 (AMD Ryzen AI 300 Series) System Version: A9 Dropbox App Version dropbox-lnx.x86_64-241.4.4795 Issue Fresh install of dropbox on a new laptop running fedora 43 linux. It is "stuck" on "Starting..." I can't figure it out. Need help. If it matters I've been running dropbox on Linux for about a decade and have never experienced this issue. It is currently running just fine on my desktop PC, which is running fedora 42 Linux. I installed drop using the instructions on the dropbox site, using the Fedora 64 bit RPM. That was fine, and the usual files are installed in the places I usually see them. The deamon even properly set itself up to auto start - so when I reboot it starts up and puts itself in the tray (see screenshot). When I reboot it does ask me to sign in - bringing up the web browser, which asks me to 'Connect' my existing account. Which I do in the web browser. I get no complaints or errors. But it doesn't seem to have any effect on the deamon. When I look at the linked devices in my dropbox account the new laptop is listed there. So dropbox has made the association somewhere in it's databases. I have looked around in the linux firewall settings, but don't see anything relevant there. But then again I'm no expert in that regard. Permissions on the disks/files are under my user/group. I am the only user account on this system. I am not seeing any network issues on the system - all other network-using apps are running as expected. If anyone has ideas -- I'm all ears!
Dropbox fails to install on my new Mac M4 running Tahoe.
I've tried multiple time to install dropbox using both the regular install and the offline install. I enter my password and then get this error (and if I drag the dmg to applications, I just get a shortcut to the installer). I reviewed this thread -- same problem, no solution. Any suggestions? Thank you!
I accidentally deleted SyncRootManager from the Windows registry
Application Affected Dropbox Device Dell Latitude 9440 Operating System/Browser (if using the web) Windows 11 Dropbox App Version (if using the app) Question or Issue To resolve an issue not related to dropbox I deleted this key in the registry: HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SyncRootManager Now Dropbox won't start. I have recreated with Key + permissions using another PC, but it seems Dropbox doesn't have the permissions to install what it needs inside this key. How can I fix this? bn.BUILD_KEY: Dropbox bn.VERSION: 240.4.8609 bn.constants.WINDOWS_SHELL_EXT_VERSION: 89 bn.is_frozen: True machine_id: 6b10792b-b8a4-4e49-9bf3-c20ac465f00e pid: 24860 cwd: 'C:\\Program Files (x86)\\Dropbox\\Client' real_path='C:\\Program Files (x86)\\Dropbox\\Client' mode=0o40777 uid=0 gid=0 parent mode=0o40777 uid=0 gid=0 HOME: None appdata: 'C:\\Users\\ricky\\AppData\\Local\\Dropbox\\instance4' real_path='C:\\Users\\ricky\\AppData\\Local\\Dropbox\\instance4' mode=0o40777 uid=0 gid=0 parent mode=0o40777 uid=0 gid=0 dropbox_path: None not found parent not found sys_executable: 'C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe' real_path='C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe' mode=0o100777 uid=0 gid=0 parent mode=0o40777 uid=0 gid=0 trace.__file__: 'C:\\Program Files (x86)\\Dropbox\\Client\\240.4.8609\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc' real_path='C:\\Program Files (x86)\\Dropbox\\Client\\240.4.8609\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc' not found parent not found TMP: C:\Users\ricky\AppData\Local\Temp TEMP: C:\Users\ricky\AppData\Local\Temp tempdir: 'C:\\Users\\ricky\\AppData\\Local\\Temp' real_path='C:\\Users\\ricky\\AppData\\Local\\Temp' mode=0o40777 uid=0 gid=0 parent mode=0o40777 uid=0 gid=0 Traceback (most recent call last): File "desktop/dropbox/client/main.py", line 6949, in _setup_root_for_account File "desktop/dropbox/sync_root/helpers.py", line 199, in create_root_for_account File "desktop/dropbox/foundation/futures/basic.py", line 1040, in result File "desktop/dropbox/sync_root/manager.py", line 382, in create_root File "desktop/dropbox/sync_root/handlers/windows/cloud_files.py", line 299, in register File "desktop/dropbox/sync_root/handlers/windows/cloud_files.py", line 601, in _register PermissionError: [WinError -2147024891] Access is denied
Ubuntu Plucky - Policy will reject signature within a year
warning: https://linux.dropbox.com/ubuntu/dists/plucky/Release.gpg: Policy will reject signature within a year, see --audit for details Control: https://linux.dropbox.com/ubuntu/dists/plucky/Release.gpg: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 1C61A2656FB57B7E4DE0F4C1FC918B335044912E is not bound: No binding signature at time 2025-05-30T19:08:44Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z -- Ubuntu Plucky is stable enough to support Dropbox, update signature PLEASE!!!!!! André
Dropbox fails to start on Linux systems where /home is a symbolic link
Device Dell XPS 15 9520 Operating System/Browser (if using the web) Fedora 43 Kinoite Dropbox App Version (if using the app) v240.4.8493 Syncing Status Up to date (workaround exists) Question or Issue I noticed this issue after installing Dropbox via Flatpak, but I confirmed it exists on the headless official version, too. Fedora 43 Kinoite (and other atomic distros like Bazzite) keeps most of the root partition read-only, mounting a btrfs subvolume at `/home`, which is a symbolic link to `/var/home`. On my system, I see this: alex@alex-laptop:/var/home/alex$ echo $HOME /home/alex alex@alex-laptop:/var/home/alex$ grep $USER /etc/passwd alex:x:1000:1000:Alex Reinking:/home/alex:/bin/bash alex@alex-laptop:/var/home/alex$ grep home /etc/fstab UUID=b3440961-1f62-4818-a9c8-1b83b2c2c23f /home btrfs subvol=home,compress=zstd:1,x-systemd.device-timeout=0 0 0 After launching the Dropbox daemon, I am prompted to sign in. After doing so, Dropbox fails to create the ~/Dropbox directory, displaying the following error dialog: One way to work around this is to manually resolve the symbolic link: $ export HOME=$(realpath ~) $ ~/.dropbox-dist/dropboxd See more discussion here: https://github.com/flathub/com.dropbox.Client/issues/392 After doing this once, however, Dropbox is able to continue working; likely because the information in ~/.dropbox bypasses the broken file system check. Please fix Dropbox's file system support check!I see no menu after clicking on the Dropbox tray icon on Fedora 43.
Application Affected Dropbox Tray Icon Device ThinkPad 230 Operating System/Browser (if using the web) Linux Fedora 43 Dropbox App Version (if using the app) Dear all, after losing many hours, I am getting nearer to make Dropbox work on Fedora 43 as it should. For now, I can see the Dropbox folder, the Dropbox tray icon on the top bar, however clicking on it (left/right click) does absolutely nothing. It means that it keeps synchronising all folders, which I don't want. I know that when installed correctly, the tray icon does show the sync menu, allowing to select which folders to sync and which not to. So obviously, I've gone wrong somewhere. Has anyone got a cure for this? I am not an expert, but have really found this very difficult.. All help is welcome. Thank you. Kind regards, Christos
