https://bugs.kde.org/show_bug.cgi?id=493665
--- Comment #20 from Piotr Mierzwinski <piotr.mierzwin...@gmail.com> --- (In reply to Waqar Ahmed from comment #18) > Did you check whether kate had opened the needed session, maybe it was some > other session? We save the session every ~5 seconds WHENEVER a new doc is > created or closed so I can't see why its failing. I can see session name in title bar, so I'm sure that Kate opened correct one. I will attach screenshot. Yesterday I did the same what at the day before yesterday, and result was the same - I met "mySession2" as empty. piotr@Dell:~$ cd /home/piotr/.local/share/kate/stash/mySession2.katesession piotr@Dell:~/.local/share/kate/stash/mySession2.katesession$ ll total 28 -rw-rw-r-- 1 piotr piotr 20 wrz 19 02:32 'Document 0' -rw-rw-r-- 1 piotr piotr 152 wrz 19 02:32 'Document 0~' -rw-rw-r-- 1 piotr piotr 306 paź 24 01:56 'Document 2' -rw-rw-r-- 1 piotr piotr 84 paź 24 01:56 'Document 2~' -rw-rw-r-- 1 piotr piotr 59 paź 24 00:37 'Document 3' -rw-rw-r-- 1 piotr piotr 13 paź 24 00:37 'Document 3~' -rw-rw-r-- 1 piotr piotr 122 sie 31 03:41 'Document 4' And again 'Document 2' and 'Document 3' have correct content, only have not been reopened. BTW. Maybe session should be also saved at the moment when Kate is closed manually and when is killed, otherwise something could be lost. > Why this happens now is beyond me atm, can't see why it would fail. Maybe you could add some more debug messages (triggered on some env.variable), or even you could send binary and I could run it and send you such report. -- You are receiving this mail because: You are watching all bug changes.
