SUMMARY STEPS TO REPRODUCE 1. Paint 2 hours, constantly saving file 2.Try to open file next day from recent files 3. Krita claims file is invalid! 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
If you have been constantly saving, there should be a backup file (those end in .kra~). Try to rename that to some_other_filename.kra and try to open it. If the original .kra file is larger than 0 bytes, you can try to repair it with ziprepair pro. There are several reasons why failing might save (no disk space, saving to a dropbox folder just when dropbox decides to sync and lock the files, hard disk trouble), and we're currently working really hard on making it clearer when and why a save has failed, but there's not much we can do with this report, since the failures are always system-specific.
I was renaming the file and noticed that the extension was “.kra~” I have no idea how the tilde got there. I never fool with the extension part of the name. File loads just fine now. Richard Haas Sent from my iPad > On May 21, 2019, at 11:50 AM, Boudewijn Rempt <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=407802 > > Boudewijn Rempt <boud@valdyas.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |boud@valdyas.org > > --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> --- > If you have been constantly saving, there should be a backup file (those end in > .kra~). Try to rename that to some_other_filename.kra and try to open it. If > the original .kra file is larger than 0 bytes, you can try to repair it with > ziprepair pro. > > There are several reasons why failing might save (no disk space, saving to a > dropbox folder just when dropbox decides to sync and lock the files, hard disk > trouble), and we're currently working really hard on making it clearer when and > why a save has failed, but there's not much we can do with this report, since > the failures are always system-specific. > > -- > You are receiving this mail because: > You reported the bug.
The ~ is what distinguishes the backup copy from the original file. Everytime you save, the original file will be copied to the kra~ file, just for safety.
I'm sorry, but there isn't much we can do here -- things like this are a system failure, not a bug in krita.