https://bugs.kde.org/show_bug.cgi?id=433816
--- Comment #11 from duncanSF <duncancampb...@gmail.com> --- Thanks for continuing the conversation. I appreciate the back-and-forth. Yes, that directory exists (showing my age, there) and has some lettersoup.kdenlivelettersoup files listed. The extension encodes the path to the project file. Some end in .lock. Most of them are empty. Looking backwards, comparing the stalefiles list with the list of recently touched projects, I find (sorting by date, grouping by name) one written 33 minutes before my most recent save on March 13th (empty), two with a similar name written nine days before that (both empty), and another cluster starting about 8.5 hours after another project's most recent save (small), with members extending forward a few days from there, Feb 24-27th (newest two with content, earlier ones empty). I'm not sure looking backwards is helpful. I'll try looking forward. Watching that directory, I opened the most recently modified project, made a change and waited without saving. Two files were added after the change. Neither is empty. I made a few more changes (adding timeline guides) without saving. The timestamp on one of those non-blank files updates a few seconds after an unsaved change. It's working but the presence of empty files suggests it doesn't always work. (actual recovery not tested today.) In short, "works-for-me," today, but I can prove it doesn't always work-for-me. Maybe there's a period during the update of that file when it's clobbered but not yet rewritten and my crash experiences coincide with that vulnerable point in the sequence. On save, the .lock file was removed and the other new file apparently emptied. Shortly after the next unsaved change the empty file remains and two new files are written. One is empty. After another change, the timestamp on the one not named .lock updates but it's still empty. Okay, that reproduces the empty file situation. Hope this helps. Sorry for being verbose. -- You are receiving this mail because: You are watching all bug changes.
