SUMMARY Autosave doesn't work for new files that haven't been saved yet, saving fails with 'Access Denied' message. STEPS TO REPRODUCE 1. Create a new file 2. Wait for the autosave to happen (depends on your autosave frequency setting) OBSERVED RESULT Autosave fails with a message "Error during autosaving: .krita-6423-document_0-autosave.kra: Access denied, displayed in status bar, or as a popup in top left corner. In krita.log file there are following messages: Converting from application/x-krita to application/x-krita. Location: C:/Temp\.krita-6423-document_0-autosave.kra. Real location: C:/Temp\.krita-9824-document_0-autosave.kra. Batchmode: 0. Configuration: none Completed saving C:/Temp\.krita-6423-document_0-autosave.kra (mime: application/x-krita). Result: Access is denied. EXPECTED RESULT Autosave working normally SOFTWARE/OS VERSIONS Windows: Windows 10 Krita: 4.1.7, 4.2.0-pre-alpha (git 9ec2737) ADDITIONAL INFORMATION Autosave works normally for files that were saved or opened, because it saves autosave files in that file's folder. There's no visible error message in 4.2.0-pre-alpha, but it does write messages to krita.log.
Usually, the temp folder on windows is located in "C:/Users/<USER>/AppData/Local/Temp", apparently you configured your windows to so it's c:\Temp, and at the same time didn't give yourself permission to write there. That's not a bug in Krita, though we could add logic to check if the temp location is writable, and if it isn't try somewhere else, but that's a lot of working around a misconfiguration. Apart from that. there's nothing we can do, though in 4.2.0 you can also choose to select your c:\Users\<USER>\ as the default location fo unsaved file autosaves. I've considered making it possible to configure the path where unnamed autosave files would be saved to, like it's possible to configure the path for swap files (also by default the temp dir), but that would give a lot of headaches when it comes to user support.
Created attachment 119838 [details] attachment-2414-0.html Oh, thanks. Yep, suspected it was something like this, due to my %temp% location, but I thought it'd be okay because it looked like it would have write permissions, at least from the looks of Security tab in properties of c:\temp\ - Full control for Everyone, SYSTEM, Administrators and Users, and even though there were no permissions set for my user profile specifically, it's reasonable to assume that I and programs I run under that user would have those permissions inherited from permissions for all Users. Even when I set permissions specifically for my user profile, autosaving would fail. It's good to know that there will be more options for autosave location. Thank you. On Mon, Mar 18, 2019 at 4:46 PM Boudewijn Rempt <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=405574 > > Boudewijn Rempt <boud@valdyas.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |RESOLVED > CC| |boud@valdyas.org > Resolution|--- |NOT A BUG > > --- Comment #1 from Boudewijn Rempt <boud@valdyas.org> --- > Usually, the temp folder on windows is located in > "C:/Users/<USER>/AppData/Local/Temp", apparently you configured your > windows to > so it's c:\Temp, and at the same time didn't give yourself permission to > write > there. > > That's not a bug in Krita, though we could add logic to check if the temp > location is writable, and if it isn't try somewhere else, but that's a lot > of > working around a misconfiguration. > > Apart from that. there's nothing we can do, though in 4.2.0 you can also > choose > to select your c:\Users\<USER>\ as the default location fo unsaved file > autosaves. > > I've considered making it possible to configure the path where unnamed > autosave > files would be saved to, like it's possible to configure the path for swap > files (also by default the temp dir), but that would give a lot of > headaches > when it comes to user support. > > -- > You are receiving this mail because: > You reported the bug.