https://bugs.kde.org/show_bug.cgi?id=423026

            Bug ID: 423026
           Summary: Can't save changes to drives that don't support
                    "permanent version storage" on Mac
           Product: krita
           Version: 4.3.0-beta2
          Platform: macOS Disk Images
                OS: macOS
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: General
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY

Krita is unable to re-write to a drive that doesn't support "permanent version
storage" in MacOS. When using a Mac with a 3rd party drive format (In my case
NTFS with a driver from Paragon) saving over a file in most applications will
bring up a warning such as:

"The document "DocumentName" is on a volume that does not support permanent
version storage. - You will not be able to access older versions of this
document once you close it. [checkbox: Do not show this message again] [button:
Cancel) [button: OK]"

With Krita I can save a document for the first time to the drive, but I can not
save it after that. When one hits save again then Krita gives the following
error:

"Could not save /path-to-document/DocumentName.kra
Reason: Cannot open file for writing. Reason: The file could not be opened.
[button: OK]"

The solution would be to ether bypass the version storage check, or create a
warning like other MacOS software uses so that its possible to save changes to
files on other drive formats.)

STEPS TO REPRODUCE
1. Open Krita on a Mac
2. Save a File to a drive that doesn't support "permanent version storage"
3. Make a change to your file and try to save it.

OBSERVED RESULT

Won't save the edits to the file

EXPECTED RESULT

Save the file, give a warning about no versioning (optional)

SOFTWARE/OS VERSIONS
macOS: MacOS 10.13.6 

ADDITIONAL INFORMATION

Renaming folders in the Krita save dialogue doesn't work ether (same problem)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to