https://bugs.kde.org/show_bug.cgi?id=382491
--- Comment #15 from Alvin Wong <alvinhoc...@gmail.com> --- (In reply to Boudewijn Rempt from comment #14) > For the record: > > On Thursday, 20 July 2017 01:18:20 PDT Boudewijn Rempt wrote: > > I just got this bug report: https://bugs.kde.org/show_bug.cgi?id=382491 , > > which suggests that QSharedMemory only works if both applications were > > built with the same version of Qt. Is that correct? I cannot find anything > > about that in http://doc.qt.io/qt-5/qsharedmemory.html > > You can find it in the changelog, in the "Impotant Behavior Changes" section. > http://code.qt.io/cgit/qt/qtbase.git/tree/dist/changes-5.9.0#n35 > > - [QTBUG-60771] Reverted a change that caused Qt 5.6 through 5.8 not to > connect to QSystemSemaphore and QSharedMemory created by running > applications using Qt earlier than 5.6. Unfortunately, this means that Qt > 5.9 will not connect to 5.6-5.8. This appears to affect only Linux and Mac, so let's not mix the two issues here. Considering the Windows situation, the timestamps between Krita sending a message and gmic-qt responding "gmic-qt: empty answer!" or "gmic-qt: Got the wrong answer!" are 2 seconds apart, which just so happens to match the timeout specified: https://github.com/c-koi/gmic-qt/blob/8e4511256c0b420f33252356d4741034044423ae/src/host_krita.cpp#L105 This could indicate that the QLocalSocket isn't flushing normally. -- You are receiving this mail because: You are watching all bug changes.
