Package Details: syncthingtray 2.0.2-1

Git Clone URL: https://aur.archlinux.org/syncthingtray.git (read-only, click to copy)
Package Base: syncthingtray
Description: Tray application for Syncthing
Upstream URL: https://github.com/Martchus/syncthingtray
Licenses: GPL-2.0-or-later
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 96
Popularity: 1.38
First Submitted: 2016-09-14 20:13 (UTC)
Last Updated: 2025-09-26 20:38 (UTC)

Pinned Comments

Martchus commented on 2025-10-07 15:00 (UTC)

AT THIS POINT YOU ALMOST CERTAINLY WANT TO USE https://aur.archlinux.org/packages/syncthingtray-qt6 INSTEAD.

Martchus commented on 2016-10-31 11:39 (UTC) (edited on 2025-05-03 08:48 (UTC) by Martchus)

All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs
There also exist a binary repository: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#ownstuff

Important remarks:

  • Switch to the Qt 6 based version. There is probably no good reason to still use the Qt 5 based version under GNU/Linux.
  • The packages within the binary repository are built against the latest packages from Arch Linux and hence might not be compatible with Manjaro. This can be the cause when the Plasmoid doesn't work.
  • Like with any other package a rebuild is required when the soname of a dependency like boost changes (see e.g. https://github.com/Martchus/syncthingtray/issues/98). The package in my binary repository should be rebuilt in a timely manner. I'm also sometimes updating pkgrel of the AUR package when a rebuild is required (only in accordance with Arch Linux of course, not in accordance with Manjaro).
    • The "dirty" way is forcing the installation/update (leaving syncthingtray broken until it has been rebuilt) or to uninstall syncthingtray temporarily before the update. After the update syncthingtray can be rebuilt and reinstalled again.
    • The correct solution is to use makechrootpkg which is also how official developers build their packages (and how packages in my binary repository are built).
  • It is required to build dependencies (that are not provided by Arch Linux itself) before building this package. So you need to build c++utilities, qtutilities, qtforkawesome and syncthingtray in that order.
  • The KDE integrations have been ported to KDE 6 but building them for KDE 5 should still work. This package does not build any KDE integrations by default because KDE 6 is now in the main repositories. To build KDE integrations for KDE 6 you need to install syncthingtray-qt6 instead of this package.
  • Note that the tests of this package might fail despite there's nothing wrong (e. g. because Syncthing is just too slow and the test runs in a timeout). To ignore those false-positives, build the package with makepkg --nocheck or makechrootpkg -- --nocheck. It makes still sense to report failures. But please include the actual error message and not just the last few lines.

Latest Comments

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

Martchus commented on 2025-10-10 08:21 (UTC)

@Sabu

Perhaps that is the problem, too little free memory space in percentage terms. Why x% and not xx GB/MB?

Yes, probably. I don't remember configuring this explicitly when creating the config for the test instance. I think those are simply the defaults from Syncthing itself.

Sabu commented on 2025-10-10 02:10 (UTC)

I saw the error and checked the disk space. During that time there where 5 GB left out of nearly 916 GB which is around 0.5%. Perhaps that is the problem, too little free memory space in percentage terms. Why x% and not xx GB/MB?

Martchus commented on 2025-10-09 23:16 (UTC)

@Sabu Ok, I double-checked and the logs actually tell us what the problem is: 

2025-10-08 02:48:49 WRN Folder is in error state (folder=test1 error="insufficient space on disk for database (~/.cache/paru/clone/syncthingtray-qt6/src/syncthingtray-2.0.2/cli/testworkingdir/testconfig/index-v2): current 0.56 % < required 1 %" log.pkg=model)

So just make sure you have enough disk space under the location mentioned by this log message.

Martchus commented on 2025-10-09 23:08 (UTC)

@Sabu It looks like the Syncthing test instance started by the integration tests has an unexpected out of sync directory in your case. I'm not sure why this happens in your environment and why it is only happening when building the Qt 6 based version. It probably doesn't mean that your build of Syncthing Tray is broken so I suggest you just move on without passing tests as mentioned in the pinned comment.

Martchus commented on 2025-10-09 08:10 (UTC) (edited on 2025-10-09 08:15 (UTC) by Martchus)

@Sabu Ok, I'll look into those failures when I have the time. And yes, the tests are very noisy. That's probably something I should improve at some point.

Sabu commented on 2025-10-09 00:39 (UTC) (edited on 2025-10-09 00:49 (UTC) by Sabu)

The full log file (LastTest.log) consist nearly 1200 rules, available @pastebin: https://pastebin.com/vHmSaXCJ NB: ESC-sequences are not properly shown (don't know how to handle this), in rule 75 and 210 there's only a lonely F shown.

Martchus commented on 2025-10-08 21:56 (UTC)

@Sabu Without full logs the failure is impossible to investigate.

Sabu commented on 2025-10-08 00:59 (UTC) (edited on 2025-10-08 01:01 (UTC) by Sabu)

I've tried to install syncthingtray-qt6 but it fails due to 2 errors while testing it after build. The following tests FAILED: 1 - syncthingconnector-qt6_run_tests (Failed) / 2 - syncthingctl-qt6_run_tests (Failed).

Martchus commented on 2025-10-07 15:00 (UTC)

AT THIS POINT YOU ALMOST CERTAINLY WANT TO USE https://aur.archlinux.org/packages/syncthingtray-qt6 INSTEAD.

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