I’m only starting this new thread because I want to know if I’m the only one having problems with Krita 5.3.1. I installed version 5.3.0, and in that version, resources and brush labels would disappear. It’s also very slow to start up, and sometimes it gets slow while working on the canvas. Then, in version 5.3.1, it was worse because, in addition to the labels disappearing, the interface froze several times after opening. I couldn’t move anything, and it said that Krita had to close. I sent a screenshot of the debug mode to the developers. I use LMDE based on Debian 12, and I’ve never had any problems with Krita before. I’d like to know if this is a widespread problem or if it’s just my computer. I’ve tried everything, even deleting all the Krita configuration files and settings from my computer and reinstalling it, but nothing works. I’ve had no choice but to go back to version 5.2.16. I don’t know if the Krita team is working on a patch or if the problem only affects a few unlucky users.
I don’t know if it is widespread on Linux.
Since you don’t explicitly name the version you use, you should check errors on Linux always against the one and only official version of Krita for Linux first, which is the AppImage from Krita’s homepage! And do not forget to set it executable via its preferences.
Michelist
I’ve used krita 5.2.16, 5.3.1 and the 6.1.0 prealpha on ‘standard’ (Ubuntu based) Linux Mint and have never had any problems apart from the various small bugs that affect everyone.
I always use the appimage and I have a slow old desktop computer.
I’m very puzzled by the various reports of serious problems that people seem to be having recently.
97
Which version are you referring to? I was using Krita 5.3.1 and LMDE based on Debian 12. Thank you for your response.
Thanks for replying, and unfortunately, I am having those problems with Krita 5.3.1. It has fantastic improvements, but it seems to be having trouble forming the database with the resources on my machine, and in the last few crashes, it’s been related to screen orientation. I’ll reinstall it to see if I missed something during the previous installation.
Are you running the appimage? If not, I strongly suggest that you do.
The appimage is not ‘installed’ in the usual sense of the word. It’s an executable file that you run, after you’ve changed its permissions, after downloading it, to make it executable.
Sorry, I better had used “variant” instead of version, and it was the question if you use the version from your repository, Flatpak, Steam, or from wherever else, because only the AppImage is official all other versions are community maintained builds and not seldom implement extra bugs unknown from the AppImage.
Michelist
Thank you so much, you’re very kind. In my case, I love AppImage, so I’m downloading the official version. I’m going to run a clean install; I just downloaded it and I’m going to tinker around for a while to see if I can resolve the conflicts. I suspect that the changes in the way the database is structured might be causing conflicts with older .bundles and, of course, with outdated plugins. Thanks for your comments. If I find a way to resolve it, I’ll document it and upload it here.
For a truly ‘clean and fresh’ experience, I recommend that you run the appimage in an isolated home environment. That way it will not be affected by any previous history.
That’s how I run all my appimages, not just krita. See this post for an explanation:
Bug where pasting something into the current document will crash Krita - #10 by AhabGreybeard