Need to see if your shared folder is taking up space on your dropbox đšâđ»? Find out how to check here.
I created 2.4M files over the limit on the desktop app and now it's stuck syncing.
Application Affected Dropbox Device Dell OptiPlex 980 Operating System/Browser (if using the web) Ubuntu Linux Dropbox App Version (if using the app) v237.4.5655 Question or Issue I created 2.4M CSV files for a client, and the Dropbox app starting to upload these files. After almost 48 hours of this, I discovered that this was way too many files. My remediation was to exclude the top-levl directory from syncing. I made that change ten hours ago, but the app is still grinding away, doing something. I tried exporting the logs to find out what it might be doing, but the logs just show up as binary data -- I don't know how to read them. How can I sort this out?
Problems syncing on Bazzite with Linux.
Integration Affected Bazzite Linux, KDE and Gnome Desktops Device Custom PC Operating System/Browser (if using the web) Bazzite Linux, Kernel 6.15.9-116.bazzite Dropbox App Version (if using the app) 231.4.5570 Question or Issue -- I downloaded Dropbox as usual but it says the following when attempting to Sync: -- I've seen this happening only in Bazzite, I don't know if there are considerations given that is an inmutable distro and comes with btrfs filesystem by default. Which is weird because you supposedly support that filesystem. -- Also, other users in the Bazzite forums have tried the following: Interesting. Thank you for the detail, I am a staff software engineer familiar with linux (I run programming.dev actually), so the description helps, Iâm just not familiar with a lot of the intricacies of linux, nor desktop linux. Iâve switched to cachyos and am trying to set up bazzite for my wife. So I get the same output on Bazzite for those commands, so UB is at least consistent here. I do not understand what you mean by using flatseal to configure the Dropbox flatpak to use /var/home. Thereâs no reference to /home anywhere in flatseal, and it looks like the only thing I can change are permissions. When I click the Move button (which I would assume would let me actually point it at /var/home, nothing happens. I actually posted about this in the Universal Blue discord, with some of the other stuff Iâve tried: ** Things Iâve tried:** adding permission in flatseal for app to access everything adding folder to /var/mnt/synco/lnsync/account to Other Files in flatseal (even though synco doesnât exist) created a 100gb partition /run/media/sabrina/Dropbox , mounting it, adding it to flatsealâs Other Files and clicking Move in the dropbox dialog again. reinstalling running Dropbox with GSK_RENDERER=ngl flatpak run com.dropbox.Client. Iâll attach the logs I got for that, but it was a big nothingburger, even after clicking Move nothing shows up. running Dropbox with GSK_RENDERER=gl flatpak run com.dropbox.Client. Same deal (gl vs ngl) I even have this bit in there: the one thing that is always recommended is moving the dropbox folder from /home/user/Dropbox to /var/home, but I have the same error as the last link I provided. When I click Move nothing ever happens. It just closes the dialog with no further messaging. If I run Dropbox from the cli, to get logs (dropboxâs debug logs are in binary for their âsupport toolâ) then I get this, where nothing shows after clicking Move. GSK_RENDERER=ngl flatpak run com.dropbox.Client dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/cryptography.hazmat.bindings._openssl.abi3.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/cryptography.hazmat.bindings._padding.abi3.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/apex._apex.abi3.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/google._upb._message.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so' <frozen zipimport>:259: UserWarning: google.protobuf.service module is deprecated. RPC implementations should provide code generator plugins which generate code specific to the RPC implementation. service.py will be removed in Jan 2025 dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/tornado.speedups.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so' Gtk-Message: 09:28:00.323: Failed to load module "colorreload-gtk-module" dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/cryptography.hazmat.bindings._openssl.abi3.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/cryptography.hazmat.bindings._padding.abi3.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/apex._apex.abi3.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/google._upb._message.cpython-38-x86_64-linux-gnu.so' <frozen zipimport>:259: UserWarning: google.protobuf.service module is deprecated. RPC implementations should provide code generator plugins which generate code specific to the RPC implementation. service.py will be removed in Jan 2025 dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/tornado.speedups.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/cryptography.hazmat.bindings._openssl.abi3.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/cryptography.hazmat.bindings._padding.abi3.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/apex._apex.abi3.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/google._upb._message.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so' <frozen zipimport>:259: UserWarning: google.protobuf.service module is deprecated. RPC implementations should provide code generator plugins which generate code specific to the RPC implementation. service.py will be removed in Jan 2025 dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/tornado.speedups.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/app/extra/.dropbox-dist/dropbox-lnx.x86_64-230.4.8797/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so' Gtk-Message: 09:28:06.961: Failed to load module "colorreload-gtk-module" At this point this seems like maybe I should be contacting Dropbox though, but Iâve seen so many other posts where people got this working that I just assumed it must be on my side. -- Other user adds: That is another view of the symptom. The reality is that there is nothing to move! But the code inside of the flatpak: doesnât understand the metadata it is getting from the composefs fs type is not expecting /home to be a symlink and so is not doing the equiv of performing a stat command the follows the symlink. For example, look at the difference of this output: $ stat /home File: /home -> var/home Size: 8 Blocks: 8 IO Block: 4096 symbolic link Device: 0,39 Inode: 563 Links: 1 Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root) Context: system_u:object_r:home_root_t:s0 Access: 1970-01-01 00:00:00.000000000 +0000 Modify: 1970-01-01 00:00:00.000000000 +0000 Change: 1970-01-01 00:00:00.000000000 +0000 Birth: - vs dereferencing the symlink like this: $ stat -L /home File: /home Size: 28 Blocks: 0 IO Block: 4096 directory Device: 0,50 Inode: 256 Links: 1 Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Context: system_u:object_r:home_root_t:s0 Access: 2025-08-25 20:30:54.504715317 +0000 Modify: 2024-12-28 13:11:12.910724872 +0000 Change: 2025-08-24 18:42:06.380999950 +0000 Birth: 2024-12-28 12:57:19.448791400 +0000 I suspect they are not recognizing that `/home` is a symlink so they are querying the wrong filesystem and failing. Thanks for the kind words. -- Another user has a theory but no action Plan: Earlier this year, upstream (Fedora) changed the root (/) filesystem type to composefs for reasons. This is not a widely recognized filesystem type across the Linux landscape. And it has limitations. One of those limitations is what is being experienced in this case - namely, the DropBox flatpak does not recognize the FS type and does not know what to do with it. The workaround I suggested was to bypass the configuration of the flatpak by modifying the config (using flatseal) to point to /var/home/userid instead of /home/userid. The reason that workaround is effective is because: TL;DR - flatpaks not based on one of the Fedora Atomic Desktop offerings do not understand the composefs file system type. The workaround is effective because on Universal Blue systems /var/home is of type btrfs instead, which is widely recognized. / is of filesystem type composefs and that fs type is not widely known outside of the Fed-a-verse /home is just a symlink to /var/home /var/home is of type btrfs instead - which is widely recognized So using /home vs /var/home provide different results because they are of different fs types and the type of the / filesystem is not widely known (yet). $ mount | grep 'on / ' | head -1 composefs on / type overlay (ro,relatime,seclabel,lowerdir+=/run/ostree/.private/cfsroot-lower,datadir+=/sysroot/ostree/repo/objects,redirect_dir=on,metacopy=on) $ mount | grep 'on /var/home ' | head -1 /dev/nvme0n1p3 on /var/home type btrfs (rw,relatime,seclabel,ssd,discard=async,space_cache=v2,subvolid=257,subvol=/home) $ ls -ld /home lrwxrwxrwx. 1 root root 8 Jan 1 1970 /home -> var/home That is the theory behind my suggestion above. I was hesitant to go into the detail here because I have been blasted for doing so in the past. What is needed: - Your help to find out why Dropbox is not working on Fedora-based distro, Bazzite.
Can I sync a single folder with selective sync, without downloading its entire directory?
Suppose I have a folder structure as follows: Folder A contains File A and Folder B. Folder B contains File B. Something like: Folder A |- File A |- Folder B |- File B The expected behaviour is that if I choose "Selective Sync" and click only "Folder B", this should locally sync Folder B and File B, but not File A. (ideally, a "-" sign should appear for Folder A with the option to click the checkbox to sync everything in Folder A). The actual behaviour is that selecting Folder B (via the checkbox) automatically checks "Folder A", and Dropbox will attempt to locally sync File A as well as Folder B. This is the behaviour on Ubuntu; if this differs on Mac or Windows please post below.
How can I save files into my Dropbox account using WPS Office on Ubuntu?
I recently had Microsoft removed from my computer and replaced with Linux Ubuntu. I'm struggling with the learning curve. I have installed Dropbox and I have installed WPS Office. How do I have WPS Office let me save to Dropbox? (as I previously did in a Windows based system)
[Solved, Ubuntu 22.04] Dropbox is always "Connecting..."
Hi, Dropbox tray icon says it is "Connecting..." forever. I cannot see the list of the latest modified files as it used to show or use the tray, actually. I am using Linux Ubuntu 22.04 (but it like that since the 19.10, I suppose) The currently installed version of Dropbox is 149.4.4568 I also don't have the "Early releases" enabled as you can see in the following screenshot. I also tried to remove `.dropbox` and `.dropbox-dist` manually to reinstall them cleanly. You can check the date and time it was reinstalled here.Feedback and questions about how selective sync works on Linux
I has taken me the better part of an hour just to a button that allows one to start a discussion. Not sure, but part of the problem may be I was using Firefox. Regardless, it should not be this difficult. I have been spending hours trying to setup my account so certain dropbox folders would be visible in my PC's Dropbox folder but not stored there. I thought that is what Selective Sync did. I also looked into Dropbox Backup. This is what I found in dropbox's documentation. " Selective sync is a feature in the Dropbox desktop app that allows you to add or remove Dropbox folders from your hard drive to save space on your computer without deleting the files themselves. You can check or uncheck folders in the Dropbox desktop app to determine whether the files are saved to your hard drive or just stored in your Dropbox account." That sounds like what I want but the documentation fails to address one aspect of how it works. Are the files which are unchecked still visible on the local PC? With much searching I found this. "What's the difference between selective sync and online-only? Making your files and folders online-only also helps save hard drive space. These files and folders will still be visible from your computer, but are stored in your Dropbox account online." Notice this response does not answer the question. It describes a characteristic of online-only but to describe a difference, one has to contrast how the other option works. From experimentation, I finally deduced unchecked folders effectively ignored by dropbox. And in another slap in the face, more searching revealed "online-only is not available on linux. Arrgh. Hours an hours of searching. because the documentation sucks. So maybe this think dropbox calls backup will help. Other cloud provides have a feature called backup that would meet my needs. And it appear to be available. "Dropbox Basic is a free plan that includes Dropbox Backup, allowing you to back up your computer and external hard drive, but limits the size of your backups to the 2 GB storage quota of the plan." This says where it is available and does not exclude Linux, so the documentation says I should have access to it. To set up your computer to back up: Open your Dropbox desktop app preferences. Click the Backups tab. Click Set up. Note: If youâre on a Dropbox team account and you donât see this option, your admin may have chosen not to allow you to enable it. Check the folders youâd like to back up. If your work and personal accounts are connected, choose which Dropbox account youâd like to back up your folders to. Click Set up and follow the steps. Mac users: Click OK when prompted to give Dropbox permission to access your folders. This is what I see using the app (v223.4.4909) on Linux. . There is no No "Backups" tab. So is the documentation wrong or am I looking in the wrong place?
