I trawled the net to see how many linux users of krita there are but came up empty!
The reason I ask this question is the hope I am not the only person in the world with python addons failing to run on appimages. For me, up until Krita 5.1.4 all addons worked properly. From that version forward a QT error exists even to the present stable version. This error also occurs in all nightly builds since 5.1.4. so it looks like I will experience problems into the future with appimages. However, this error does not occur in the current Flatpak 5.2.2 version. Has anybody running appimages experienced such issues? I am not a programmer and (probably incorrectly) attempted to articulate this in bug report 480542.
As of 5.2, plugin builders had to make a change to their plugins in order to run on Krita. This was due to a QT upgrade. It’s possible that Flatpak didn’t add the upgraded version of QT and that’s why the plugins were working with that Flatpak version and not appimage.
Appimage is the only official (and recommended) way to run Krita on Linux.
Please don’t feel naive. I barely understand what I put in my post. It’s just that I’m on this forum every day and I’ve picked up a lot via osmosis.
If there is a particular plugin that’s giving problems, best thing to do is send a note to its owner - either on this forum (if they have published the plugin here) or on github (where most of the plugins seem to be hosted).
It is also important to update your plugins, just as you update Krita. So for each plugin that stops working, visit the corresponding homepage to see if there are updates and update your plugins.
Some plugin authors unfortunately have not updated their plugins, for various reasons I guess, maybe some don’t use Krita anymore, others may not know what happened to their plugins, or they may not even know that something happened because they don’t use their plugin anymore, but if we users don’t point it out to them, they may never know that they should refactor their code. So, to anyone who has a plugin that no longer works: Please tell the author of your plugin and ask them if they are willing to fix it.
Hi @mugwah , appimage user here, Fedora Linux 39 KDE. All third party plugins works (python scripts/plugins, Gmic, etc…).
I trawled the net to see how many linux users of krita there are but came up empty!
I probably live in a bubble, but I can guarantee you it’s far from being empty . Proprietary search engines nowadays −especially those "AI powered"− will probably redirect you to mainly commercial options and depreciation of free alternatives.
Has anybody running appimages experienced such issues? I am not a programmer and (probably incorrectly) attempted to articulate this in bug report 480542.
I opened your bug report: 480542 – Appimage looking for PyQt5.QtTest in the wrong place , and it looks like you use a Linux Mint operating system based on Ubuntu 20.04. Meaning a Linux distro that received a package freeze in December 2019, soon 5 years ago.
I’m not asking you to upgrade your OS just for a software; that would be a terrible advice if everything is working as you like on your side except krita/appimage. That’s a lot of work.
But I underline that because from my own experience, appimage rarely includes everythings as in “every dependencies” at their core. I noticed some bits still depends of the operating system they run on (I can’t open anymore old appimage I stored on my disk for this reason I guess: dependencies issues).
That’s probably where the Flatpak version is doing a better work in comparison. So maybe in your case it is better (lowest effort) to stick with this package.
+1 with @Michelist , Python plugins manually installed tends to suffer quickly of being outdated.
I wrote previously “everything is working”, but it’s not true: I lost 5 month ago the possibility to use the krita-plugin-reference. I bug reported it, but the project looks like unmaintained.
That’s why in general I try to not relly or get used to external plugins as much as I can.
The 5.2.x versions rely on recent versions of the libc packages and that is why my old Debian 10 system can’t run 5.2.x.
However, with my Linux Mint 21.3 system, I can run the version 3.0 appimage.
I haven’t tried fully testing everything on it of course but it does paint and save and export.
The reason why i started this thread is I wished to prove the problem was not caused by the state of my ageing version of Mint. So,I ran a live ISO of the current release (linuxmint-21.3-cinnamon-64bit.iso). Then I downloaded a “perfect” Krita.AppImage and the QT problem was still there. I then downloaded and ran the most recent Krita-next.appimage and still the QT problem exists. I must point out Krita and its built-in extensions appeared to work well in the live environment. It’s the (from PyQt5.QtTest import QTest) call that shows an error.
My OS will reach end-of-life in 2025. I believe I can get a cleaner and more stable system by erasing /root and installing the next LTS version. I keep /home on a separate hard drive and /root is on an SSD. Before I embark on that project I wished to see if there would be a “Krita Advantage” in doing it right now. The answer appears to be no!
Tried running Krita appimage in a live Ubuntu (ubuntu-22.04.3-desktop-amd64.iso) and got an error:
ubuntu@ubuntu:~/Downloads$ ./krita-5.2.2-x86_64.appimage
dlopen(): error loading libfuse.so.2
Went searching and found fuse3 is the shipped version (3.10.5-1build1)
Got Krita to run eventually with --appimage–extract but it developed “special needs” so I gave up.
What I will do is wait until the “Powerful People” start canvassing for feedback when RC2 waters break and see if the PyQt issues are still around for the next rebirth!
. Proprietary search engines nowadays −especially those "AI powered"− will probably redirect you to mainly commercial options and depreciation of free alternatives.
I’ll update it!