https://bugs.kde.org/show_bug.cgi?id=410331
Dmitry <dmitry.make...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmitry.make...@gmail.com
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
Resolution|NOT A BUG |---
--- Comment #5 from Dmitry <dmitry.make...@gmail.com> ---
Hello, new Krita user here, Windows 10 x64. I've also seen this error. And
numerous forum posts about this error, and everywhere people suggest it's a
permission issue. Well, I'm a system administrator and I'm pretty sure I have
enough permissions on my working folders. I've done some testing and (helped by
reports that files can't be saved in folders that are in root) found out that
Krita can't save a file in D:\test11, but can save in D:\test11\test22, even
though folder permissions are the same. Then I've run procmon to see what
exactly Krita tries to do. I'm not that great at understanding Windows file API
calls, but I've seen this:
D:\test11.nKanRR.kra PRIVILEGE NOT HELD
and later when successfully saving to D:\test11\test22\test.kra
D:\test11\test22.aZmNdf.kra SUCCESS
(multiple operations).
I believe the issue is Krita's trying to create a temp file not in the folder
it's saving to, but in the parent folder, probably because the last slash in
the filename (or path) is lost (or replaced with "."). Thus when saving in
D:\test11 it tries to create temp file in D:\, and that usually requires
additional privileges.
BTW, only the temp file name is affected. Later it copies temp file (if it
saved succesfully) to the intended file name, and that goes as expected:
ReadFile D:\test11\test22.aZmNdf.kra SUCCESS Offset: 0, Length: 101
629, Priority: Normal
WriteFile D:\test11\test22\test.kra SUCCESS Offset: 0, Length: 101
629, Priority: Normal
(among other things).
--
You are receiving this mail because:
You are watching all bug changes.
