-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shared folder get a (2) added at the end, only on ONE client and content is not synchronized #28381
Comments
@alcordier you probably found #25564. If it is likely, please close your ticket as duplicate |
Hi Vincent, I don't think it is related to #25564: I have only one group in my case and the directory is only shared with users, not group. Alain |
Is there anything I can do to help solving this problem ? |
I do not have time to look into this problem right now, sorry. Ideal would be to have steps to reproduce the issue reliably, even on new installs. If that is not possible, it means there is something specific to your setup, maybe a specific configuration or a specific configuration of shares that other setups usually don't have. Could be broken share entries or so. I suggest you look at the "oc_share" table and search files_target for the "(2)" entry, then connect with the "id" by "oc_share.parent" from the result. Find related entries. If you find anything, post it. |
There are no parent defined on any share, all have NULL.
Below is an example of a share on which the problem occurs. It is Ok for all users except user1 where it get a (2) appended whatever I try (utilitest is me):
|
Next to check:
|
I already checked for another "Demolition-tour-Lbis-" folder. The answer is no (and same answer for other folders). I also tried to put owncloud in maintenance mode and empty oc_filecache with no success. However, I just realized that user1 has a "Demolition-tour-Lbis-" in his personal folders. |
Please never empty filecache. Now all your shares are orphaned as they don't have a matching fileid to point to. If you did this in the past it could be the reason for some side effects. |
Hey, this issue has been closed because the label |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Steps to reproduce
Expected behaviour
The shared folder should keep his name.
This looks similar to #25718, but there is only one group, and no LDAP involved...
Actual behaviour
On one of my clients descktop (Windows), a particular shared folder get continuously renamed with a (2) appended. This only occurs on this computer, and he get twice the folders in the onwnCloud client list (one normal, one with "(2)" at the end), but the folder appears only once in the local filesystem (normal name).
I tried various techniques in the hope of solving this, but none worked:
update
oc_share
set file_target='/Demolition-tour-Lbis-' where id=1480;but the name is changed as soon as the client reconnects !
Server configuration
Operating system: CentOS Linux release 7.3.1611 (Core)
Web server: Apache/2.4.6
Database: 5.5.52-MariaDB MariaDB Server
PHP version: 7.0.19
ownCloud version: (see ownCloud admin page) ownCloud 9.1.6 (stable)
Updated from an older ownCloud or fresh install: updated from 8 one year ago
Where did you install ownCloud from: from official website + updates
Signing status (ownCloud 9.0 and above):
Login as admin user into your ownCloud and access
http://example.com/index.php/settings/integrity/failed
paste the results into https://gist.github.com/ and puth the link here.
No errors have been found.
The content of config/config.php:
List of activated apps:
Enabled:
Disabled:
Are you using external storage, if yes which one: local/smb/sftp/...
YES: Local
Are you using encryption: yes/no
No
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
No
LDAP configuration (delete this part if not used)
Client configuration
Browser: Firefox up to date
Operating system: Windows 10, owncloud Version 2.3.2 (build 6928)
The text was updated successfully, but these errors were encountered: