I've made about 4 different topics over the past year and a half about krita crashing on linux ubuntu, not autosaving properly, and then me not having the proper information to have my topic considered.

The last thread I made here: viewtopic.php?f=139&t=152308

Krita crashed and I lost a ton of work. I tried to provide as much info as I could, but nobody would tell me exactly what was needed, and in the end my problem got ignored.

I love this program, but have serious issues with it being reliable. I'm running it off of really solid hardware too with an Nvidia gtx 960, 12 gigs of ram, and running off ubuntu 18.04 with an installed version of krita from the PPA. This really shouldn't be so unreliable.

Just yesterday in the middle of an animation, in the middle of me drawing, I was getting weird display errors on one of my frames. The brush tool wouldn't paint, but would randomly turn the pixels I painted white. I started getting strange artifacting after a few moments. I tried saving my work to a new file and re-opening it, and the entire frame was just deleted. There were no autosave files for me to use either, and I have my autosave feature set to save every 1 minute.

Most other times the program in the middle of drawing will just immediately shut down with no warning. This happens frequently enough to make letting go and focusing on being creative a challenging. And since I can't seem to trust to autosave feature, I'm having to slap the f4 key every few minutes to create incremental backups.

I can provide data, whatever is needed. But I need to know what to provide and where to give it. I want to help make this program more reliable and support it in whatever way I can.

Hi forleafe,

For crashes the major thing we need is backtraces. The PPA should contain debug symbols, which in turn should cause a window to pop-up when having a crash.

If that doesn't happen, try running Krita with GDB:

https://community.kde.org/Guidelines_an ... e_with_GDB

Then, if you have a backtrace it needs to go to bugs.kde.org under the product Krita.

For other bugs they should also always go to bugs.kde.org because we cannot track a bug on the forum.

EDIT:

For some reason the PPA doesn't contain debug symbols, I am gonna bother the person responsible for it to add them. :/

EDIT2:

Actually, it is called "krita-dbgsym". You should be able to install them if they aren't already.

TheraHedwig wrote:Hi forleafe,

For crashes the major thing we need is backtraces. The PPA should contain debug symbols, which in turn should cause a window to pop-up when having a crash.

If that doesn't happen, try running Krita with GDB:

https://community.kde.org/Guidelines_an ... e_with_GDB

Then, if you have a backtrace it needs to go to bugs.kde.org under the product Krita.

For other bugs they should also always go to bugs.kde.org because we cannot track a bug on the forum.

EDIT:

For some reason the PPA doesn't contain debug symbols, I am gonna bother the person responsible for it to add them. :/

EDIT2:

Actually, it is called "krita-dbgsym". You should be able to install them if they aren't already.

I'll go ahead and install this. But does running krita out of the terminal have the same effect? I run all of my programs from a terminal so I know what's going on should any of them have issues.