When a plugin fails to load Python Plugin Manager displays an pop-up error message. How can I capture this information as there is no way to select it or copy it? PrntScrn does not capture it either. The only way I can save this information is to photograph the screen with a phone!!! Surely there has to be a better way?
1 Like
For me, this is not true.
Unfortunately, you have forgotten the most important information we need: your OS and the version of Krita this happens with.
And I guess the author(s) of the Plugin(s) in may be interested to know the name of the plugin in question.
Copied with PrntScrn on Windows 10:
Michelist
Apologies for sys-data omission.
The reason I did not include plugin details is that it may detract from the issue. The inability to capture the error popup appears to be the synergy of Krita coding and OS design. I am trying to get an answer for the error content from the (Actuator) developer on a separate channel.
Here is the SysInfo:
Krita
Version: 5.2.2
Hidpi: true
Qt
Version (compiled): 5.15.7
Version (loaded): 5.15.7
OS Information
Build ABI: x86_64-little_endian-lp64
Build CPU: x86_64
CPU: x86_64
Kernel Type: linux
Kernel Version: 5.4.0-167-generic
Pretty Productname: Linux Mint 20.3
Product Type: linuxmint
Product Version: 20.3
Desktop: X-Cinnamon
Appimage build: Yes
Locale
Languages: en_IE, en_Latn_IE, en, en_US, en_Latn_US
And if the author of the Actuator Plugin is in the vicinity maybe we could âkill two birds with one stoneâ as they say!
1 Like
You might get faster help if you go to the pluginâs web page and leave a comment for the creator. You could check to see if you have the most recent version at the same time.
At least a ping of @yetanotherpainter should be sent like I did now, so it is no need that youâll ping the author too. This could lead to an openly viewable solution, what is the preferable way for any issues discussed in a forum, this way others could theoretically profit from a found solution.
But maybe the other channel means PM or contact via the pluginâs store page? To get silent support hidden for the eyes of other usersâŚ
Michelist
Judging by the error it is a system error. libQt5Test.so.5 has unrefined symbol.
This error does not seem to be caused by the Plugin code itself 
With all my desire to help. It seems to me that is out of the plugin control. Unless I just remove usage of qTest import. Which I am not sure could fix the issue.
I tested Actuator against Krita 5.2.2 on Windows platform. And it is operational.
Hmm, with that kind of error I was suspecting OP might not be using the appimage, but the debug info says âAppimage build: Yesâ 
Actuator ran successfully in Krita 5.1.4.
Running you code snippet in 5.2.2 gave the following output:
==== Warning: Script not saved! ==== **** ImportError: /lib/x86_64-linux-gnu/libQt5Test.so.5: undefined symbol: _Z32qt_register_signal_spy_callbacksRK21QSignalSpyCallbackSet, version Qt_5 In file: In function: at line: 1. Line with error: **** (edited)
Just to clarify: All Appimages I tested Actuator on were official versions downloaded from Krita website and not compiled by me.
++++ I have moved this discussion over from Discord ++++
Just to add a context. I asked @mugwah to run small code snipped in a scripter
from PyQt5.QtTest import QTest
QTest.qWait(2000)
print('I was waiting for two seconds')
And it seems that Qt Dependencies for that app image are broken somehow.
Just for fun I installed the flatpak version of Krita 5.2.1
Actuator 0.7.3 works just fine!
Hope this helps narrow down the search for an appimage solution
1 Like
If there is a problem with appimage we should investigate this and report a bug.
1 Like
I just ran that snippet in scripter on a 5.2.0, 5.2.2 and recent-ish nightly appimage. and for me it doesnât cause any issues.
Though maybe the PyQt5.QtTest package (or PyQt as a whole?) is not part of the appimage, so itâs a gamble whether the system version is compatible or not? Which seems wrong, but I donât know much about these things.
Interesting. The whole goal of the appimage is to have âindependentâ environment to run the application.
I wonder if appimage does not include the Qt.
The error says itâs trying to import QtTest from what seems to be a system lib at /lib/x84_84-linux-gnu/libQt5Test.so.5. When I run the code from PyQt5 import QtTest in the Appimage, I get an error that libQt5Test.so.5 doesnât exist, although there is one in the Appimage directory (under usr/lib/). In other words, it seems to be looking in the wrong place for it.
1 Like
hello! I was trying to move to linux and I have encountered the same libQt5Test.so.5 error with both a recent nightly appimage build and the official stable appimage from the Krita website.
Did anyone make a bug report since this was found? I can make it if we donât have one yet.
Thereâs an open bug report for that. It seems like it needs more investigation. 480542 â Appimage looking for PyQt5.QtTest in the wrong place
2 Likes