Package Details: syncthingtray-qt6 1.7.2-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: 28
Popularity: 3.82
First Submitted: 2020-11-07 16:16 (UTC)
Last Updated: 2025-02-04 21:14 (UTC)

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 .. 8 Next › Last »

Martchus commented on 2025-02-06 21:43 (UTC)

If it is caused by how KDE handles adjacent Plasmoids then there is indeed nothing I can do about it. However, I think this shouldn't be a problem when showing the Plasmoid as part of the system tray Plasmoid. The README contains more information about the different ways the Plasmoid can be configured, see https://github.com/Martchus/syncthingtray?tab=readme-ov-file#configuring-plasmoid.

derivativeoflog7 commented on 2025-02-06 21:41 (UTC)

@matchus I mean, it could be caused by how KDE handles adjacent plasmoids, or by how I have my panel configured for all I know

Martchus commented on 2025-02-06 21:39 (UTC)

Feel free to open an issue on GitHub with a screnshot showing the problematic part of the Plasmoid UI, e.g. highlighting it somehow. Maybe this can be fixed easily. (Although I must say that layouting/alignment can be a bit problematic in Qt Quick so it is really only maybe easy to fix.)

derivativeoflog7 commented on 2025-02-06 21:35 (UTC)

@Martchus i see; I could use the plasmoid but I'm really picky about the mismatching padding in the tray bar lol
Now I've tried to set it to autostart through the KDE autostart settings instead, let's see if that works, if not I'll try other solutions

Martchus commented on 2025-02-06 21:31 (UTC)

I don't have that issue although I am using KDE and thus the Plasmoid and thus don't use the autostart of the standalone tray application. (I only use the autostart feature of the standalone tray application under Windows but there it is implemented differently so that's not comparable.)

Syncthing Tray is really not supposed to delete its own autostart entry again unless you explicitly uncheck the checkbox under the autostart settings. The only thing that comes to my mind is that the deletion is happening while the testsuite is executed when building this package (e.g. when updating). The tests are of course not supposed to influence your normal configuration but there might be a shortcoming in the test setup leading to this problem.

I suppose a simple workaround would be to set the ownership of that .desktop file so that it cannot be deleted.

derivativeoflog7 commented on 2025-02-06 15:51 (UTC)

Every once in a while the autostart entry in ~/.config/autostart misteriously disappears; I enable the option from the program and it works for a while, but then it stops working seemingly randomly.
I have other .desktop files in that folder and those don't randomly disappear.
I'm running KDE Plasma Has anyone else been having this issue?

costor commented on 2025-01-12 23:58 (UTC)

@iyanmv @Martchus syncthingtray-git builds and work fine for me! I indeed had [kde-unstable] enabled, but I had forgotten that it was enabled...

iyanmv commented on 2025-01-12 22:30 (UTC)

Martchus: syncthingtray-git builds just fine also with Qt 6.9.0. Thanks!

Martchus commented on 2025-01-11 00:54 (UTC)

I pushed https://github.com/Martchus/syncthingtray/commit/db32c94c7212f7f890307d7cb045035040ff418d on GitHub. With that compilation against Qt 6 works for me. I haven't tested compilation against the latest KDE frameworks yet. You can test it using the syncthingtray-git package.

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