Opening recent file created a strange filename with underscores instead of slashes
For a while I thought I had lost a whole day's work.
After saving, closing and logging out, I logged in again, opened musescore and my piece. The file I thought I had worked on had none of the recent changes. I looked at previous versions in Dropbox, it was as all recent work had never happened.
Thanks to `find -name` in my home, I found something related. It's the filename with full path that I thought I was working on, only all slashes had been replaced by underscores.
It seems that last time I was working on the file, it was actually saving (I save very very often) to another. Instead of working on:
/home/gauthier/arrangering/mypiece.mscz
I was working on:
~/_home_gauthier_arrangering_mypiece.mscz
Ubuntu 15.10, musescore 2.0.2. I couldn't find such a bug in the issue tracker, but am currently not in a position to test with nightly build. I also cannot reproduce the issue, so I didn't put it in the tracker.
At approximately the same time this happened, I switched WM from Unity's to Xmonad. I can't see how that could be related, but I don't remember doing anything else funky. Is this anything known? Does it ring any bell?
Comments
Files with that sort of name are created if there is a crash and MuseScore offers to recover scores the next time it starts. This is so that you don't accidentally overwrite your known good copy with a possibly-good-but-possibly-not recovered file.
That's interesting. So what probably happened is that I had a crash (a logout while musescore is open shouldn't qualify, right?), and at the beginning of my day I opened the recover version without noticing.
Can opening a recovery version go unnoticed? Shouldn't it be made very obvious that it is a recovery version, that you should save somewhere else? Like making it read-only?
In reply to That's interesting. So what by Gauthier Östervall
No, recovering a file after a crash would not go unnoticed - you would have to answer a dialog about whether you wanted to restore the previous session. It *is* of course possible that you answered this and simply forgot, or didn't realize what it was asking.
BTW, logging off your computer while MuseScore is open could indeed count as a crash, if you hadn't saved any open scores, depending on how your OS handles this.