Package Details: synology-drive 3.5.2_16111-3

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: 1.43
First Submitted: 2018-01-03 10:34 (UTC)
Last Updated: 2025-05-08 19:42 (UTC)

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.

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

DamianUntapped commented on 2025-05-07 00:43 (UTC)

@schinfo

Sorry just now seeing your message. I added that to ~/.bashrc, didn't seem to do anything.

schinfo commented on 2025-04-17 10:58 (UTC) (edited on 2025-04-17 11:00 (UTC) by schinfo)

@DamianUntapped

Please try to add the following line to ~/.bashrc

# settings for wayland
export QT_QPA_PLATFORM="xcb"

DamianUntapped commented on 2025-04-16 22:39 (UTC)

FYI, setting the QT_QPA_PLATFORM to xcb does not persist through a restart.

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.

DamianUntapped commented on 2025-03-24 12:45 (UTC)

How do I check the exec status of /home?

schinfo commented on 2025-03-24 09:55 (UTC)

@DamianUntapped

Take a look at the old comment here on page 2 (Moabeat commented 2023-09-13 22:32).

Maybe that will help you too.

schinfo commented on 2025-03-24 09:45 (UTC)

Then I assume that Synology Wayland does not support.

DamianUntapped commented on 2025-03-23 21:41 (UTC)

Running pacman -Qs qt5-wayland returns: local/qt5-wayland 5.15.16+kde+r60-1 (qt5) Provides APIs for Wayland

So I think it is installed?

schinfo commented on 2025-03-23 18:47 (UTC) (edited on 2025-03-23 18:48 (UTC) by schinfo)

Please see if you have installed qt5-wayland

DamianUntapped commented on 2025-03-23 17:14 (UTC)

@schinfo

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.

1 2 3 4 5 6 .. 9 Next › Last »