SUMMARY All saved sessions were lost today. One saved session just turned up empty with a few crashes being reported. And all the saved entries in there were gone. Possible causes: 1. There were too many saved entries inside the saved session, in the hundreds 2. Two monitors are being used, so opening kate in the second monitor opens up a new kate instance. 3. External hit ( Technical ) / External hit ( Political ) Possible remediations: Please do see whether the second monitor caused this issue. Or causes these kinds of issues. Please do save the session info in a backup file which can be recovered in case such an issue happens again. To repeat, a Session file with hundreds of entries simply became empty overnight. Thank you and kind regards, Annit Bhattacharya
Sorry that this happened but we can't do much here without a way to reproduce this problem. Also, creating backups is something you need to do yourself.
I can state with 100% probability that immediately after the data loss, I received crashes inside Kate. I did not have a bug account then so could not capture them. The problem is 99% probability to do with 1000s ( thousands ) of entries in the session file. It is 10% probable something to do with two monitors because currently if you open kate in another monitor it opens a new instance of Kate with undetermined behaviour as to which session it opens. Do take a note of this. Also do take a note of the fact that running kate in another monitor when another kate is running in the other monitor results in unexpected behaviour, where if you click close to the 'switch to instance' dialog. And the save session option is too easy to overwrite a session with hundreds of entries with an empty one ( haven't been able to reproduce this ) When opening in another monitor, it should open an empty instance and not open a duplicate session automatically as one can open the session manually if one really wants but having a duplicate window with the same session open is a recipe for confusion. All in all the sessions section needs to be more intuitive and a tilde backup wouldn't go amiss should the crash be the actual cause. Thank you.