You need to install syncthingtray-qt6 (and may uninstall syncthingtray) as I mentioned in my last summary about recent changes in this forum thread. Checkout the remarks in the pinned comments on the AUR for further details.
And yes, this is about the Plasmoid vs. the stand-alone version. Checkout the according README section for details.
That’s fortunately not how it works. When uninstalling a package of a GUI application like Syncthing Tray the configuration is not lost. So when installing the package again you won’t have to reconfigure anything. This also counts for switching from syncthingtray to syncthingtray-qt6 except that you’ll have to remove the “old” Plasmoid and add the new Plasmoid because for Plasma these are distinct Plasmoids. Removing/re-adding the Plasmoid does not reset the overall configuration so this is not a big deal. Again, checkout the README for details.
Hmm, what am i doing wrong? why cant i reach/resolve
:: (27/40) Failed to download PKGBUILD: kcmutils-git
:: (27/40) Failed to download PKGBUILD: upower-git
:: (27/40) Failed to download PKGBUILD: qtforkawesome-qt6
:: (27/40) Failed to download PKGBUILD: kirigami-git
-> error fetching kauth-git: Cloning into 'kauth-git'...
fatal: unable to access 'https://aur.archlinux.org/kauth-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching knotifications-git: Cloning into 'knotifications-git'...
fatal: unable to access 'https://aur.archlinux.org/knotifications-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching kiconthemes-git: Cloning into 'kiconthemes-git'...
fatal: unable to access 'https://aur.archlinux.org/kiconthemes-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching kdoctools-git: Cloning into 'kdoctools-git'...
fatal: unable to access 'https://aur.archlinux.org/kdoctools-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching kguiaddons-git: Cloning into 'kguiaddons-git'...
fatal: unable to access 'https://aur.archlinux.org/kguiaddons-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching kdbusaddons-git: Cloning into 'kdbusaddons-git'...
fatal: unable to access 'https://aur.archlinux.org/kdbusaddons-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching kcrash-git: Cloning into 'kcrash-git'...
fatal: unable to access 'https://aur.archlinux.org/kcrash-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching karchive-git: Cloning into 'karchive-git'...
fatal: unable to access 'https://aur.archlinux.org/karchive-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching kwidgetsaddons-git: Cloning into 'kwidgetsaddons-git'...
fatal: unable to access 'https://aur.archlinux.org/kwidgetsaddons-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching kcmutils-git: Cloning into 'kcmutils-git'...
fatal: unable to access 'https://aur.archlinux.org/kcmutils-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching upower-git: Cloning into 'upower-git'...
fatal: unable to access 'https://aur.archlinux.org/upower-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching qtforkawesome-qt6: Cloning into 'qtforkawesome-qt6'...
fatal: unable to access 'https://aur.archlinux.org/qtforkawesome-qt6.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
error fetching kirigami-git: Cloning into 'kirigami-git'...
fatal: unable to access 'https://aur.archlinux.org/kirigami-git.git/': Could not resolve host: aur.archlinux.org
context: exit status 128
I do use adguard on my server for DNS, maybe something to do with that ? I would doubt it though.
k…-git packages are not expected to be required. Could it be that Manjaro is not yet providing KDE 6 packages (so you’re still using Plasma 5)? Note that Manjaro is not supported by the AUR and using it nevertheless is asking for trouble as packages in Manjaro might be too old. I suppose in this case you can mitigate the problem by staying with syncthingtray as long as Manjaro is still only providing KDE 5. To still build KDE integrations as part of syncthingtray you need to add the following to /etc/makepkg.conf:
Thx, it started working (resolving) about an hour later but i can not install syncthingtray-qt6 , i have tried and tried but i just get a lof of dependency errors and then after about half an hour of shell text going by it just fails.
I can show the last part as a screen shot (sorry but it was such a long installation attempt each time (and i tried many times) that i just used screen shots)
I understood, i shall leave it for tonight though. Its been a long day trying to figure this thing alone. I shall start again in the morning with your settings in the makepkg.
It is a while ago since my last update, so here a few developments:
The previously mentioned Windows 11 style can now be selected in the latest release.
I setup a website. It doesn’t contain much information on its own. The main reason for creating it is the downloads section which will make it hopefully much easier to find the most relevant download for one’s platform.
A Flatpak has been created (by qgymib). It doesn’t contain the KDE integrations, though (because that’s not possible).
I’m currently working on a way to ease managing ignore patterns. For this I have already created a file browser that shows the directory tree from the Syncthing database plus what is actually present on the local system. I hope I’ll be able to make it easy to add/remove paths to ignore/unignore via this UI. You can access/test the WIP file browser by setting the environment variable SYNCTHINGTRAY_ENABLE_WIP_FEATURES=1.
I released a new version today (1.6.0) and it contains many changes under the hood to reduce CPU usage.
The previously mentioned feature about ignore patterns is also no longer hidden behind a feature-flag. It still needs improvements in several areas but what is there should generally work (even though the UI is quite clunky at this point).
There were also changes regarding the Windows builds recently: They use mingw-w64 12 as of 1.6.0 and with that also the Universal CRT instead of the legacy one. I think this is only problematic if you use a system older than Windows 10 where you might need to install it. The builds are also conducted using the latest GCC. This also means that Qt 6 now finally doesn’t build for 32-bit Windows anymore so I dropped those builds as of version 1.5.3. (There are still 32-bit Windows builds of the version using Qt 5.)
That are all-in-all quite a few changes so let me know if something broke now (by filing an issue on GitHub).
The only limitation I am aware of so far is that I couldn’t compile/use Boost.Process (because its dependency Boost.Context is not supported on aarch64-w64-mingw32 yet). That means stopping Syncthing via the launcher forcefully might not cleanly terminate all processes. (Stopping Syncthing when the built-in Syncthing library is used is not affected and will work properly.)
