If you run a QT server application, and a client in a separate process, it will spam the log with "QWSLock::down(): Invalid argument" messages because of an old bug in the locking code. There's a patch on the net that fixes it, which I manually adapted by removing the commented-out debug statements.
We have been using this patch for about half a year without problems, and the QT people apparently don't care about the bug, hence there's no upstream status. Including this into OE core will at least save other people the trouble of having to find and apply it for themselves. Signed-off-by: Mike Looijmans <mike.looijm...@topic.nl> --- meta/recipes-qt/qt4/qt4-4.8.6.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-qt/qt4/qt4-4.8.6.inc b/meta/recipes-qt/qt4/qt4-4.8.6.inc index 074e82d..a2c0688 100644 --- a/meta/recipes-qt/qt4/qt4-4.8.6.inc +++ b/meta/recipes-qt/qt4/qt4-4.8.6.inc @@ -26,6 +26,7 @@ SRC_URI = "http://download.qt-project.org/official_releases/qt/4.8/${PV}/qt-ever file://0030-aarch64_arm64_qatomic_support.patch \ file://0031-aarch64_arm64_mkspecs.patch \ file://0032-aarch64_add_header.patch \ + file://Fix-QWSLock-invalid-argument-logs.patch \ file://g++.conf \ file://linux.conf \ " -- 1.7.9.5 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
