You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the client refuses to keep its Nextcloud_sync.log file in the /home/[user]/.config/Nextcloud directory. No matter what I do, the client keeps re-creating its log file in .local/share/Nextcloud, even after total directory deletion.
Steps to reproduce
Delete the old .local/share/Nextcloud directory
Start Nextcloud
Everything starts correctly (no output error), but the .local/share/Nextcloud is recreated with the Nextcloud_sync.log
Restart Nextcloud, this output shows up :
nextcloud.gui.application: Migrating old config from "/home/[user]/.local/share/Nextcloud" to "/home/[user]/.config/Nextcloud"
nextcloud.gui.application: Failed to move the old config directory to its new location ( "/home/[user]/.local/share/Nextcloud" to "/home/[user]/.config/Nextcloud" )
nextcloud.gui.application: Will move the individual files ("Nextcloud_sync.log")
Everything starts correctly, a new Nextcloud_sync.log is created in .config/Nextcloud, but only the one in .local/share/Nextcloud gets updated
Restart Nextcloud, this output shows up :
nextcloud.gui.application: Migrating old config from "/home/[user]/.local/share/Nextcloud" to "/home/[user]/.config/Nextcloud"
nextcloud.gui.application: Failed to move the old config directory to its new location ( "/home/[user]/.local/share/Nextcloud" to "/home/[user]/.config/Nextcloud" )
nextcloud.gui.application: Will move the individual files ("Nextcloud_sync.log")
nextcloud.gui.application: Fallback move of "Nextcloud_sync.log" also failed
Everything starts correctly, the .local/share/Nextcloud_sync.log gets updated, the .config/Nextcloud one is left abandoned, without being updated
Rinse and repeat
Expected behavior
I think the log file should now be .config/Nextcloud/Nextcloud_sync.log, the .local/share/Nextcloud one should not be recreated if it doesn't exist anymore.
Which files are affected by this bug
.config/Nextcloud/Nextcloud_sync.log
Operating system
Linux
Which version of the operating system you are running.
Arch Linux
Package
Distro package manager
Nextcloud Server version
Unknown
Nextcloud Desktop Client version
3.13.0
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?
Default internal user-backend
LDAP/ Active Directory
SSO - SAML
Other
Nextcloud Server logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered:
Bug description
Hello there 👋
It seems like the client refuses to keep its
Nextcloud_sync.log
file in the/home/[user]/.config/Nextcloud
directory. No matter what I do, the client keeps re-creating its log file in.local/share/Nextcloud
, even after total directory deletion.Steps to reproduce
.local/share/Nextcloud
directory.local/share/Nextcloud
is recreated with theNextcloud_sync.log
Nextcloud_sync.log
is created in.config/Nextcloud
, but only the one in.local/share/Nextcloud
gets updated.local/share/Nextcloud_sync.log
gets updated, the.config/Nextcloud
one is left abandoned, without being updatedExpected behavior
I think the log file should now be
.config/Nextcloud/Nextcloud_sync.log
, the.local/share/Nextcloud
one should not be recreated if it doesn't exist anymore.Which files are affected by this bug
.config/Nextcloud/Nextcloud_sync.log
Operating system
Linux
Which version of the operating system you are running.
Arch Linux
Package
Distro package manager
Nextcloud Server version
Unknown
Nextcloud Desktop Client version
3.13.0
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?
Nextcloud Server logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: