Arch Linux User Repository

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
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.
Note that the syncthingtray-qt6 package in my binary repository is even built against Arch Linux's kde-unstable repository in order to include KDE integrations as well. That means you'll need that repository as well - even for the desktop-neutral parts (at least when kde-unstable has a newer version of Qt).** You can still build this package yourself against the normal repositories (without KDE integrations) or use syncthingtray instead for the time being.

Important remarks:

• 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 usually also 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.

I'm having a similar issue as iyanmv on Plasma 6 Wayland session. When clicking on the icon in the system tray, the menu window opens in the center of the screen, not attached to the panel below the system tray. That means no other application can be open on that screen in order to interact with it. This may be caused by shifting focus as I have "focus follows mouse" enabled.

I was using the Qt widgets version but I guess what I wanted was the plasmoid. I changed _enable_plasmoid=${SYNCTHING_TRAY_ENABLE_PLASMOID:-0} to _enable_plasmoid=${SYNCTHING_TRAY_ENABLE_PLASMOID:-1} in the PKGBUILD and enable it directly on the system tray. I have no intention to use X11, been happily using Wayland since Plasma 5.24 :)

Thanks for the help!

You haven't clarified whether you use the Qt widgets based version or the Plasmoid. I assume you use the former. Then positioning doesn't work under Wayland what you have probably switched to (because Wayland does not offer an API, I cannot fix this from my side). I suggest you keep using X11 (still supported by Plasma 6) or you use the Plasmoid instead (see the previously linked documentation for details).

Sorry, perhaps I was not clear. The looking of the app is good (colors and all that follow Breeze Dark theme). What I meant is that on Plasma 5.x when I click on the try icon I get a panel directly on top of the icon exactly the same as clicking on the volume or network icons, for example. But in Plasma 6 RC 2 I get a centered pop up window in the middle of the screen.

Martchus: Yes, I'm running Plasma 6 RC 2 from [kde-unstable]

Are you using the Qt Widgets based version or the Plasmoid?

The Qt Widgets based version (provided by this package using Qt 6) will only look like its Qt 5 based equivalent when the same Qt Widgets style is installed and configured. The Breeze style is only available for Qt 5 so far - unless you install the RC version from the kde-unstable repo.

If you are using the Plasmoid then the appearance of the Syncthing Tray Plasmoid will always look in-line with the Plasma shell but of course you need Plasma from the kde-unstable repo to be able to use the Plasmoid contained by this package.

If you're not sure whether you use the Qt Widgets based version or the Plasmoid then read https://github.com/Martchus/syncthingtray?tab=readme-ov-file#configuring-plasmoid.

Hey Martchus: Thanks for providing already this for Plasma 6! I wonder if it's possible to have a similar style/behaviour as with Plasma 5.x/Qt5. I tried changing the settings, but I can't make it look as a system tray panel as I was doing with syncthingtray with Qt5. Is this what you mean by "KDE integrations for KDE 6" in your pinned comment?

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
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.
Note that the syncthingtray-qt6 package in my binary repository is even built against Arch Linux's kde-unstable repository in order to include KDE integrations as well. That means you'll need that repository as well - even for the desktop-neutral parts (at least when kde-unstable has a newer version of Qt).** You can still build this package yourself against the normal repositories (without KDE integrations) or use syncthingtray instead for the time being.

Important remarks:

• 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 usually also 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.

By the way, the current soname of the dav1d library is libdav1d.so.7. That means at least your dav1d version is behind which is not good because partial updates are generally not supported.

Looks like your ffmpeg/dav1d builds are not compatible. That is not related to syncthingtray itself.