You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Linux
249 TopicsUpdate Fedora Repositories from Fedora Workstation 31 to Fedora Workstation 32
Currently all current Fedora Workstation users (version 32) receive the below error message: Dropbox Repository 51 kB/s | 25 kB 00:00 Errors during downloading metadata for repository 'Dropbox': - Status code: 404 for http://linux.dropbox.com/fedora/32/repodata/repomd.xml (IP: 54.192.73.23) Error: Failed to download metadata for repo 'Dropbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Ignoring repositories: Dropbox This is because Fedora Workstation 32 anticipated an update to your Fedora repositories. However, upon looking at the directory list and consulting Dropbox customer support on Twitter, it is clear that there is not an updated Fedora Workstation 32 repository. See here: https://linux.dropbox.com/fedora/ Why you should update this repository: 1. You have clearly maintained a repository for most older versions of Fedora Workstation, so this missing repository for 32 is an inconsistent abberation. 2. Fedora Workstation 32 is upstream of corporate subscription-based RedHat Enterprise Linux, therefore, updating this for Fedora Workstation 32 will fix this issue once Workstation is merged into RedHat Enterprise Linux. 3. You may have subscribers who use Fedora Workstation 32 for their professional work. Their subscription money should pay for an update to your Fedora repositories for the latest version: 32. 4. This has already been an issue which many users have asked you to fix. Therefore, updating your repositories will maintain your current customer base and future customer base once Fedora Workstation 32 is merged downstream into Redhat Enterprise Linux and maintain your reputation with professional Linux users.5.6KViews17likes2CommentsI cannot install the desktop app on Linux Fedora 37
Gnome 43 has removed libnautilus-extension.so.1 making it impossible to install Dropbox on Fedora 37. Please update the rpm installer to make use of the changes in gnome 43. For reference: https://ask.fedoraproject.org/t/official-dropbox-package-doesnt-install-in-fedora-37/27296 Here is a link to an open pull request to make the necessary changes: https://github.com/dropbox/nautilus-dropbox/pull/105Solved16KViews15likes70CommentsCan't un-exclude directories with `dropbox.py exclude remove <directory>` on Ubuntu 20.04.2
I have a Linux machine (running Ubuntu 20.04.2 LTS, "Focal Fossa") upon which I am running a "headless" Dropbox daemon as per here: https://www.dropbox.com/install-linux The Dropbox daemon is up to date: ``` $ dropbox.py version Dropbox daemon version: 125.4.3474 Dropbox command-line interface version: 2020.03.04 ``` This machine is truly "headless", so I am doing everything on the command line. Installation of the daemon and initial sync seemed to work fine, though autostart isn't working for me. I've found that I can exclude directories with `dropbox.py exclude add <directory>` just fine. When I run that command for a directory in my Dropbox, the directory briefly appears in the list output from `dropbox.py exclude`. However, once the directory is actually deleted from the local Dropbox directory, it disappears from the list too. For example, I do have a bunch of directories excluded, and they are not present in the local Dropbox directory. However, the tool incorrectly reports no excluded directories: ``` $ dropbox.py exclude No directories are being ignored. ``` This is fine, if a bit weird, but the problem is that I can't add excluded directories back (un-exclude them?) with `dropbox.py exclude remove <directory>`. That command outputs nothing and has no effect. Why not? How can I get this to work? It seems totally broken right now.7.6KViews10likes43CommentsFuture Support for Linux?
Hi.. That other thread is getting really, really long, so I thought I'd pose a question here, for someone from Dropbox to answer, rather than the complaints and rants in the other thread. :-) Right at this moment I'm considering going through the painof shifting my DB folder to ext4 despite the security/stability issues of using an old filesystem for one app. I want to know if I'm just wasting my time and money continuing to be a paid DB customer who usesa cross-platform mix of machines. So.. Questions for Dropbox to answer here: - Does dropbox intend to continue supporting Linux? - Is there a roadmap or intentionto support modern filesystems rather than the nearing legacy ext4? - How much of a minority are paid Linux accounts? 1%? Less? Not really expecting an answer, and if you're not a dropbox rep, please keep your comments in the other thread.. :-)Solved6.9KViews9likes7CommentsLinux Computer Backup
I was pointed here to give a suggestion from this thread:https://www.dropboxforum.com/t5/Dropbox-files-folders/Trying-to-backup-on-Linux/td-p/548352 It would be nice if the functionality was added to(https://help.dropbox.com/installs-integrations/desktop/linux-commands) Some commands like: `dropbox backup enable/disable` and `dropbox backup add/remove /path/to/folder/or/file` Currently the advice is to mount into the dropbox folder (https://askubuntu.com/questions/1366889/how-can-i-use-dropbox-to-back-up-arbitrary-folders/1366896#1366896)6.9KViews8likes8CommentsDropbox is compatible with Ext4 but doesn't recognize ext4 drive?
So, like most Linux users, I've gotten the message about needing to upgrade to an ext4 drive. I had an extra drive in my machine with nothing on it so I formatted it to ext4. I rebooted then went into my prefs to change location and it tells me: To sync your Dropbox, move your Dropbox folder to a partition with a compatible File System. Dropbox is compatible with Ext4. So, when is an ext4 drive not an ext4 drive? I'm using v55.4.17111KViews8likes51CommentsDropbox Client for Linux on Ubuntu 24.04 LTS- icon not clickable.
Guys, I've noticed a bug on Dropbox Client on Ubuntu 23.10 and the same occurs on Ubuntu 24.04 LTS after a installed it from scratch on my machine. It's really a bug on the app on desktop. The problem is: the app on system tray doesnt open or show anything until the system is blocked to block screen and returns putting password. After that it works normally as it should. I recorded a short video showing the problem with you: https://youtu.be/6a4cvtZsRWo How can this issue be solved? Is this the right place to report it? God bless you all!Solved9.2KViews6likes34CommentsUnable to start dropbox in Ubuntu 20.04
Hi, I am unable to start the dropbox in Ubuntu 20.04 with Headless Mode with the following errors. I had read through all the forums and documents to find out the solution in order to fix this error but now lucks. I had already perform `dropbox start` as root but still obtains: Couldn't start Dropbox. This is usually because of a permissions error. Storing your home folder on a network share can also cause an error. Get more help at https://www.dropbox.com/c/help/permissions_error The log of/tmp/dropbox_errorf0tk7axj.txt are shown below: bn.BUILD_KEY: Dropbox bn.VERSION: 131.4.3968 bn.constants.WINDOWS_SHELL_EXT_VERSION: 48 bn.is_frozen: True machine_id: 20210623-1124-0478-1463-487467590001 pid: 30950 ppid: 1 ppid exe: '/usr/lib/systemd/systemd' uid: 0 user_info: pwd.struct_passwd(pw_name='root', pw_passwd='x', pw_uid=0, pw_gid=0, pw_gecos='root', pw_dir='/root', pw_shell='/bin/bash') effective_user_info: pwd.struct_passwd(pw_name='root', pw_passwd='x', pw_uid=0, pw_gid=0, pw_gecos='root', pw_dir='/root', pw_shell='/bin/bash') euid: 0 gid: 0 egid: 0 group_info: grp.struct_group(gr_name='root', gr_passwd='x', gr_gid=0, gr_mem=[]) effective_group_info: grp.struct_group(gr_name='root', gr_passwd='x', gr_gid=0, gr_mem=[]) LD_LIBRARY_PATH: None cwd: '/root' real_path='/root' mode=0o40700 uid=0 gid=0 parent mode=0o40755 uid=0 gid=0 HOME: '/root' appdata: '/root/.dropbox/instance5' real_path='/root/.dropbox/instance5' mode=0o40700 uid=0 gid=0 parent mode=0o40755 uid=0 gid=0 dropbox_path: None not found parent not found sys_executable: '/root/.dropbox-dist/dropbox-lnx.x86_64-131.4.3968/dropbox' real_path='/root/.dropbox-dist/dropbox-lnx.x86_64-131.4.3968/dropbox' mode=0o100755 uid=0 gid=0 parent mode=0o40755 uid=0 gid=0 trace.__file__: '/root/.dropbox-dist/dropbox-lnx.x86_64-131.4.3968/python-packages.zip/dropbox/client/ui/common/boot_error.pyc' real_path='/root/.dropbox-dist/dropbox-lnx.x86_64-131.4.3968/python-packages.zip/dropbox/client/ui/common/boot_error.pyc' not found parent not found tempdir: '/tmp' real_path='/tmp' mode=0o41777 uid=0 gid=0 parent mode=0o40755 uid=0 gid=0 Traceback (most recent call last): File "dropbox/client/main.pyc", line 5397, in _setup_root_for_account AssertionError: fresh link yet no preferences5.2KViews6likes28Comments