So, I have 15gb RAM. Troubleshooted just in case with keeping certain programs open and closing all of them. Same result. Yesterday I was able to draw for a bit and it randomly closed maybe once or twice. However, I called it a night when it froze my entire PC when i tried to force it closed, which led me to unplug my PC. And today, I only managed to make simple 1 minute doodles before it crashes or freezes, and this time it glitches a bit too, with me hitting undo making random light strokes show up.
Is this something to report as a bug, or potentially an issue on my end. I’m on Linux Mint 22.1
I think it would take a lot more information to figure anything out. Maybe there’s a log file reporting errors…
As a suggestion, try an older version of Krita to see how it behaves.
(I’m using Mint 22.2 and the latest Krita, 16GB RAM, and a 2nd-generation i7. Everything is running smoothly)
Krita has crash and other logs you can access through the “Help” menu. Those can perhaps have some useful information. Most recent entries are at the bottom of the log files.
woops idkhow the forums work, i deleted my comment thinking it didnt reply to you. but yeah i downlaoded 5.2.2 and it works fine; i have an i3 so maybe its hardware
good to know, thanks. i didnt know that ToT
I came here because after just upgrading my Appimage from 5.2.11 to 5.2.13 Krita already crashed twice in 2 hours on my Kubuntu 24.04 (system kept up to date). In both cases it happened when I hit a keyboard shortcut, last time it was Ctrl+T (transform). I looked at Krita log in Help menu and at some the system logs but I could not find anything useful. Maybe Plasma will produce some type of error report that may indicate what process had crashed.
For the time being I’m downgrading back to 5.2.11, I may try using 5.2.13 with short autosave intervals. Krita has been extremely stable on this machine before updating to 5.2.13.
Yeah my krita worked pretty fine before the update from 2 weeks ago, i happened to time shift back to the end of september and it was all good. i set my system to ignore any update after the end of that month but i impulse updated the third party plugins which took be back to the issues ive mentioned here xDD
I have a mild suspicion that this could be related to changes in Linux packages. I had both 5.2.13 and 5.2.11 crash and that’s not a good feeling.
@dkazakov Dmitry, is there a specific Linux command that I could run to troubleshoot Krita while I’m drawing, to show you what’s going on in case it crashes again?
Hi!
Could you download this debugging package and run it under gdb? When it crashes, gdb will let you show the backtrace, which you could show us:
Check instructions on how to run it in “crash bug” section of this document:
@dkazakov Dmitry, I downloaded the prealpha and tried running over gdb, so far no crashes.
But when I opened my working version of Krita, I was greeted with a message saying something about my resource database having to be rebuilt.
Let me just say that I’m very unhappy with the results of that rebuild, I have a lot of cleanup to do. Does this have anything to do with running Krita over gdb prior to this?
Another question is: does it make any sense to run/test 5.2.11 and 13 on gdb, or do I need a specially compiled version of Krita?
Thank you.
The database change is because the debugging version was 5.3, which has newer version of the database. Yes, you can try to run the released version of 5.2.x under GDB with the same command. Though the resulting backtrace may be not helpful with about 50% probability. Though you might be lucky and we’ll manage to decrypt it 
OK thank you. Next time I’ll try to run 5.3.x under a different user account so my 5.2.x database stays intact.
You can just make a backup of resource files in %APPDATA%\krita and the config file in %LOCALAPPDATA%\kritarc and then restore them after switching back to the stable version.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.