Arch Linux User Repository

Hey rsaffi, I haven't experienced this before and I have several files from the extensions you see as blocked:

$ cd ~/SynologyDrive

$ find . -name "*.html" | wc -l
1684

$ find . -name "*.pdf" | wc -l
1332

$ find . -name "*.xls" | wc -l
66

$ find . -name "*.xlsx" | wc -l
33

But I don't have all those extensions as blocked on the database file you mention:

$ sqlite3 filter.sqlite "select * from filter_table"
1|0|-13|/Backup
1|0|-13|/Moments
1|0|-2|.lnk
1|0|-2|.pst
1|0|-2|.swp
1|0|-2|.temp
1|0|-2|.tmp
1|0|-4|.
1|0|-15|0

I think is better if you open a thread on the Forums 0 and give us the link here so we can follow the conversation and help you with your issue, to keep this comment section relevant to packaging only.

Guys, I created my account here so I could ask this question: I was just able to analyze Synology Drive application for Linux (v2.0.3-11102, but same applies for v3.0.0-12467 for what I've checked) and I'm baffled that nobody else mentioned it here.

I don't think it's a problem with the package provided here, but rather with the application itself. Since you all most likely also USE it, I though it'd be a good place to ask, as I couldn't find it when searching the web.

Do any of you also noticed that the Synology Drive application (for Linux only!) doesn't sync some very specific filetypes? I investigated this deep, first by looking into the application logs on ~/.SynologyDrive/log and realizing that it was denying syncing such files by saying:

2021-01-06T19:28:25 (32080:45248) [WARNING] download-remote-handler.cpp(525): Filtered Event (session): '/path/to/some/file.pdf'. (blocked: -264).
2021-01-06T19:28:25 (32080:45248) [INFO] download-remote-handler.cpp(578): Worker (13): File '/home/ricardo/SynologyDrive/path/to/some/file.pdf' cannot pass filter testing '-131336'.

I continued my investigation and found ~/.SynologyDrive/data/db/filter.sqlite. Upon playing around with the Filter option available on the GUI, I could pinpoint that it was adding the entries to the table filter_table. That's when I got confirmation that Synology is explicitly blocking A LOT of filetypes on the Linux client. Not only I can't upload such files to Drive but my client also doesn't download them due to the filters.

These are the filetypes I see on that table: .aac, .aif, .aifc, .aiff, .ape, .au, .cdda, .dff, .doc, .docx, .dsf, .eaac, .epub, .flac, .htm, .html, .kar, .key, .l16, .lnk, .m3u, .m4a, .m4b, .m4p, .mid, .midi, .mobi, .mp1, .mp2, .mp3, .mpc, .mpga, .numbers, .odp, .ods, .odt, .ogg, .pages, .pcm, .pdf, .pls, .pps, .ppsx, .ppt, .pptx, .pqp, .prc, .pst, .ra, .ram, .snd, .swp, .temp, .tmp, .tta, .txt, .vqf, .wav, .wma, .xls, .xlsx. I noticed this exactly when I realized that no PDF or ODT files were being neither fetched from my NAS nor being sent to it.

Keep in mind that I tried to manually delete them from the database on-the-fly, but it doesn't help. And upon closing and opening the application, that table is repopulated with those entries (plus any manual exclusions one can put in place from the GUI). I even tried to delete those entries and add an immutable extended attribute to the filter.sqlite file before starting the application, but that makes it crash on startup.

Anyone else with the same issue? I truly apologize asking this here. Feel free to delete this if you see fit.

Hey iyanmv, I'm sorry but I haven't experienced anything like that. Would you mind telling us more about your issue? Maybe open a thread in the archlinux forums explaining it (with some details about your window manager, desktop, etc). A screenshot would be nice as well. This way we could try to guess what's the problem.

I opened a ticket in Synology support but we couldn't figure it out the problem. Also I cannot replicate the issue in Ubuntu 20.04 so it must be something specific from Arch. Any ideas? Can anyone replicate my issue?

Hi, I was using Synology Cloud Station Backup but it seems like Synology Drive is a replacement for that app. However, with this app, after introducing the address and credentials to connect to the Synology, the screen to choose the directories to backup it's shown with wrong colors. Everything is dark and only when I put the mouse on top of a folder I can read the name of the directory. Anyone else having same issue? It's like the color scheme is totally wrong. Any ideas how to solve this?

Hey folks, I've updated the package to 2.0.3-11102. I'm not doing beta updates here (keeping it to stable builds). I've also fixed the md5 sum for i686 builds (I wasn't filling that).

If not on beta DSM, still using 6, drive client updated to 2.0.3. Not sure how to do pull requests, but here's my PKGBUILD diff. FYI, I could not find i686 version.

diff --git a/PKGBUILD b/PKGBUILD
index def3264..0f367d5 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,10 +1,10 @@
 # Maintainer: Felipe Martin <me@fmartingr.com>

 pkgname="synology-drive"
-pkgver="2.0.2"
-pkgrel="11078"
+pkgver="2.0.3"
+pkgrel="11102"
 pkgdesc="Drive for PC, the desktop utility of the DSM add-on package, Drive, allows you to sync and share files owned by you or shared by others between a centralized Synology NAS and multiple client computer    -arch=('i686' 'x86_64')
+arch=('x86_64')
 url="https://www.synology.com"
 license=('unknown')
 depends=('glibc' 'libsm' 'binutils' 'fontconfig' )
@@ -13,11 +13,11 @@ conflicts=('cloudstation-beta' 'cloudstation-3.0' 'cloudstation-drive' )
 source=()
 md5sums=()

-source_i686=(https://global.download.synology.com/download/Tools/SynologyDriveClient/2.0.2-11078/Ubuntu/Installer/i686/synology-drive-client-11078.i686.deb)
+source_i686=()
 md5sums_i686=('')

-source_x86_64=(https://global.download.synology.com/download/Tools/SynologyDriveClient/2.0.2-11078/Ubuntu/Installer/x86_64/synology-drive-client-11078.x86_64.deb)
-md5sums_x86_64=('67c77b95a4a3572bae61c2e6cdddf1a5')
+source_x86_64=(https://global.download.synology.com/download/Utility/SynologyDriveClient/2.0.3-11102/Ubuntu/Installer/x86_64/synology-drive-client-11102.x86_64.deb)
+md5sums_x86_64=('8be197272d8f25c5cc82a31621e2199c')

 prepare() {
    cd "$srcdir"

@cmuench Thanks for the info, a reinstall fixed it for me

@archlinuxomane I just downloaded the package and replaced the .deb url in the PKGBUILD and was able to install the latest x86_64 release. In my homedir the ~/.SynologyDrive/SynologyDrive.app/lib/plugins/platforms/libqxcb.so file exists. Maybe it is a different issue. The file was right now created after the start of the client.

with DSM7, which is now in beta, a new version was released: https://global.download.synology.com/download/Utility/SynologyDriveClient/3.0.0-12467/Ubuntu/Installer/x86_64/synology-drive-client-12467.x86_64.deb

I can't get it to work with the old PKGBUILD, some error with the qt5-framework:

QFactoryLoader::QFactoryLoader() checking directory path "/home/foo/.SynologyDrive/SynologyDrive.app/bin/platforms" ...

Cannot load library /home/foo/.SynologyDrive/SynologyDrive.app/lib/plugins/platforms/libqxcb.so: (libfontconfig.so.1: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden)

QLibraryPrivate::loadPlugin failed on "/home/foo/.SynologyDrive/SynologyDrive.app/lib/plugins/platforms/libqxcb.so" : "Cannot load library /home/foo/.SynologyDrive/SynologyDrive.app/lib/plugins/platforms/libqxcb.so: (libfontconfig.so.1: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden)"

qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.

This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: linuxfb, minimal, offscreen, vnc, xcb.