Created attachment 103521 [details] Backtrace crash report when tried saving a new .kra file I have recently updated Krita to the newest git version 3.1.88 (git 57fe954), from the previous version, where there was no issues. But when I first started trying to make a new image I noticed that it took longer than it should have to open up. Then I started to draw and about the time when krita would autosave, every 5 min, it would crash; losing all the settings that I had had set with brushes and layouts. Then I tried to save the new file, I had just created, right away, but it would crash instantly. So I tried opening previously made .kra files and with same result it would crash again. But opening a .png or .jpg file there was no issue. Exporting the image as a .png it gives me an internal error but doesn't crash. Everything in the setting is default for the image, so I don't know why it is doing this. I can't even use Krita from the git version. The 3.1.1 snap package all works fine. I had no crashes with opening or saving files.
Created attachment 103522 [details] gdb krita just in case the backtrace report was lacking information needed
Hi, It looks like you build Krita yourself. You might need to make a clean build and a clean install dir because somehow two builds have become mixed up: QMetaType::registerType: Binary compatibility break -- Size mismatch for type 'KisGridConfig' [1100]. Previously registered size 84, now registering size 68 That means that binaries from two builds are being loaded in the same process. This isn't a bug in Krita; it's a problem with your build, so I'm closing the report.
*** Bug 375214 has been marked as a duplicate of this bug. ***
Created attachment 103550 [details] attachment-25929-0.html Thank you for the reply. On Thu, Jan 19, 2017 at 3:37 AM, Boudewijn Rempt <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=375285 > > --- Comment #3 from Boudewijn Rempt <boud@valdyas.org> --- > *** Bug 375214 has been marked as a duplicate of this bug. *** > > -- > You are receiving this mail because: > You reported the bug. >