Closed baumkirchner closed 1 year ago
Sounds like https://github.com/nextcloud/server/pull/36161
cc @icewind1991 @nickvergessen
Hi, please update to 25.0.7 or better 26.0.2 and report back if it fixes the issue. Thank you!
My goal is to add a label like e.g. 26-feedback to this ticket of an up-to-date major Nextcloud version where the bug could be reproduced. However this is not going to work without your help. So thanks for all your effort!
If you don't manage to reproduce the issue in time and the issue gets closed but you can reproduce the issue afterwards, feel free to create a new bug report with up-to-date information by following this link: https://github.com/nextcloud/server/issues/new?assignees=&labels=bug%2C0.+Needs+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+
This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.
⚠️ This issue respects the following points: ⚠️
Bug description
All folders shared by one user are displayed twice for the recipients of the share after update from 24.0.8.2 to 24.0.9.2. The resp. first one has the original name, seems to be empty and its sharing dialogue mentions server error. The resp. second one is displayed as "original name (2)", contains the original contents and sharing settings. On some but not all shares the recipient of the share was able to leave the share with the original name. Then after removing the share and resharing, both by the original owner of the share, the recipient received a working share with the original name. The error seems "curable" this way, but this is needed to be done for each single user and each single share separately. And in some cases this is not possible at all, the failed share stays tenaciously and can be neither accessed nor removed nor leaved nor repaired by resharing by the share owner. Neither
occ maintenance:repair
norocc maintenance:repair-share-owner
helped.Steps to reproduce
This is a static behaviour since the update mentioned above and not reproducible on demand
Expected behavior
All folders are displayed correctly with correct sharing for all share recipients
Installation method
Community Manual installation with Archive
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.0
Web server
Nginx
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 22.2.3 to 22.2.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
The first error (id: CWsXK068EE5EO6TJYbGd) has been triggered when i try to access one of the failed shares as the recipient of the share. The second one (id: luFkgwirsNtLTuBQNYXo) is triggered by trying to leave the failed share as the recipient of the share. The third one (id: i70o1aINIfqdSoJsIL7Q) comes when trying to display the sharing settings of the failed share as the recipient of the share