https://bugs.kde.org/show_bug.cgi?id=382491
--- Comment #12 from Nicholas LaPointe <nicholaslapoin...@gmail.com> --- (In reply to Thiago Macieira from comment #11) > > The issue I encountered involved QSharedMemory, which is used for passing > > image data back and forth. > It won't work with two Qt. Sorry, this is an unfixable problem. Right, I was saying that for the purpose of contrasting my problem and what I think might be this bug report's problem. QSharedMemory is used for passing image data while QLocalSocket is used for passing commands, and it seems like the command part is giving trouble in Windows. (I wrote about my problem here because it seemed like it could be related at first glance.) > Why do you have two Qt? If I'm not mistaken, Krita targets 5.6 as a minimum, but doesn't have a maximum. Because of that, I have a few versions of Qt installed in the /opt directory to verify that Krita works as expected when using different versions of Qt. I stumbled upon the QSharedMemory incompatibility because I didn't rebuild gmic-qt after rebuilding Krita using Qt 5.9. My own situation is different from what your earlier question was about: (In reply to Thiago Macieira from comment #9) > Why do you have two Qt5Core in the same system in the first place? The Windows version of Krita and the Windows version of the third-party plug-in gmic-qt are each bundled with Qt. We'd like the plug-in to run correctly regardless of which versions of Qt are being used. For my problem, I think we'll just have to not use QSharedMemory; for this bug report's problem, I can't say for sure if differing Qt versions are what's at fault (I don't have a development environment set up in Windows to verify). -- You are receiving this mail because: You are watching all bug changes.
