Note this is a HUGE SECURITY ISSUE potentially causing DATA LOSS.

I had used gedit to edit several files, then I closed it, and when I attempted to open it again (from the Launcher icon) it start to systematically crash every time I tried.

After a while, Ubuntu's crash report window appeared offering me to report the crash and relaunch Gedit, and for some reason after this it did start.


However, and here comes the huge security issue:
- I wrote some text
- I went to save the file by hitting Ctrl+S

Expected result: should prompt me for where to save the file
Actual result: it didn't prompt me for a location and filename, and it gave me an error message 
"Could not find the file ...."
with the path to a file which actually does exist, unrelated to what I'm editing (I am editing a new file from scratch, and I haven't saved it previously), and it is the path of a random file that I had been editing before closing Gedit before the crashes.
Now the filename displayed on the top of the tab (which is supposed to be the name of the file I am editing, which should be "Untitled") is the name of that file, and I'm not sure if it had been so since the beginning.

So now I've done a Save As, chosen a new path and file name, and saved, and it still gives me the same error message and it hasn't saved the file. Unless it has saved it at a random location.

Overall it is a complete nonsense:
- it didn't prompt me for the path where to save the file.
- the message "could not find file..." when attempting to save doesn't make sense. Is it failing to read or write? 
- Either way it's complaining for a random file that it shouldn't be trying to either read or write at all
- If it is attempting to write (which would be a huge bug, saving to some random file that I have not chosen), complaining about the inability to *find* it doesn't make sense: you either complain that it's parent directory doesn't exist (which is not the case) or that the file cannot be written for whatever reason
- if it is attempting to read it, there's no reason to
- it's complain that the file doesn't exist while indeed it does (which is a fortunate nonsense, because I wonder what it would have done with that random file, overwrite it?)
- it didn't save the file I created, at least not where I told it to save it (the second time with Save As).


It seems pretty clear that, after the crashes, Gedit has started in some corrupted state where critical information is completely messed up (such as the path of the current file being edited). The very fact that the sanity of this information is not checked is can potentially cause disastrous data loss/corruption.