https://bugs.kde.org/show_bug.cgi?id=398192
--- Comment #9 from TallFurryMan <eric.dejouha...@gmail.com> --- Refining the test, it appears the issue may source from the intrication of signals between gadgets. The code is re-entring the event loop at various places, and if the INDI server is still busy deleting properties, the code locks up in QMetaObject::Activate. Originally I thought it was the way QTest is implemented, which requires lots of deferred calls to manipulate the UI, but it seems I got the test right in the end. Jasem, I pushed D27593 with the test showing the issue. Remove the delay as specified in the differential to reproduce. -- You are receiving this mail because: You are watching all bug changes.
