ownCloud client fails to apply custom targetPath and always defaults to /

[Kwallie010]

Pre-submission Checks

• I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
• I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.

Describe the bug

When using the ownCloud desktop client (v5.3.2.15463 on Fedora 42), syncing a local folder to a custom remote path (e.g. /Documents, /Videos) fails — the client ignores the specified path and instead sets the target path to / in the configuration file (~/.config/ownCloud/owncloud.cfg).

As a result, all local folders are synced to the root of the remote space, rather than into their respective directories.

Expected behavior

The client should store and respect the configured remote folder path.
For example: syncing /home//Documents to /Documents should result in:
targetPath=/Documents

Actual behavior:
Despite selecting a target path in the GUI, the config always shows:
targetPath=/
This results in all sync folders being merged into the root directory on the server.

Steps to reproduce the issue

1. Start the ownCloud client
2. Add a new folder to sync:
   • Local: /home//Documents
   • Remote: /Documents
3. Complete the setup and inspect ~/.config/ownCloud/owncloud.cfg
4. Observe:
   targetPath=/
5. Do the same for Videos, Homelab, etc — all get targetPath=/

Screenshots

No response

Logs

No response

Client version number

Client version:
ownCloud version 5.3.2.15463
OS: Fedora 42
Server version:
ownCloud Infinite Scale 5.3 (self-hosted)

Desktop environment (Linux only)

KDE Plasma

Client package version and origin (Linux only)

Fedora_41 repository via DNF (no Fedora_42 repo exists yet): https://download.owncloud.com/desktop/ownCloud/stable/latest/linux/download/

Installation path (Windows only)

No response

Server information

ownCloud Infinite Scale 5.3 (self-hosted via Docker) on a Raspberry PI 5 running Raspberry PI OS / Debian GNU/Linux 12 (bookworm)

Additional context

• targetPath remains / even after removing and re-adding the sync with a different remote path
• Might be a GUI bug or config-writing issue
• Possibly related to client/server mismatch or Fedora 42 support missing