Hello,

I've been dealing with a small annoyance when opening files with Krita, and I guess it's about time I said something about it.

When starting a new session of Krita, the first file I open is immediately marked as modified (asterisk in titlebar, asks to save when closing, the whole deal). This isn't a huge problem, but it kinda gives me as a user a weird, unsettling feeling that something was/wasn't saved, even though I know no actual modifications were made to the file. I haven't known this to cause any actual problems when saving the file.

I haven't opened a bug report because I'm uncertain whether this is a problem with Krita itself or with how I set it up in my system (appimage with custom menu launcher, Linux Mint 18.2). I also haven't found any other information about it, so I hope I'm not repeating something that someone else has already said, but I'm sorry if I am.

-Amir

This is already changed in 4.0, it's now [unsaved] for new documents and [modified] for existing ones with modifications.

TheraHedwig wrote:This is already changed in 4.0, it's now [unsaved] for new documents and [modified] for existing ones with modifications.

That's a fine change, but what I mean to say is that an existing file that I open is marked as modified immediately after opening, without any modifications actually existing.

We overhauled saving massively, it doesn't happen in 4.0, but I wouldn't be able to tell you why it happens on your device either.

TheraHedwig wrote:We overhauled saving massively, it doesn't happen in 4.0, but I wouldn't be able to tell you why it happens on your device either.

I see. I'll wait for 4.0 then. Thanks.