New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
G'Mic fails to start because could not find Qt platform plugin "xcb" - Krita v3.2.0-beta.2 #87
Comments
WORKAROUNDI have been able to create a WORKAROUND until this bug is fixed. As stated in the error message, the
(If you don't have that file, then you have more problems, this workaround wouldn't apply as is.)
(again: you are issuing this command from the directory where
Summary:You need to have this directory structure where you have the
...where: |
Unfortunately this workaround won't work for me. Tried setting it up as described but no luck. EDIT: Found a workaround for the self-compiled plugin. Using a script wrapper setting LD_LIBRARY_PATH to /usr/lib/x86_64-linux-gnu/ will let the plugin work properly. It's something! |
Thanks for reporting. In any case, I think I'll have to remove the Krita plug-in binaries I provide on the G'MIC website, because I guess this won't work for many users :( |
G'Mic won't start and no information or visible reaction is shown on Krita's GUI when 'Start GMic-Qt' is selected in the Filter menu.
This issue has already been reported in krita's (KDE) bugtracking system.
When launching Krita on the console, this error is logged exactly when the 'Start GMic-Qt' button is pressed:
My system:
Kubuntu Linux 16.04;
Krita 3.2.0-beta.2 (running the appimage from /opt/krita/);
G'Mic-Qt for Krita - Linux 64 bits -2.0.3_pre#170712
Steps to reproduce:
At this point, nothing visible will happen in Krita's GUI. But if you have launched Krita from the console, then you will see the aforementioned error message.
Expected behaviour: G'Mic should launch when the 'Start GMic-Qt' button is pressed.
I have created a WORKAROUND that allows me to successfully run G'Mic in Krita 3.2 Beta2. See next post.
The text was updated successfully, but these errors were encountered: