Arch Linux User Repository

IMPORTANT !!! - Version 3.5.1-16102 fixed an security vulnerability. (Synology-SA-24:21)

This package might be incorrectly flagged out-of-date because the new DSM 7 is not released yet to the public. Synology released a release candidate of it in June 2021, Version: 7.0-41882 [1]. The newest Synology Drive client was released to be compatible with the new DSM 7, but older NAS with DSM 6 might still provide the version 2.0.3-11102 to download.

Nevertheless, I successfully got the newest Synology Drive version built and it's running without any problem so far. Here is my PKGBUILD diff.

--- PKGBUILD.orig   2021-06-14 22:25:17.663862087 +0200
+++ PKGBUILD    2021-06-14 22:22:23.686091193 +0200
@@ -13,11 +13,11 @@
 source=()
 md5sums=()

-source_i686=(https://global.download.synology.com/download/Utility/SynologyDriveClient/2.0.4-11112/Ubuntu/Installer/i686/synology-drive-client-11112.i686.deb)
-md5sums_i686=('5d0d8f8fc6d0aefa0b1fe707289fb2fc')
+source_i686=(https://global.download.synology.com/download/Utility/SynologyDriveClient/3.0.1-12664/Ubuntu/Installer/i686/synology-drive-client-12664.i686.deb)
+md5sums_i686=('7e3dc5fd2b9c38f073ea677689f9eab2')

-source_x86_64=(https://global.download.synology.com/download/Utility/SynologyDriveClient/2.0.4-11112/Ubuntu/Installer/x86_64/synology-drive-client-11112.x86_64.deb)
-md5sums_x86_64=('0bff75d3e9a1a6eed8fd4c8351ba4104')
+source_x86_64=(https://global.download.synology.com/download/Utility/SynologyDriveClient/3.0.1-12664/Ubuntu/Installer/x86_64/synology-drive-client-12664.x86_64.deb)
+md5sums_x86_64=('0788446c2de2e05127c3b2b0f03c5131')

 prepare() {
    cd "$srcdir"

[1] https://www.synology.com/en-global/releaseNote/DSM

Hey @iyanmv, thanks a lot for your input! I will try to fix most of this for the next release of the package so I don't break versioning. Regarding why the dependencies, this comes from the previous cloud-drive application that required those (it won't install otherwise). I will fire up a VM to check out everything from scratch. Thanks again!

Hi @fmartingr. Thanks for maintaining this package. I wrote some time ago about an issue with this app using dark color themes. I was able to replicate the issue in Ubuntu so I opened a ticket in the Synology support website. It is an issue with the drive.stylesheet and component.default.stylesheet files. I will write back here if they offer any workaround or fix.

Regarding the PKGBUILD here, there are some issue as well:

1. 11112 is part of the official release version, so you should use it accordingly: pkgver=2.0.4_11112. Note that I replace the hyphen with an underscore as mentioned in the guidelines [1].

2. pkgrel is meant to distinguish different builds from the same upstream versions. For example, when you do a change in the PKGBUILD. You should replace 11112 with 1. But note that when doing that, AUR helpers will believe it is a downgrade so you should also enable the epoch. Again, check [1].

3. You should change license to custom and install the license file in the right place [2]. You can add something like this at the end of package() function.

install -Dm 644 "${pkgdir}"/opt/Synology/SynologyDrive/LICENSE.txt "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"

1. I don't understand where did you get the dependencies. If you check the .deb package, this is what you get:

$ dpkg -I synology-drive-client-11112.x86_64.deb 
(...)
 Depends: libc6 (>= 2.19), libglib2.0-0 (>= 2.16.0), libgtk2.0-0 (>= 2.12.0)
 Suggests: nautilus (>= 3.4.2)
(...)

So why binutils, fontconfig and libsm are dependencies?

1. (Optional) You can achieve the same you are doing in both prepare() and package() with two lines in package():

cd "${srcdir}"
tar -xJf data.tar.xz -C "${pkgdir}"

1. (Optional) It would be nice to check if the app can run using the libraries provided by Archlinux. Most of libraries included by Synology in the .deb are available in the system adding qt5-base, qt5-svg, curl, openssl, zlib and sqlite to dependencies. But this may be a bit of extra work.

[1] https://wiki.archlinux.org/index.php/PKGBUILD#Version

[2] https://wiki.archlinux.org/index.php/PKGBUILD#license

@ram4nd Try with this PKGBUILD: https://code.fmartingr.dev/fmartingr/aur-packages/src/branch/master/synology-drive/builds/3.0.0-12467/PKGBUILD

If there isn't many changes in the new major it should work as the stable ones, but I'm not using the beta so I can't test it properly.

Can you create another version for DSM 7 beta? https://prerelease.synology.com/en-global/download/dsm70_beta?builtin_name=synology_rtd1296_ds218

Hi fmartingr, I just saw your answer here (thanks, by the way!!), but as it turns out I was in the meantime writing a post on Reddit about it.

It's this one!

It's based on my comment here, but I ended up putting a lot more details on my post there, together with some screenshots.

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?