Package Details: syncthingtray-qt6 2.0.10-1

Git Clone URL: https://aur.archlinux.org/syncthingtray-qt6.git (read-only, click to copy)
Package Base: syncthingtray-qt6
Description: Tray application for Syncthing (using Qt 6)
Upstream URL: https://github.com/Martchus/syncthingtray
Licenses: GPL-2.0-or-later
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 48
Popularity: 3.11
First Submitted: 2020-11-07 16:16 (UTC)
Last Updated: 2026-04-09 10:38 (UTC)

Dependencies (28)

Required by (0)

Sources (2)

Pinned Comments

Martchus commented on 2023-11-21 23:20 (UTC) (edited on 2024-10-21 15:10 (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:

  • 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-qt6 broken until it has been rebuilt) or to uninstall syncthingtray-qt6 temporarily before the update. After the update syncthingtray-qt6 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-qt6, qtforkawesome-qt6 and syncthingtray-qt6 in that order.
  • The KDE integrations have been ported to KDE 6. This package builds KDE integrations for KDE 6 by default as KDE 6 is now in the main repositories.
  • 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 .. 11 Next › Last »

Martchus commented on 2026-03-23 14:21 (UTC) (edited on 2026-03-23 14:23 (UTC) by Martchus)

Is there a way to build this without building gcc-snapshot?

Sure, this package does not depend on gcc-snapshot so it won't pull-in this dependency by default. Also none of its dependencies will pull it in. If you used some helper there is probably something wrong with that as you should not have ended up building gcc-snapshot by accident.

I have tried looking around as to what pulls it in as a dependency, but I could not find it in the end, I am not experienced enough.

You couldn't find it because there is nothing to find.

And of course that takes hours on a 13900HX.

Really? That CPU sounds like it is actually quite fast. Maybe you should set MAKEFLAGS so that all of your CPU cores are used. I mean not for gcc-snapshot which you don't need anyway but to build packages faster in general.

I would like to build this instead of using the binary as I tend to keep my install fixed to a certain date in pacman, and update when I have the time for that while still being able to install packages consistently. Using the binary would not be possible that way.

If you are using repos from https://archive.archlinux.org then you indeed cannot install packages from my repo at any time. However, considering you probably just need to install a small set of packages from my repo it is probably not going to be a big deal to do this at the same time when you update everything. You could comment my repo in and out as needed to avoid installing packages from it accidentally.

szebenyib commented on 2026-03-23 07:51 (UTC)

Is there a way to build this without building gcc-snapshot?

I have tried looking around as to what pulls it in as a dependency, but I could not find it in the end, I am not experienced enough. And of course that takes hours on a 13900HX.

I would like to build this instead of using the binary as I tend to keep my install fixed to a certain date in pacman, and update when I have the time for that while still being able to install packages consistently. Using the binary would not be possible that way.

Martchus commented on 2026-03-11 11:13 (UTC)

As stated in the pinned comment, I sometimes update the pkgrel. I do that mainly if a patch or other packaging change is required, though. Otherwise it isn't all that helpful and even causes more annoyances for certain users.

The problem is that users of kde-unstable need to rebuild earlier than users of testing which in turn need to rebuild earlier than users of regular repositories. Users of e.g. Manjaro probably need to rebuild even later. So it makes most sense if users handle rebuilds of AUR packages on their own.

I also want to avoid making things worse for people using these unstable/testing repositories who have already rebuilt sooner because that discourages use of these repositories - but this kind of testing is very important and shouldn't be discouraged.

physkets commented on 2026-03-11 10:19 (UTC)

If it needs a rebuild, could you initiate it by upping the pkgrel?

Martchus commented on 2026-03-11 09:56 (UTC)

@Martchus Is there an issue on the KDE bugtracker for this problem?

I don't know. You'll probably find something if you search for it :-)

However, I can tell you that they've already acknowledged the ABI break by bumping the sover of libplasma and I don't think there's anything else to expect.

Note that if the package still doesn't work be sure you have rebuilt it against the latest libplasma. And if it then still doesn't work there's another unrelated problem.

physkets commented on 2026-03-11 06:56 (UTC)

@Martchus Is there an issue on the KDE bugtracker for this problem?

Martchus commented on 2026-01-16 22:19 (UTC)

The Plasmoid fails to load under KDE Plasma 6.5.90 with:

kf.coreaddons: "Could not load plugin from /usr/lib/qt6/plugins/plasma/applets/martchus.syncthingplasmoid-git.so: Die Bibliothek /usr/lib/qt6/plugins/plasma/applets/martchus.syncthingplasmoid-git.so kann nicht geladen werden: /usr/lib/qt6/plugins/plasma/applets/martchus.syncthingplasmoid-git.so: undefined symbol: _ZNK6Plasma5Theme5colorENS0_9ColorRoleENS0_10ColorGroupE"

This is not a problem with this package but rather Plasma breaking its ABI and API with the libplasma change f56f5eb4aea5f0604636ee5afa791d7672290612. I provide a rebuilt package of syncthingtray-git in my ownstuff-experimental repo to fix this.

yaros commented on 2025-10-23 03:02 (UTC)

@saymonz I'm sorry, I totally misunderstood you. I thought you tried to build it yourself without cleaning. I'm happy it's working for everyone now :)

saymonz commented on 2025-10-22 02:24 (UTC)

@yaros yeah it worked for me too, that's why I thanked @flying-sheep, sorry if that was unclear. That was indeed a me issue.

yaros commented on 2025-10-22 02:21 (UTC)

@saymonz I just did it and it worked, just like @flying-sheep but with yay. --rebuild flag is important. If you are using makepkg you need to make sure you set -C flag to do a full clean build.

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