SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION My version of Krita is 5.1.3. I didn't understand what happened so that all layers of my animation became empty, even though they were colored and changed hours before, on the same day. I don't know if it's a bug or some layer setting that was accidentally turned on, but I've been trying to troubleshoot this to no avail.
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.
Created attachment 155191 [details] attachment-2880-0.html Thank you for your support, I'll try this! Em ter., 10 de jan. de 2023 às 18:13, wolthera <bugzilla_noreply@kde.org> escreveu: > https://bugs.kde.org/show_bug.cgi?id=463905 > > wolthera <griffinvalley@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |griffinvalley@gmail.com > Status|REPORTED |NEEDSINFO > > --- Comment #1 from wolthera <griffinvalley@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.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
Created attachment 155233 [details] attachment-5375-0.html 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_noreply@kde.org> escreveu: > https://bugs.kde.org/show_bug.cgi?id=463905 > > wolthera <griffinvalley@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |griffinvalley@gmail.com > Status|REPORTED |NEEDSINFO > > --- Comment #1 from wolthera <griffinvalley@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.