SUMMARY I'm bitterly reporting that thanks to Krita being somewhere unstable, it wiped of my long work progress today. At random, the program won't dare save progress. And when it happens, you can't save anything more. This, hurts me like I can't explain it. Especially given the fact that I was doing professional work with the app. STEPS TO REPRODUCE I don't know how to reproduce the issue. The saving system of your app is unstable and that's all. OBSERVED RESULT Firstly it writes autosave, but it's stuck at a level in the progress bar. It didn't budge for lots of minutes. So I cancelled it. I then continued to work and tried to save again using all possible ways, but no saved file anymore. And the saving progress bar won't ever show up again after you confirm save location and file name in the save dialog. EXPECTED RESULT The save system should be flawless. By the way, this isn't common to this version of Krita only. It also happens with 4.4.2 and 4.4.3. SOFTWARE/OS VERSIONS Windows 10 1909 Additional information. App used : Krita stable git version 4.4.4 alpha(7d4dcb1) As soon as I noticed that I couldn't save to a new file, I wanted to copy all the layers. But when I did so, Krita immediately crashed !
Can you please attach the content of Help -> Show Krita log for bug reports? And please do tell how was your work (the one you lost progress in) called.
(In reply to Tiar from comment #1) > Can you please attach the content of Help -> Show Krita log for bug reports? > And please do tell how was your work (the one you lost progress in) called. Here's the log data ! ------------------------------------------------------------------- WARNING: The Krita usage log file doesn't exist.File name and location: C:/Users/Yed/AppData/Local/krita.log------------------------------------ Krita Version: 4.4.4-alpha (git 7d4dcb1) Qt Version (compiled): 5.12.9 Version (loaded): 5.12.9 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.18363 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (NVIDIA GeForce GT 640M Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 3.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true Hardware Information Memory: 9 Gb Cores: 4 Swap: C:/Users/Yed/AppData/Local/Temp ------------------------------------------------------------------- The work was called : A5_P03A_450ppi_new.kra It's the file for a comic page.
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.
Uhh, "WARNING: The Krita usage log file doesn't exist.File name and location: C:/Users/Yed/AppData/Local/krita.log------------------------------------" that's incredibly unfortunate, and I have no idea how you ended up in that situation, krita.log is something that Krita writes every time it's opened. Since you don't have it, we can only guess what happened... Please check if there is a crash log on your system according to this instruction: https://docs.krita.org/en/reference_manual/sharing_krita_logs.html#windows > but it's stuck at a level in the progress bar. > It didn't budge for lots of minutes. So I cancelled it. It probably was saving the binary data for a long time (so it was "stuck" on 60%), the progress reporting for saving .kra is quite basic, it doesn't run smoothly. > I then continued to work and tried to save again using all possible ways, but no saved file anymore. > And the saving progress bar won't ever show up again after you confirm save location and file name in the save dialog. That sounds very wrong... there is a chance it still tried to save the original file so it ignored all future save like in bug 410024. (Another related bug is bug 409445). I'll try to recreate this situation to see if there are specific steps to get both the crash and no saving. --- Thanks for reporting, btw, we've got some reports about failed saving but we need enough information to at least guess what happened, otherwise we cannot fix it... your report at least gave me a clue.
*** This bug has been marked as a duplicate of bug 410024 ***