Created attachment 150106 [details] Krita system information 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 *** Finished a session with a save, where, let's say, an arm was drawn. Some other parts, say, wall, was drawn a week ago. After reopening file - the wall wasn't drawn on the image. The next day the same thing happened to mouth. STEPS TO REPRODUCE 1. Have no idea, it happened twice. No crashes, just saved file (.kra format), reopened it - and here it is. OBSERVED RESULT Some parts, that weren't even touched during the previous session - was totally removed. They weren't even on a separate layers. EXPECTED RESULT The opened file is the same, as the saved one. SOFTWARE/OS VERSIONS Windows: 10.0.19044.1766 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.12.12 ADDITIONAL INFORMATION
Created attachment 150107 [details] Krita usage log
Comment on attachment 150107 [details] Krita usage log Saved last time 23 Jun 2022 00:44:50. Today after reopening some parts are missing.
Hi, does your target folder for saving your file is synchronised remotely with a cloud or backup services? A synchronisation bug with such a service could explain this effect.
(In reply to David REVOY from comment #3) > Hi, does your target folder for saving your file is synchronised remotely > with a cloud or backup services? > > A synchronisation bug with such a service could explain this effect. As I know - not. I haven't set up anything like this. If there is a way to check if there is something that was applied automatically - please provide it and I'll re-check.
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.
From the log it looks like you're solely working with autosave files? That's not a good habit... In any case, this cannot be a bug in Krita. It must be a user error -- like having a file open twice, using autosave files instead of properly saving. But not something we can fix in Krita.