Bug 441568 - Krita stuck at "Waiting for saving to complete" when closing a document with unsaved changes
Summary: Krita stuck at "Waiting for saving to complete" when closing a document with ...
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: File formats (show other bugs)
Version: 5.0.0-beta1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: efficiency-and-performance
Depends on:
Blocks:
 
Reported: 2021-08-26 12:38 UTC by Tyson Tan
Modified: 2021-08-31 15:27 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Krita Waiting for saving to complete when closing an unsaved new document (158.69 KB, image/png)
2021-08-26 12:38 UTC, Tyson Tan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tyson Tan 2021-08-26 12:38:13 UTC
Created attachment 141062 [details]
Krita Waiting for saving to complete when closing an unsaved new document

Krita shows a "Waiting for saving to complete" message and stuck when trying to close an unsaved new document after doing nothing for a while.

Steps to Reproduce:
1) Create a new document
2) Make some useless actions like freehand selection tool
3) Switch to another window for a while
4) Switch back to Krita, press Exit button on the window or press Ctrl + W to close the document.
5) Krita shows "Waiting for saving to complete" and stuck forever.


Krita log:
KRITA DID NOT CLOSE CORRECTLY
================================================================================
SESSION: 26 Aug 2021 20:34:53 +0800. Executing /home/tysontan/Applications/krita-5.0.0-beta1-8f23816-x86_64_c2c07f9e91d866a88bcfa6f01777ccef.appimage

Krita Version: 5.0.0-beta1 (git 8f23816), Qt version compiled: 5.12.11, loaded: 5.12.11. Process ID: 5433
-- -- -- -- -- -- -- --
26 Aug 2021 20:34:53 +0800: Style: fusion. Available styles: Windows, Fusion
26 Aug 2021 20:34:54 +0800: Database is up to date. Version: 0.0.13, created by Krita 5.0.0-beta1, at 周三 8月 18 15:51:43 2021
26 Aug 2021 20:34:55 +0800: KisAppimageUpdater: AppImageUpdate (/tmp/.mount_krita-U3HHp5/usr/bin/AppImageUpdate) was not found within the Krita appimage, or is not executable
26 Aug 2021 20:34:59 +0800: Removing autosave file /home/tysontan/.krita-2909-document_0-autosave.kra

Operating System: Arch Linux
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.13.12-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i9-9900KF CPU @ 3.60GHz
Memory: 62.8 GiB of RAM
Graphics Processor: Radeon RX 590 Series

krita-5.0.0-beta1-8f23816-x86_64.appimage
Comment 1 Tyson Tan 2021-08-26 12:42:33 UTC
Actually, this happened again when I attempt to close the the screenshot for attachment 141062 [details]. I cropped the original screenshot, so the file was modified, but it was only exported, not saved. The filename on Krita's window has a * to it.

So I think it happens when closing any document with unsaved changes.
Comment 2 Tyson Tan 2021-08-26 12:45:32 UTC
* when Krita attempted an autosave
Comment 3 vanyossi 2021-08-27 00:40:46 UTC
The reported hash from bug report (8f23816) is after "1b8f551f73" which caused this bug in master (hash 66a04399b1). This is fixed by master 3bd7c61221