Package Details: syncthingtray 1.2.1-1

Git Clone URL: https://aur.archlinux.org/syncthingtray.git (read-only, click to copy)
Package Base: syncthingtray
Description: Tray application for Syncthing
Upstream URL: https://github.com/Martchus/syncthingtray
Licenses: GPL
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 58
Popularity: 3.92
First Submitted: 2016-09-14 20:13 (UTC)
Last Updated: 2022-07-05 21:06 (UTC)

Pinned Comments

Martchus commented on 2016-10-31 11:39 (UTC) (edited on 2022-01-11 11:30 (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.

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).

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

Martchus commented on 2022-07-06 10:52 (UTC)

You need to rebuild c++utilities first.

You're not the first user to run into this problem. I'm really wondering why you would assume it makes sense to (re)build syncthingtray before its dependency c++utilities. If you're using an AUR helper you should likely move to using a better one or report a bug. However, I suggest to simply run makepkg/makechrootpkg manually and read various Wiki pages to understand how package building works. If you're lazy, I also provide a binary repository (see pinned comment).

mattalxndr commented on 2022-07-06 05:19 (UTC) (edited on 2022-07-06 05:19 (UTC) by mattalxndr)

I'm getting an error upgrading:

syncthingtray % makepkg --syncdeps
==> Making package: syncthingtray 1.2.1-1 (Wed 06 Jul 2022 12:17:44 AM CDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading syncthingtray-1.2.1.tar.gz...
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 1763k  100 1763k    0     0  2347k      0 --:--:-- --:--:-- --:--:-- 9301k
==> Validating source files with sha256sums...
syncthingtray-1.2.1.tar.gz ... Passed
==> Extracting sources...
-> Extracting syncthingtray-1.2.1.tar.gz with bsdtar
==> Starting build()...
-- The C compiler identification is GNU 12.1.0
-- The CXX compiler identification is GNU 12.1.0

[...]

-- Building with Qt Widgets GUI.
-- Building WITHOUT Qt Quick GUI.
-- Using Qt WebEngine as web view provider.
-- Using template for webviewdefs.h from QT_UTILITIES installation.
-- Using template for webviewincludes.h from QT_UTILITIES installation.
-- Linking syncthingwidgets against Qt module Qt5::Network.
-- Linking syncthingwidgets against Qt module Qt5::Concurrent.
-- Linking syncthingwidgets against Qt module Qt5::Gui.
-- Linking syncthingwidgets against Qt module Qt5::Widgets.
-- Linking syncthingwidgets against Qt module Qt5::WebEngineWidgets.
-- Linking syncthingwidgets against Qt module Qt5::Core.
-- Qt variable QT_INSTALL_TRANSLATIONS queried from qmake: /usr/share/qt/translations
-- Qt variable QT_INSTALL_TRANSLATIONS resolved to path: /usr/share/qt/translations
-- Project has translations which will be released.
-- Using template for qtconfig.h from QT_UTILITIES installation.
-- Using template for global.h from CPP_UTILITIES installation.
-- Using template for version.h from CPP_UTILITIES installation.
-- Using template for Config.cmake from CPP_UTILITIES installation.
-- Using template for template.pc from CPP_UTILITIES installation.
-- Using template for doxygen from CPP_UTILITIES installation.
-- Generating target for generating API documentation for syncthingwidgets with Doxygen
-- Using template for config.h from CPP_UTILITIES installation.
CMake Error at tray/CMakeLists.txt:96 (find_package):
Could not find a configuration file for package "c++utilities" that is
compatible with requested version "5.17.0".

The following configuration files were considered but not accepted:

/usr/share/c++utilities/cmake/c++utilitiesConfig.cmake, version: 5.16.0



-- Configuring incomplete, errors occurred!
See also "/home/matt/.cache/yay/syncthingtray/src/syncthingtray-1.2.1/CMakeFiles/CMakeOutput.log".
==> ERROR: A failure occurred in build().
Aborting...

SanskritFritz commented on 2022-06-04 10:49 (UTC)

@mattalxndr Remove syncthingtray from your autostart, or disable the plasmoid from the list of entries in the tray settings.

mattalxndr commented on 2022-06-04 09:57 (UTC)

For some reason, whenever I install this, I get both the plasmoid and the syncthingtray icons in the tray. How do I avoid having two icons in the tray that do virtually the same thing (other than hiding one of them in the overflow menu).

Martchus commented on 2022-05-26 10:03 (UTC)

@VyacheslavS Impossible to tell what's going wrong without logs. Checkout the pinned comment for how to ignore test failures. (Although it might be worthwhile looking into them.)

VyacheslavS commented on 2022-05-25 18:04 (UTC) (edited on 2022-05-25 18:10 (UTC) by VyacheslavS)

-> error making: syncthingtray

2/2 Test #2: syncthingctl_run_tests ...........   Passed   32.52 sec
50% tests passed, 1 tests failed out of 2
Total Test time (real) =  59.02 sec
The following tests FAILED:
      1 - syncthingconnector_run_tests (Failed)
Errors while running CTest
Output from these tests are in: /home/svm/.cache/yay/syncthingtray/src/syncthingtray-1.1.20/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
FAILED: connector/CMakeFiles/check /home/svm/.cache/yay/syncthingtray/src/syncthingtray-1.1.20/connector/CMakeFiles/check 
cd /home/svm/.cache/yay/syncthingtray/src/syncthingtray-1.1.20 && /usr/bin/ctest -V
ninja: build stopped: subcommand failed.

Martchus commented on 2022-05-05 00:08 (UTC)

To who flagged the package: Please rebuild packages in the right order. Nothing is outdated here. Please refrain from flagging a package if you run into a problem.

reefland commented on 2022-01-11 17:16 (UTC)

@Martchus - I understand now, thank you. I uninstalled the "syncthingtray-git" repo and went back to "syncthingtray" and it worked fine. As you said, just luck that the act of rebuilding from repo switch fixes it, not the alt repo itself.

Martchus commented on 2022-01-11 16:34 (UTC)

When using my binary repo then Manjaro packages might be too old, indeed. Switching to the Git version doesn't help in this case at all, at least not using the version from my binary repo.

When building the package from sources one has to take care of rebuilding if a dependency changes its soname - regardless whether Manjaro or normal Arch is used. The only convenience Arch users have is that I usually bump pkgrel as needed (so e.g. their AUR helper does the rebuild as needed). Building packages from sources is also what my last comment was about.

Switching to the Git version likely helped in your case because that obviously means doing a new build so you've got the required rebuild. (But you could have just rebuilt the normal package as well.)

reefland commented on 2022-01-11 16:25 (UTC)

@Martchus - my understanding was that when using Manjaro, he has to wait until their packages catch up. If he wants it to work today, switch repos. My apologies if that is technically not accurate, but it worked as a solution for me, even if just luck.

Martchus commented on 2022-01-11 15:55 (UTC)

@reefland Whether using the Git or normal version makes not really a difference. You'll need to rebuild regardless which package you use. Of course rebuilding the package more frequently increases the chance of rebuilding it when it is required but that's just luck and I wouldn't sell it as solution.

reefland commented on 2022-01-11 15:33 (UTC)

@Oleg_Andreych - if using Manjaro switch to "syncthingtray-git" repo instead to resolve the message you see.

Martchus commented on 2022-01-11 11:29 (UTC)

@Oleg_Andreych Also read the pinned comment.

SanskritFritz commented on 2022-01-11 09:21 (UTC) (edited on 2022-01-11 09:22 (UTC) by SanskritFritz)

Oleg 1. don't run Manjaro :D but if you must, 2. rebuild the package after a system upgrade. And 3. read the pinned comment.

Oleg_Andreych commented on 2022-01-11 07:11 (UTC)

syncthingtray doesn't start with an error:

syncthingtray: error while loading shared libraries: libboost_filesystem.so.1.76.0: cannot open shared object file: No such file or directory

boost-libs package version is 1.78.0-1.

I'm running Manjaro.

Martchus commented on 2022-01-03 12:09 (UTC)

@Harvie It makes still sense to report test failures. But please include the actual error message and not just the last few lines.

Harvie commented on 2022-01-03 12:05 (UTC)

This worked for me to install it using yay: yay --mflags "--nocheck" -S syncthingtray

Martchus commented on 2021-10-06 09:16 (UTC)

Should be fixed.

Varakh commented on 2021-10-06 09:01 (UTC)

==> Validating source files with sha256sums... qtforkawesome-0.0.1.tar.gz ... FAILED

Same for me on Arch

adwl commented on 2021-10-06 08:57 (UTC) (edited on 2021-10-06 09:54 (UTC) by adwl)

edit: Working Now

==> Validating source files with sha256sums... qtforkawesome-0.0.1.tar.gz ... FAILED

on Majaro. Disregard if this is not an issue for Arch

Martchus commented on 2021-10-06 08:33 (UTC)

The dependency should be there now. Sorry for the inconvenience. It is new so my scripts for pushing automatically to the AUR were lacking it.

Maxnet commented on 2021-10-06 07:37 (UTC)

fails to build due to missing dependency qtforkawesome. Can you have a look at it?

ChillFre4k commented on 2021-10-06 06:16 (UTC)

Hi,

there is no package for "qtforkawesome" at the moment. @Martchus

Martchus commented on 2021-07-19 13:33 (UTC)

see https://github.com/Martchus/syncthingtray/issues/98

reefland commented on 2021-07-19 13:01 (UTC) (edited on 2021-07-19 13:02 (UTC) by reefland) 

$ syncthingctl status
syncthingctl: error while loading shared libraries: libboost_filesystem.so.1.75.0: cannot open shared object file: No such file or directory

$ pacman -Q boost-libs
boost-libs 1.76.0-1

$ pacman -Q syncthingtray 
syncthingtray 1.1.8-1

Martchus commented on 2021-07-17 13:37 (UTC) (edited on 2021-07-17 13:39 (UTC) by Martchus)

I assume you've just ran the local -a command in some shell in some terminal. You could add the command within the PKGBUILD's check() function and also echo the environment variables. This way you would see whether it is setup as expected also in the build environment. (An AUR helper or makepkg might mess-up something here, e.g. makepkg generally sets environment variables from /etc/makepkg.conf.)

at the beginning

I've noticed that setting variables at the beginning of the file might not be reliable, at least that's my experience when using makechrootpkg (see https://github.com/hipersayanX/ArchPackages/commit/1e61856d067b5aeae6828e39e01d617661b1069e). Hence I recommend to set environment variables within the relevant functions.

tdallagn commented on 2021-07-16 17:12 (UTC)

I'm not sure what's wrong with my locales, it seems alright:

$ locale -a
C
en_GB.utf8
en_US.utf8
POSIX

But adding export LC_ALL=C; unset LANGUAGE at the beginning of the PKGBUILD worked, thanks!

Martchus commented on 2021-07-10 10:35 (UTC)

Looks like the locale isn't setup correctly in your build environment. Does it help to put export LC_ALL=C; unset LANGUAGE into the check() function within the PKGBUILD (before the test suite is invoked)? If that's the case than the problem is likely due to an incorrect locale setup.

By the way, this is how one usually sets up the locale: https://wiki.archlinux.org/title/Locale#Generating_locales

tdallagn commented on 2021-07-10 10:25 (UTC) (edited on 2021-07-10 10:26 (UTC) by tdallagn)

Upgrading from 1.1.7-1 to 1.1.8-1 fails because the tests fail.
Full logs: https://0bin.net/paste/W-nQ1Ar0#OaFh1cPlBcy65ZQy7luStEtnNS3jY7EL9zCi+N6h-5A

2: !!!FAILURES!!!
2: Test Results:
2: Run:  1   Failures: 0   Errors: 1
2:
2:
2: 1) test: ApplicationTests::test (E)
2: setUp() failed
2: - uncaught exception of type std::exception (or derived).
2: - locale::facet::_S_create_c_locale name not valid
2:
2:
2: Tests failed
2/2 Test #2: syncthingctl_run_tests ...........***Failed    0.01 sec
0% tests passed, 2 tests failed out of 2
Total Test time (real) =   0.02 sec
The following tests FAILED:
1 - syncthingconnector_run_tests (Failed)
2 - syncthingctl_run_tests (Failed)
Errors while running CTest
Output from these tests are in: /tmp/bauh/arch/build_1625912474/syncthingtray/src/syncthingtray-1.1.8/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
FAILED: connector/CMakeFiles/check
cd /tmp/bauh/arch/build_1625912474/syncthingtray/src/syncthingtray-1.1.8 && /usr/bin/ctest -V
ninja: build stopped: subcommand failed.
==> ERROR: A failure occurred in check().
Aborting...
rm -rf /tmp/bauh/arch/build_1625912474

Package "syncthingtray" upgrade failed

bigolewannabe commented on 2021-04-07 18:47 (UTC)

If it helps, I noticed the same error trying to build this package. During the test run is the same error I got when I tried running plasmashell in a console. parsting and something about a - in a date throwing a c++utilities exception.

Martchus commented on 2021-04-07 14:48 (UTC)

Thanks for the stack trace, its very useful and I guess I've already found the issue. It is not within c++utilities, though. The problem is that a parsing error isn't handled correctly.

sez11a commented on 2021-04-07 14:45 (UTC)

Here's the stacktrace generated by my just-updated version of Arch. Looks like the problem is in C++ utilities:

Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]

4 0x00007f40a4415ef5 in raise () at /usr/lib/libc.so.6
5 0x00007f40a43ff862 in abort () at /usr/lib/libc.so.6
6 0x00007f40a463c86a in __gnu_cxx::__verbose_terminate_handler() () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
7 0x00007f40a4648d3a in __cxxabiv1::__terminate(void (*)()) (handler=<optimized out>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:48
8 0x00007f40a4648da7 in std::terminate() () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:58
9 0x00007f40a464904e in __cxxabiv1::__cxa_throw(void, std::type_info, void ()(void)) (obj=<optimized out>, tinfo=0x7f40880d72b8 <typeinfo for CppUtilities::ConversionException>, dest=0x7f40880bf120 <CppUtilities::ConversionException::~ConversionException()>) at /build/gcc/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95
10 0x00007f40880ae3f5 in () at /usr/lib/libc++utilities.so.5
11 0x00007f4088101fbc in Data::SyncthingConnection::readStatus() () at /usr/lib/libsyncthingconnector.so.1.1.3
12 0x00007f40a4a71d86 in () at /usr/lib/libQt5Core.so.5
13 0x00007f40a41f5965 in () at /usr/lib/libQt5Network.so.5
14 0x00007f40a4a67532 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
15 0x00007f40a56d9752 in QApplicationPrivate::notify_helper(QObject, QEvent) () at /usr/lib/libQt5Widgets.so.5
16 0x00007f40a4a3aa2a in QCoreApplication::notifyInternal2(QObject, QEvent) () at /usr/lib/libQt5Core.so.5
17 0x00007f40a4a3d523 in QCoreApplicationPrivate::sendPostedEvents(QObject, int, QThreadData) () at /usr/lib/libQt5Core.so.5
18 0x00007f40a4a94054 in () at /usr/lib/libQt5Core.so.5
19 0x00007f40a2e1af9c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
20 0x00007f40a2e6ea49 in () at /usr/lib/libglib-2.0.so.0
21 0x00007f40a2e186f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
22 0x00007f40a4a93691 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
23 0x00007f40a4a393ac in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
24 0x00007f40a4a41844 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
25 0x000055ab7b60720b in ()
26 0x00007f40a4400b25 in __libc_start_main () at /usr/lib/libc.so.6
27 0x000055ab7b60733e in ()

[Inferior 1 (process 1772) detached]

On my system, I was able to update everything but Syncthingtray itself; that fails to install due to an error with the tests:

2: !!!FAILURES!!! 2: Test Results: 2: Run: 1 Failures: 1 Errors: 0 2: 2: 2: 1) test: ApplicationTests::test (F) line: 130 cli/tests/application.cpp 2: forced failure 2: - app failed with return code 134 2: stdout: 2: stderr: Info: Connecting to http://localhost:59718 ...terminate called after throwing an instance of 'CppUtilities::ConversionException' 2: what(): unexpected "-" after day 2: 2: 2: 2: Tests failed 2/2 Test #2: syncthingctl_run_tests ...........***Failed 2.55 sec

0% tests passed, 2 tests failed out of 2

Total Test time (real) = 5.08 sec

The following tests FAILED: 1 - syncthingconnector_run_tests (Failed) 2 - syncthingctl_run_tests (Failed) Errors while running CTest Output from these tests are in: /home/sezovr/.cache/yay/syncthingtray/src/syncthingtray-1.1.4/Testing/Temporary/LastTest.log Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely. FAILED: connector/CMakeFiles/check cd /home/sezovr/.cache/yay/syncthingtray/src/syncthingtray-1.1.4 && /usr/bin/ctest -V ninja: build stopped: subcommand failed. ==> ERROR: A failure occurred in check(). Aborting... error making: syncthingtray

Martchus commented on 2021-04-07 11:07 (UTC) (edited on 2021-04-07 11:09 (UTC) by Martchus)

So I assume you're using the Plasmoid and plasmashell crashes. Without logs and stack trace it is hard to tell what's wrong.

That a single Plasmoid can crash the whole shell is likely nothing I can improve because that's a result of how Plasma's architecture is designed.

Note that if you're using Manjaro the package in my binary repository might be to new and hence break with the possibly older version of plasmashell in Manjaro.

About the test suite: https://forum.syncthing.net/t/yet-another-syncthing-tray/8502/121

shaybox commented on 2021-04-07 11:02 (UTC)

My god so this is the package that's broken my system all day, I thought it was latte-dock until I realized the systray widget was the culprit, but it's this.

jkhsjdhjs commented on 2020-10-24 01:32 (UTC)

@Martchus Ah ok, sorry. Didn't notice that qtutilities was an aur package. It works now, thanks!

Martchus commented on 2020-10-23 22:50 (UTC)

@jkhsjdhjs The AUR and my binary repository have the latest version of qtutilities. You need to build packages in the right order. (Generally, you need to build all dependencies of a package before building the package itself.)

jkhsjdhjs commented on 2020-10-23 21:38 (UTC)

I'm currently unable to build the latest version of syncthingtray, because it requires qtutilities 6.3.0, which is not in the repos yet. Let's hope the repo package gets updated soon.

CMake Error at connector/CMakeLists.txt:48 (find_package):
  Could not find a configuration file for package "qtutilities" that is
  compatible with requested version "6.3.0".

  The following configuration files were considered but not accepted:

    /usr/share/qtutilities/cmake/qtutilitiesConfig.cmake, version: 6.2.1



-- Configuring incomplete, errors occurred!
See also "/home/jkhsjdhjs/.cache/pikaur/build/syncthingtray/src/syncthingtray-1.0.0/CMakeFiles/CMakeOutput.log".

prettyvanilla commented on 2020-10-11 15:35 (UTC)

In the latest package updates you forgot to update the checksums for syncthingtray, qtutilities and c++utilities.

Martchus commented on 2020-07-07 22:05 (UTC)

@sez11a See comments on qtutilities and better add comments in the specific package which has the build errors.

sez11a commented on 2020-07-07 21:07 (UTC) (edited on 2020-07-07 21:08 (UTC) by sez11a)

I get an error compiling qtutilities: 

[ 91%] Building CXX object CMakeFiles/qtutilities.dir/qtutilities_autogen/3YJK5W5UP7/qrc_qtutilsicons.cpp.o
[ 94%] Linking CXX shared library libqtutilities.so
[100%] Built target qtutilities
==> Starting check()...
/home/me/.cache/yay/qtutilities/PKGBUILD: line 31: cd: /home/sezovr/.cache/yay/qtutilities/src/qtutilities: No such file or directory
==> ERROR: A failure occurred in check().
    Aborting...
Error making: qtutilities

gwpl commented on 2020-04-15 12:24 (UTC) (edited on 2020-04-15 12:25 (UTC) by gwpl)

syncthingtray_0.10.8 compilation error .

full log attached here : https://github.com/Martchus/syncthingtray/issues/63 .

$ pacaur -S syncthingtray
(...)
2: !!!FAILURES!!!
2: Test Results:
2: Run:  1   Failures: 1   Errors: 0
2: 
2: 
2: 1) test: ApplicationTests::test (F) line: 146 /home/gw/.cache/pacaur/syncthingtray/src/syncthingtray-0.10.8/cli/tests/application.cpp
2: forced failure
2: - Line    Status                        (idle|scanning) could not be found in output.
2: 
2: 
2: Tests failed
2/2 Test #2: syncthingctl_run_tests ...........***Failed    2.53 sec

0% tests passed, 2 tests failed out of 2

Total Test time (real) =   6.10 sec

The following tests FAILED:
          1 - syncthingconnector_run_tests (Failed)
          2 - syncthingctl_run_tests (Failed)
Errors while running CTest
make[3]: *** [connector/CMakeFiles/check.dir/build.make:77: connector/CMakeFiles/check] Error 8
make[2]: *** [CMakeFiles/Makefile2:632: connector/CMakeFiles/check.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:639: connector/CMakeFiles/check.dir/rule] Error 2
make: *** [Makefile:325: check] Error 2
==> ERROR: A failure occurred in check().
    Aborting...
:: failed to build syncthingtray package(s)

tydynrain commented on 2020-03-28 23:20 (UTC)

@Martchus, uninstalling ffmpeg-full and reinstalling ffmpeg, along with using --nocheck worked finally. Thank you.

Martchus commented on 2020-03-28 22:54 (UTC)

I also deleted my comment because it is not very useful without the errors.

So here again: I doubt this has anything to do with this package beside the fact that it is using qt5-webengine which pulls the ffmpeg package which pulls dav1d. It looks like your ffmpeg and dav1d versions aren't matching. Are you using a custom ffmpeg build and missed https://www.archlinux.org/todo/dav1d-060-soname-bump/ ?

tydynrain commented on 2020-03-28 22:51 (UTC)

@Marchus The post on the tageditor was an accident, which is why I deleted it. I think I followed a link from this page, which is why I accidentally posted it there.

Martchus commented on 2020-03-28 22:33 (UTC)

Looks like the exact same error as you've got with tageditor. See my comment there. It has likely nothing to do with any of these packages.

tydynrain commented on 2020-03-28 22:30 (UTC)

I got this error during the build phase today:

/usr/bin/ld: warning: libdav1d.so.3, needed by /usr/lib/libavcodec.so.58, not found (try using -rpath or -rpath-link)

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_get_picture'

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_version'

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_data_unref'

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_open'

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_data_wrap'

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_send_data'

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_flush'

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_picture_unref'

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_close'

/usr/bin/ld: /usr/lib/libavcodec.so.58: undefined reference to `dav1d_default_settings'

collect2: error: ld returned 1 exit status

make[2]: *** [tray/CMakeFiles/syncthingtray.dir/build.make:428: tray/syncthingtray] Error 1

make[2]: Leaving directory '/home/tydynrain/.cache/aurutils/sync/syncthingtray/src/syncthingtray-0.10.7'

make[1]: *** [CMakeFiles/Makefile2:1549: tray/CMakeFiles/syncthingtray.dir/all]

Error 2

make[1]: Leaving directory '/home/tydynrain/.cache/aurutils/sync/syncthingtray/src/syncthingtray-0.10.7'

make: *** [Makefile:158: all] Error 2

==> ERROR: A failure occurred in build().

Aborting...

Martchus commented on 2020-02-05 11:25 (UTC)

see https://aur.archlinux.org/packages/tageditor/#comment-727871

vanjiii commented on 2020-02-05 11:07 (UTC)

Hey, validity check fails during update:

==> Validating source files with sha256sums...
    syncthingtray-0.10.6.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: syncthingtray

Martchus commented on 2019-10-06 12:45 (UTC)

I can not reproduce it myself so I guess I'll better just make the package skip the tests by default.

tydynrain commented on 2019-10-06 06:26 (UTC) (edited on 2019-10-06 06:38 (UTC) by tydynrain)

I get the same error and failure during build for version 0.10.1 (the --nocheck flag worked):

2: !!!FAILURES!!!

2: Test Results:

2: Run: 1 Failures: 1 Errors: 0

2:

2:

2: 1) test: ApplicationTests::test (F) line: 146 /home/tydynrain/.cache/yay/syncthingtray/src/syncthingtray-0.10.1/cli/tests/application.cpp

2: forced failure

2: - Line - .* could not be found in output.

2:

2:

2: Tests failed

2/2 Test #2: syncthingctl_run_tests ...........***Failed 6.84 sec

50% tests passed, 1 tests failed out of 2

Total Test time (real) = 21.18 sec

The following tests FAILED:

  2 - syncthingctl_run_tests (Failed)

Errors while running CTest

make[3]: *** [connector/CMakeFiles/check.dir/build.make:57: connector/CMakeFiles/check] Error 8

make[2]: *** [CMakeFiles/Makefile2:416: connector/CMakeFiles/check.dir/all] Error 2

make[1]: *** [CMakeFiles/Makefile2:423: connector/CMakeFiles/check.dir/rule] Error 2

make: *** [Makefile:305: check] Error 2

==> ERROR: A failure occurred in check().

Aborting...

Error making: syncthingtray

victorbrca commented on 2018-06-11 16:49 (UTC) (edited on 2018-06-11 16:49 (UTC) by victorbrca)

@Martchus the --nocheck did it for me. And sorry for not posting the full error. This is what I was getting... but I still don't see anything specific other than the second check failing due to a timeout. 

test 2
    Start 2: syncthingctl_run_tests

2: Test command: /tmp/syncthingtray/src/syncthingtray-0.8.1/cli/syncthingctl_tests "-p" "/tmp/syncthingtray/src/syncthingtray-0.8.1/cli/testfiles" "-w" "/tmp/syncthingtray/src/syncthingtray-0.8.1/cli/testworkingdir" "-a" "/tmp/syncthingtray/src/syncthingtray-0.8.1/cli/syncthingctl"
2: Test timeout computed to be: 10000000
2: Directories used to search for testfiles:
2: /tmp/syncthingtray/src/syncthingtray-0.8.1/cli/testfiles/
2: ./testfiles/
2: 
2: Directory used to store working copies:
2: /tmp/syncthingtray/src/syncthingtray-0.8.1/cli/testworkingdir/
2: 
2: Executing test cases ...
2: .
2:  - Setup configuration for Syncthing tests ...
2: 
2:  - Launching Syncthing ...
2: 
2: Waiting till Syncthing GUI becomes available ...- syncthingctl status --api-key syncthingtestinstance --url http://localhost:59251
2: Directories
2:  - test2
2:    Label                         Test dir 2
2:    Path                          /tmp/some/path/2/
2:    Status                        paused
2:       Global                        0 file(s), 0 dir(s), 0 bytes
2:       Local                         0 file(s), 0 dir(s), 0 bytes
2:    Shared with                   Test dev 2
2:    Type                          Send & Receive
2:    Ignore permissions            no
2:    Auto-normalize                yes
2:    Rescan interval               365 d
2: 
2:  - test1
2:    Path                          /tmp/some/path/1/
2:    Status                        idle
2:       Global                        0 file(s), 0 dir(s), 0 bytes
2:       Local                         0 file(s), 0 dir(s), 0 bytes
2:    Last scan time                2018-06-11 09:16:42
2:    Shared with                   Test dev 2
2:                                  Test dev 1
2:    Type                          Send & Receive
2:    Ignore permissions            no
2:    Auto-normalize                yes
2:    Rescan interval               2 h
2: 
2: Devices
2:  - Desktop-Arch
2:    ID                            [removed]
2:    Status                        own device
2:    Addresses                     dynamic
2:    Compression                   metadata
2: 
2:  - Test dev 1
2:    ID                            [removed]
2:    Status                        disconnected
2:    Addresses                     dynamic
2:    Compression                   metadata
2: 
2:  - Test dev 2
2:    ID                            [removed]
2:    Status                        paused
2:    Addresses                     tcp://192.168.2.2:22000
2:    Compression                   metadata
2: 
2: expected status: Directories
2:  - test2
2:    Label                         Test dir 2
2:    Path                          /tmp/some/path/2/
2:    Status                        paused
2:       Global                        0 file\(s\), 0 dir\(s\), 0 bytes
2:       Local                         0 file\(s\), 0 dir\(s\), 0 bytes
2:    Shared with                   Test dev 2
2:    Type                          Send & Receive
2:    Ignore permissions            no
2:    Auto-normalize                yes
2:    Rescan interval               365 d
2: 
2:  - test1
2:    Path                          /tmp/some/path/1/
2:    Status                        (idle|scanning)
2:       Global                        0 file\(s\), 0 dir\(s\), 0 bytes
2:       Local                         0 file\(s\), 0 dir\(s\), 0 bytes
2:    Last scan time                \d\d\d\d-\d\d-\d\d \d\d:\d\d:\d\d.*
2:    Shared with                   Test dev 2
2:                                  Test dev 1
2:    Type                          Send & Receive
2:    Ignore permissions            no
2:    Auto-normalize                yes
2:    Rescan interval               2 h
2: 
2: Devices
2:  - Test dev 1
2:    ID                            [removed]
2:    Status                        disconnected
2:    Addresses                     dynamic
2:    Compression                   metadata
2: 
2:  - Test dev 2
2:    ID                            [removed]
2:    Status                        paused
2:    Addresses                     tcp://.*22000
2:    Compression                   metadata
2: 
2:  - .*
2:    ID                            \w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w
2:    Status                        own device
2:    Addresses                     dynamic
2:    Compression                   metadata
2: 
2: F
2:  - Waiting for Syncthing to terminate ...
2: 
2:  - Syncthing terminated with exit code 0.
2: 
2:  - Syncthing stdout during the testrun:
2: [monitor] 09:16:42 INFO: Signal 15 received; exiting
2: 
2: 
2: 
2: !!!FAILURES!!!
2: Test Results:
2: Run:  1   Failures: 1   Errors: 0
2: 
2: 
2: 1) test: ApplicationTests::test (F) line: 120 /tmp/syncthingtray/src/syncthingtray-0.8.1/cli/tests/application.cpp
2: forced failure
2: - Actual status does not match expected status.
2: 
2: 
2/2 Test #2: syncthingctl_run_tests ...........***Failed    2.26 sec

Martchus commented on 2018-06-06 18:26 (UTC)

@victorbrca I can look into it tomorrow. As a workaround, you can of course build it without running the tests (makepkg --nocheck).

The text you've pasted only says that the test for the command line interface didn't pass. What is the actual error message?

Did you change any of the variables at the beginning of the PKGBUILD?

victorbrca commented on 2018-06-06 18:16 (UTC) (edited on 2018-06-06 18:17 (UTC) by victorbrca)

I'm not sure if anyone else is having issues, but I'm not able to build it for quite a few days. 

The following tests FAILED:
      2 - syncthingctl_run_tests (Failed)
Errors while running CTest
make[3]: *** [connector/CMakeFiles/check.dir/build.make:57: connector/CMakeFiles/check] Error 8
make[2]: *** [CMakeFiles/Makefile2:281: connector/CMakeFiles/check.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:288: connector/CMakeFiles/check.dir/rule] Error 2
make: *** [Makefile:240: check] Error 2
==> ERROR: A failure occurred in check().
    Aborting...
:: failed to build syncthingtray package(s)

Martchus commented on 2017-11-14 19:05 (UTC)

Seems like the web UI crashes in the default configuration when the jdk package (also in AUR) is installed. To prevent this you can: * uninstall the jdk package * remove /usr/lib/jvm/java-9-jdk/lib/libdeploy.so * configure the syncthingtray package to use Qt WebEngine (using variable/switch in the PKGBUILD)

Martchus commented on 2017-06-23 09:58 (UTC) (edited on 2017-06-23 09:59 (UTC) by Martchus)

@FlorianJacob I know that I've released v0.6.1 but it contains only one new commit for building under Tumbleweed. It is not worth the rebuild.

Martchus commented on 2017-02-26 20:19 (UTC)

Should be fixed

xduugu commented on 2017-02-26 19:58 (UTC)

Doesn't build when KIO is disabled: CMake Error: The source directory "/tmp/makepkg/syncthingtray/src/syncthingtray-0.5.0/NO_FILE_ITEM_ACTION_PLUGIN=ON" does not exist. Specify --help for usage, or press the help button on the CMake GUI.

Martchus commented on 2016-10-31 11:39 (UTC) (edited on 2022-01-11 11:30 (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.

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).

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.