I'm using krita 4.0.1 appimage on debian testing. Krita doesn't create autosave files for new documents derived from templates (eg Design cinema 16:10), so in the event of a crash all the edits a user makes on the template will be lost. A custom document will get autosave files, so the user can recover some of their work on a custom document if a crash occurs. Steps to reproduce: 1) Create a new document using the Design cinema 16:10 template, and another custom document. 2) Make some brush strokes on both documents 3) Wait for the autosave delay period to pass for both documents 4) SIGKILL krita or crash it somehow 5) Start krita again Expected result: Krita offers to recover autosave files for both documents Actual result: Krita only offers to recover the autosave for the custom document
Weir, I cannot reproduce the issue. Both files get saved... But Deevad has just reported that autosave fails to work after the first save operation on the file... that might be related.
I can reproduce neither of the reports :( If one saves a file, the autosave gets saved into the same directory as the file itself. And the recovery is suggested when one tries to open this file again.
(In reply to Dmitry Kazakov from comment #1) > Weir, I cannot reproduce the issue. Both files get saved... Does the name of the template file's tab/window view have "[Write Protected]" included in it? if it doesn't then I guess the issue is just with my particular setup. (In reply to Dmitry Kazakov from comment #2) > If one saves a file, the autosave gets saved into the same directory as the > file itself. And the recovery is suggested when one tries to open this file > again. Right, but when one is working on a new document that has not yet been saved (according to the steps I've outlined) then I think krita usually puts the autosave file in the user's home directory and offers to recover that file after a crash or some other failure.
If the name in the titlebar includes "[Write Protected]" then that means the location cannot be written to; that's not something we can fix. Could you check whether that's the case?
Hi, Boud! Can it be that Krita tries to save autosave of the templated file into the same folder with the template itself? Afair, our expected behavior for unnamed documents is to save into home folder, probably we have some specific option for the templates?
That could be... But it's not the behaviour I'm seeing.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug still exists for me on the 4.2.0-pre-alpha (git 715ad13) appimage I downloaded yesterday. (In reply to Boudewijn Rempt from comment #4) > If the name in the titlebar includes "[Write Protected]" then that means the > location cannot be written to; that's not something we can fix. Could you > check whether that's the case? I figured out that templates are stored in directories like /tmp/.mount_krita-hWinAD/usr/share/krita/templates, everything contained in .mount_krita-hWinAD/ is owned by root, so krita can't autosave there. drwxrwxr-x 3 root root 0 Oct 10 00:19 .mount_krita-hWinAD I tried to chown it but it didn't work, am I using chown incorrectly? $ sudo chown -R wyst /tmp/.mount_krita-hWinAD/ chown: cannot access '/tmp/.mount_krita-hWinAD': Permission denied Seems to be an issue with my machine, no idea how to fix it though. I think Krita should warn the user that it can't do an autosave in situations like this, similar to how it warns the user that it is post-poning autosave when the document is busy (can happen when a CPU intensive filter is still processing). The "[Write Protected]" warning only appears in the window title (not visible in fullscreen) and in the tab title (not visible in sub-window mode). It ought to appear in the status bar like the autosave post-pone waring does. Should I make a new wishlist ticket and close this ticket, or just edit this ticket?
Updated status to REPORTED and version to nightly appimage (git 715ad13)
Created attachment 115717 [details] (Video example) I can reproduce this with the latest Krita 4.2.0-pre-alpha (git a2ae7f3) and with Krita 4.1.5 as well (see video).
Confirming.
Git commit 292b1db151704be3779874fed8e21fac4ad02798 by Boudewijn Rempt. Committed on 16/05/2019 at 11:33. Pushed by rempt into branch 'master'. Autosave in the unnamed location if the current document was readonly M +1 -1 libs/ui/KisDocument.cpp https://invent.kde.org/kde/krita/commit/292b1db151704be3779874fed8e21fac4ad02798
Git commit 31bc40499b259705f96b10140667145f75466e77 by Boudewijn Rempt. Committed on 16/05/2019 at 11:32. Pushed by rempt into branch 'master'. Set the document we created from a template to read/write If the template is in a read-only folder (like an installation location) the document would be set to ReadOnly, which is wrong. M +1 -0 libs/ui/KisPart.cpp https://invent.kde.org/kde/krita/commit/31bc40499b259705f96b10140667145f75466e77
Git commit 2f984c10ecf7cd6c7da36d211104112222576bee by Boudewijn Rempt. Committed on 17/05/2019 at 08:12. Pushed by rempt into branch 'krita/4.2'. Set the document we created from a template to read/write If the template is in a read-only folder (like an installation location) the document would be set to ReadOnly, which is wrong. M +1 -0 libs/ui/KisPart.cpp https://invent.kde.org/kde/krita/commit/2f984c10ecf7cd6c7da36d211104112222576bee
Git commit 4b3cf1c93de0af4704f745201bbdd87874a5c495 by Boudewijn Rempt. Committed on 17/05/2019 at 08:12. Pushed by rempt into branch 'krita/4.2'. Autosave in the unnamed location if the current document was readonly M +1 -1 libs/ui/KisDocument.cpp https://invent.kde.org/kde/krita/commit/4b3cf1c93de0af4704f745201bbdd87874a5c495