⚠️ Before submitting, please verify the following: ⚠️
Bug description
Starting NextCloud Desktop 33.0.2 on Linux migrates the config from ~/.local/share/NextCloud to ~/.config/NextCloud, but logfiles are still written to ~/.local/share/NextCloud after the config migration
This results in the following messages to stderr on the next start (with 3 sync targets defined):
$ nextcloud
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 QList("A_sync.log", "B_sync.log", "C_sync.log")
nextcloud.gui.application: Fallback move of "A_sync.log" also failed
nextcloud.gui.application: Fallback move of "B_sync.log" also failed
nextcloud.gui.application: Fallback move of "C_sync.log" also failed
and logfiles are still written to /home/user/.local/share/Nextcloud
Removing the folder /home/user/.local/share/Nextcloud while the client is closed removes these errors on the next start, but as the folder is recreated to write the logfiles there... it's back to square one.
Steps to reproduce
- upgrade a 4.x to 33.0.1 on Linux
- start and exit "nextcloud"
- rm ~/.local/share/Nextccloud
- start nextcloud again
- ls ~/.local/share/Nextccloud
Expected behavior
Migration should happen only once, logfiles should be written to the new location.
Which files are affected by this bug
~/.local/share/NextCloud
Operating system
Linux
Which version of the operating system you are running.
Linux Mint 21.3 Cinnamon 6.0.4
Package
Distro package manager
Nextcloud Server version
Nextcloud Hub 25 Autumn (32.0.8)
Nextcloud Desktop Client version
33.0.2-20260401.075017.54f537e35f-1.0~jammy1
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 4.x to 33.0.x)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
(exclusive Client side problem, thus no server logs)`
Additional info
The "create debug archive" button in Settings -> General is greyed out, debug logs could be created with "F12" but the string .local/share could not be found in any of the debug logs created.
Bug description
Starting NextCloud Desktop 33.0.2 on Linux migrates the config from ~/.local/share/NextCloud to ~/.config/NextCloud, but logfiles are still written to ~/.local/share/NextCloud after the config migration
This results in the following messages to stderr on the next start (with 3 sync targets defined):
and logfiles are still written to /home/user/.local/share/Nextcloud
Removing the folder /home/user/.local/share/Nextcloud while the client is closed removes these errors on the next start, but as the folder is recreated to write the logfiles there... it's back to square one.
Steps to reproduce
Expected behavior
Migration should happen only once, logfiles should be written to the new location.
Which files are affected by this bug
~/.local/share/NextCloud
Operating system
Linux
Which version of the operating system you are running.
Linux Mint 21.3 Cinnamon 6.0.4
Package
Distro package manager
Nextcloud Server version
Nextcloud Hub 25 Autumn (32.0.8)
Nextcloud Desktop Client version
33.0.2-20260401.075017.54f537e35f-1.0~jammy1
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 4.x to 33.0.x)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
(exclusive Client side problem, thus no server logs)`
Additional info
The "create debug archive" button in Settings -> General is greyed out, debug logs could be created with "F12" but the string
.local/sharecould not be found in any of the debug logs created.