| Git Clone URL: | https://aur.archlinux.org/synology-drive.git (read-only, click to copy) |
|---|---|
| Package Base: | synology-drive |
| Description: | Desktop utility of the DSM add-on package, Synology Drive Server |
| Upstream URL: | https://www.synology.com/en-global/releaseNote/SynologyDriveClient |
| Keywords: | client drive nas synology |
| Licenses: | custom:Synology Linux License Grant |
| Conflicts: | cloudstation-3.0, cloudstation-beta, cloudstation-drive, synology-drive, synology-drive-client |
| Submitter: | fmartingr |
| Maintainer: | schinfo |
| Last Packager: | schinfo |
| Votes: | 51 |
| Popularity: | 0.013803 |
| First Submitted: | 2018-01-03 10:34 (UTC) |
| Last Updated: | 2026-01-22 09:15 (UTC) |
@giogio
On your Manjaro ;-) I use Manjaro myself and haven't had any problems yet. An error analysis is not possible with the limited information you provide.
You should also use Google (synology drive client error code 3). It explains exactly step by step what to do if you have this problem.
Can't seem to make synology-drive 4.0.2_17889-1 work on Manjaro.
It starts ok, finds the NAS on my LAN, verify my user and password but then fail with error message -3 and suggests me to contact the official support.
The Synology support chatbot says that Linux rolling releases are not supported and that the problem is probably that the version of gclib on my system is too new (mine is 2.42) or maybe some missing legacy library.
What else can I try? thanks for any help
@Equinox6002:
No, there will be no beta support.
Would it be possible to add a beta branch? https://www.synology.com/de-de/beta/2025_Drive_4_0_0_Beta/release_note#SynologyDriveClient
I have a new workflow where the on-demand sync feature would be useful. The option doesn't show up under sync rules > sync mode like its supposed to. Any idea what I may have configured wrong for this to not show up?
@schinfo
Sorry just now seeing your message. I added that to ~/.bashrc, didn't seem to do anything.
@DamianUntapped
Please try to add the following line to ~/.bashrc
# settings for wayland
export QT_QPA_PLATFORM="xcb"
FYI, setting the QT_QPA_PLATFORM to xcb does not persist through a restart.
I fixed it on Wayland. For anyone else having issues, all I needed to do was run 'set QT_QPA_PLATFORM xcb' in the terminal. Make sure you have wayland qt5 installed with this command 'yay -S qt5-wayland' first. Then start up synology drive and it should work. If you don't want to do all of this every time you log in, I found that editing the synology-drive-autostart.desktop file "exec=" line to this "env QT_QPA_PLATFORM=xcb; synology-drive start" makes it start up at log in. This file can be found at ~/.config/autostart. You will want admin privileges to edit the file (using sudo and an editor like gedit). Another update, sometimes it still wouldn't start at login with these changes, so I duplicated the auto start file and dropped it in this folder ~/.config/autostart-scripts and that seems to be working consistently.
How do I check the exec status of /home?
Pinned Comments
DamianUntapped commented on 2025-04-12 20:54 (UTC) (edited on 2025-05-27 01:13 (UTC) by DamianUntapped)
I fixed it on Wayland. For anyone else having issues, all I needed to do was run 'set QT_QPA_PLATFORM xcb' in the terminal. Make sure you have wayland qt5 installed with this command 'yay -S qt5-wayland' first. Then start up synology drive and it should work. If you don't want to do all of this every time you log in, I found that editing the synology-drive-autostart.desktop file "exec=" line to this "env QT_QPA_PLATFORM=xcb; synology-drive start" makes it start up at log in. This file can be found at ~/.config/autostart. You will want admin privileges to edit the file (using sudo and an editor like gedit). Another update, sometimes it still wouldn't start at login with these changes, so I duplicated the auto start file and dropped it in this folder ~/.config/autostart-scripts and that seems to be working consistently.