https://bugs.kde.org/show_bug.cgi?id=463905
--- Comment #4 from Emily <pmi...@gmail.com> --- Hi! About the problem day log, it says this, basically:Error occurred on Monday, January 2, 2023 at 08:10:27. krita.exe caused an Access Violation at location 00007FFD82D648AA in module libkritaresources.dll Reading from location 0000000000000000. I'll try to check the backup files too. Em ter., 10 de jan. de 2023 às 18:13, wolthera <bugzilla_nore...@kde.org> escreveu: > https://bugs.kde.org/show_bug.cgi?id=463905 > > wolthera <griffinval...@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |griffinval...@gmail.com > Status|REPORTED |NEEDSINFO > > --- Comment #1 from wolthera <griffinval...@gmail.com> --- > Hm... That's quite little information, we usually try to us > krita-artists.org > for situations where you don't know if something's a bug or an unknown > setting > before reporting, because the forum makes it much easier to share > screenshots. > > That said, could you go to help->Show Krita log for bugreports and share > the > contents? If you aren't comfortable with that, what I primarily would like > to > know what the log says for the day of the problem. > > Other than that, you could check if the backup file does have the data, it > should be in the same folder as your original file, but then with ~ added > to > the end (unless you changed the settings in settings->configure > Krita->general->file handling), you can rename the file and remove the ~ > at the > end to be able to open it in Krita. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
