https://bugs.kde.org/show_bug.cgi?id=393112
--- Comment #8 from Wysteria <nabstertopsykre...@gmail.com> ---
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?
--
You are receiving this mail because:
You are watching all bug changes.
