Broken permissions on Nextcloud folder after every reboot

AdamAnon · August 11, 2024, 8:15am

I’ve updated Windows clients to 3.13.2 few days ago. Ever since, permissions on my Nextcloud folder on all my PCs are broken after every reboot and it refuses to sync. I get a red icon in the tray and an error “Unable to open or create sync database. Make sure you have write access to the sync folder.”

My sync folder is inside my home directory and inherits permissions like all other folders. However, permissions for Users get changed to Deny/Write on every reboot for the Nextcloud folder. This doesn’t happen to any other folders, only to the Nextcloud folder.

mritzmann · August 12, 2024, 2:48pm

I’m not sure if this is related:

github.com/nextcloud/desktop

[Bug]: Folder permissions are changed during synchronization (3.13.1 & 3.13.2)

opened 05:27PM - 30 Jun 24 UTC

TopMax

0. Needs triage

### ⚠️ Before submitting, please verify the following: ⚠️ - [X] This is a **b…ug**, not a question or a configuration issue. - [X] This issue is **not** already reported on Github (I've searched it). - [X] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions. - [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/) ### Bug description After updating from 3.13.0 to 3.13.1, this error occurs. If a file is updated in an existing folder, the permissions are modified for all folders directly above it up to the sync root folder, the folders become writable for groups and others. Another way is to simply create a new folder for example in the sync root folder. Directly after creation, the folder then has the following rights, for example `drwx------ 2 user user 4096 Jun 30 19:14 test`. After the folder was synchronized, the rights have now changed, in this example `drwx-w--w- 2 user user 4096 Jun 30 19:14 test`. There are no log entries for either the server or the client. After downgrading from 3.13.1 to 3.13.0, this error no longer occurs. ### Steps to reproduce 1. Create a new folder with only read, write and execute permission for the user. 2. After the synchronization is complete check the permissions 3. The permissions changed to allow the group and other to write to the folder --- 1. Create a new file in a previously created folder (older client versions) and check that this folder only has read, write and execute permission for the user. 2. Create a new file in this folder or modify an existing one. 4. After the synchronization is complete check the permissions of the folder 5. The permissions changed to allow the group and other to write to the folder ### Expected behavior After the synchronization no folder permissions are changed. ### Which files are affected by this bug custom created test folder ### Operating system Linux & macOS ### Which version of the operating system you are running. Arch Linux & Debian 12 ### Package Distro package manager & AppImage ### Nextcloud Server version 29.0.3 ### Nextcloud Desktop Client version 3.13.1 & 3.13.2 ### Is this bug present after an update or on a fresh install? Updated from a minor version (ex. 3.4.2 to 3.4.4) ### Are you using the Nextcloud Server Encryption module? Encryption is Disabled ### Are you using an external user-backend? - [x] Default internal user-backend - [ ] LDAP/ Active Directory - [ ] SSO - SAML - [ ] Other ### Nextcloud Server logs _No response_ ### Additional info _No response_

AdamAnon · August 12, 2024, 3:07pm

Hmmm, maybe. In my case the permissions were changed to be more restrictive only on the Nexctloud folder itself on reboot, immediatelly after first reboot after update - Users were set Deny Write so sync would stop. This happened on every reboot. I’ve reset the permissions several times over and over and it no longer happens. I rebooted all PCs repeatedly and it’s OK now.

AdamAnon · August 19, 2024, 9:49am

OK, this is getting SUPER IRRITATING. It’s happening again. Every time I reboot my PCs, permissions on the Nextcloud folder are changed to deny write to Users. I’m going to try to downgrade all clients to 3.13.0. I’m getting so tired of problems with Nextcloud upgrades, both servers and now even the client.

juampii · August 29, 2024, 12:12pm

This is happening in a few instances i have where virtual files is used, this and the slow sync speed with folders with lots of files are annoying. For example sync with the owncloud client speed up the proces like 100x. i imagine with owncloud server all runs way better, so time to change back again.

AdamAnon · August 29, 2024, 12:52pm

No virtual files are used on my instance. It’s a small, single-user installation on 2.5Gbps LAN. Sync is very fast, I have redis and all… The 3.13.2 client was simply bugged. I rolled back all my clients to 3.13.0 and it stopped happening.

Taomyn · August 31, 2024, 9:42am

v3.13.3 continues with this issue

AdamAnon · August 31, 2024, 10:02am

Nice! OK, so no more client updates for me, I guess.

constructed · August 31, 2024, 12:54pm

This is really annoying and happens to me as well. Even that I don’t reboot my machine at all, it’s just happening every “real” sync or somewhat less frequent. I wouldn’t even notice that without ansible throwing an error about 777 permissions on role repository. I have to run ‘find ~/Nextcloud -type d -perm 777 -exec chmod 755 {} ;’ to fix this problem. Have rolled back to 3.12.7 and hopefully it won’t happen again. But outdated client notifications will be probably less annoying and I’ve just opted-out automatic new version checking.

AdamAnon · August 31, 2024, 1:13pm

So you’re having the same client problem on a Linux desktop? Interesting.

kevriq · October 2, 2024, 1:08pm

Hello, i encounter exactly the same problem on Windows. The update to 3.14.1 apparently did not resolve this problem. Still current on your side? THANKS