If you're referring to using Xorg, then that's a non-starter. Xorg is dead and rotting.
And Wayland still has many limitations and you've just hit one of those. Of course you're also right about Xorg. That unfortunately puts the GNU/Linux desktop at a bad place right now but this is probably out of scope here. (When I asked Plasma developers to provide necessary APIs under Wayland to fix the issues with the stand-alone version of Syncthing Tray they declined. The Plasmoid is the way to go.)
Pinned Comments
Martchus commented on 2023-11-21 23:20 (UTC) (edited on 2024-03-06 16:45 (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
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 usesyncthingtray
instead for the time being.Important remarks:
pkgrel
of the AUR package when a rebuild is required (only in accordance with Arch Linux of course, not in accordance with Manjaro).syncthingtray-qt6
broken until it has been rebuilt) or to uninstallsyncthingtray-qt6
temporarily before the update. After the updatesyncthingtray-qt6
can be rebuilt and reinstalled again.makechrootpkg
which is also how official developers build their packages (and how packages in my binary repository are built).c++utilities
,qtutilities-qt6
,qtforkawesome-qt6
andsyncthingtray-qt6
in that order.makepkg --nocheck
ormakechrootpkg -- --nocheck
. It makes still sense to report failures. But please include the actual error message and not just the last few lines.