Comment 1 for bug 211735

I see this bug on OS X. I've not reason to suppose that it is either win32 specific (as the tag suggests) or Unix specific.

When "save" doesn't save, that's quite serious.

One way to reproduce this bug (on Unix):

Start a new Inkscape document, add something to it and save it.

From a separate command line window, chmod the file so that it is not writable: "chmod -w foo.svg" should do.

In Inkscape add some text that says "spong", thereby changing the document.

Save it. Note that the save fails because the file cannot be written.

In the separate command line window, chmod the file back so it is writable again: "chmod +w foo.svg"

In Inkscape, save the document (without making any changes to it). Note the suspicious lack of anything.

In the separate command line window, verify that the document has not changed. For example, grep it to see if contains the word "spong": grep spong foo.svg

In Inkscape make a trivial change to the document, and undo it. Now save.

Observe that the document really has been saved this time.