Hey, thanks for testing the experimental version. Than I need to refactor the patch that was fixing the issue on 3.15.
> What's worse, if I mount the data partition with ntfs3 (instead of > ntfs-3g), nextcloud-desktop will just segfault. A segfault is often easier to hunt down. Can you provide these changes and the segfault on the upstream bugreport? Regards, hefee -- On Dienstag, 22. Juli 2025 21:39 you wrote: > Am 21.07.25 um 20:29 schrieb Hefee: > > > Hey, > > > > nextcloud 3.16.5/6 had a lot fixes that cares about read-only files and > > endless loop on Linux[1]. That touches the code that was reverted to fix > > #1091614. My guts feeling is that it may fixes your issue. See > > > > https://github.com/nextcloud/desktop/pull/8290 > > > > With this patch added by upstream, I think it is time to check if the > > issue is fixed by upstream. > > > > So I created a experimental version 3.16.6-1 where I removed the reverts > > for #1091614. > > > > Can you check, if the busy loop issue is fixed within that version? > > > > Regards, > > > > hefee > > > > [1] https://github.com/nextcloud/desktop/releases > > > > If tested the experimental build. Unfortunately the issue is not fixed. > Mounting the data partition with ntfs-3g, it still enters a busy loop. > > What's worse, if I mount the data partition with ntfs3 (instead of > ntfs-3g), nextcloud-desktop will just segfault. > > Michael
signature.asc
Description: This is a digitally signed message part.
