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.
I'm using Fedora Workstation 25 with GNOME.
Trying to change the Dropbox directory results in the utterly useless message "Unexpected errors occurred. Your Dropbox is ok!".
Steps to recreate problem:
Observations:
Dear JaneA,
I have 2 OS on my laptop: Windows 10 and Fedora26. All OS install on SSD.
A HDD drive for share data. It's formatted NTFS. And I have dropbox data on this drive.
Dropbox on Windows 10 is ok as it always.
Dropbox on Fedora failed when I relocate to NTFS drive.
The permission in Fedora is ok for all file of dropbox.
Could you show me the log file location of dropbox, so I can trace the problem.
I think Dropbox team try to protect the log file, so user can't access that.
Thanks in advance.
TuanNV
@tharris104 wrote:
I really doubt this issue is beyond Dropbox.
I doubt it's beyond Dropbox, but all the evidence suggests it is very much beyond the support staff who post here, hence my comment about "please help". Seriously, the first reply I got in this thread wasn't even for the right operating system. And look at the "sudo chmod" advice - does that seem like it's written by someone who's used Linux for longer than it took to write that bit of the FAQ? I'm sure the support staff who post here help lots of people, but based on this thread so far it really doesn't seem like they're equiped to provide a solution for a generic error message appearing when a specific operation is attempted with the Linux client on some distros.
Even after raising a support ticket I was given the "sudo chmod" advice again. And then after providing details of a load of tests I'd done on different versions of Fedora, with and without LVM and LUKS, and providing strace output, I was told "sudo chmod" etc. Only after I expressed disatisfaction with that, again, was I told the ticket has been referred to engineering.
If you raise your own support ticket at https://www.dropbox.com/support then, maybe after you've explained to them N times that "sudo chmod" doesn't help, that might get referred to engineering. Maybe more support tickets will mean engineering give greater priority to finding a solution.
@tuannv0708 wrote:
Could you show me the log file location of dropbox, so I can trace the problem.
I think Dropbox team try to protect the log file, so user can't access that.
As I've stated elsewhere in this thread the log is at ~/.dropbox/logs/ and Dropbox support have told me "you won't be able to open them, I'm afraid they are encrypted and can only be decrypted here."
If I were you I'd raise a support ticket at https://www.dropbox.com/support
Okay everyone, I figured out why mine wasn't working.. which is funny becuase this directory has been on my Dropbox since 2012 yet I am just now having issues moving the files..
After the error.. it was always creating the empty directories and I noticed this:
@tharris104 wrote:
Okay everyone, I figured out why mine wasn't working.. which is funny becuase this directory has been on my Dropbox since 2012 yet I am just now having issues moving the files..
After the error.. it was always creating the empty directories and I noticed this:
drwxrwxr-x 2 tharris tharris 4096 Apr 6 2016 Musicdrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:48 Persondrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:44 RubymineProjectsdr-xr-xr-x 2 tharris tharris 4096 Jul 26 2016 SEP-MP5drwxrwxr-x 2 tharris tharris 4096 Aug 8 15:59 Softwaredrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:44 Workdrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:45 XonoticI went to the web interface and removed that shared drive from another Dropbox user.. went to move.. and no more error. So possibly if you have folders that are shared from other dropbox users, this may be whats causing issues with permissions so removing that at least gets data stored on bigger drive...
Which means the problem you were encounting is completely different to the issue I'm encountering.
Just saying... you should check permissions on those empty directories.. or even on their website.. it will have a lock next to the icon.
@tharris104 wrote:
Just saying... you should check permissions on those empty directories.. or even on their website.. it will have a lock next to the icon.
What empty directories?
I have no shared folders. I can reproduce the problem even after deleting everything in my Dropbox directory. I can move the Dropbox directory within ${HOME}. I think we have both encountered things that cause the Dropbox client to chuck out the same generic error message but the underlying issues are entirely different.
mike _. wrote:What empty directories?
I have no shared folders. I can reproduce the problem even after deleting everything in my Dropbox directory. I can move the Dropbox directory within ${HOME}. I think we have both encountered things that cause the Dropbox client to chuck out the same generic error message but the underlying issues are entirely different.
You are probably right aboout that.. The directories I am talking about are created on the mount (or wherever your moving to) after trying to move the folders.. I was messing with mount points and actually ended up with my 2TB mounted inside home. But after looking at the empty folders, thats when I saw the permissions it was trying to move..
100% match to my issue, Usng Fedora 26 - Followed all the permisson changes in this thread. However I can move the "~/Dropbox" directory in to a "~/subfolder?Dropbox" sync works. Unable to move Dropbox folder to another partion on same SSD or any HDD Drive. (internal or external).. Would you recommned I open a new ticket to raise the awareness to support?
@pix365 wrote:
100% match to my issue, Usng Fedora 26 - Followed all the permisson changes in this thread. However I can move the "~/Dropbox" directory in to a "~/subfolder?Dropbox" sync works. Unable to move Dropbox folder to another partion on same SSD or any HDD Drive. (internal or external).. Would you recommned I open a new ticket to raise the awareness to support?
Yep, sounds like same issue I encoutered. Dropbox support told me earlier today that engineering are "not actively working on a solution for this problem". Which is disapointingbut not particularly surprising given the obscureness of the issue and the number of people who'd be affected by it.Someone else raising a ticket may make them more inclined to look at the issue. Tell them you think you're encounting the same issue as ticket 6168712.
It'd be interesting to know if the issue occurs on any distro other than Fedora. I can't replicate it on openSUSE. I've not tried any other distros. I've not yet had time/inclination to try other distros.
Hi there!
If you need more help you can view your support options (expected response time for a 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!