GNOME Bugzilla – Bug 156141
After crash all my feeds was gone
Last modified: 2005-04-10 20:25:43 UTC
I was running Blam and suddenly my computer started to lag heavily so I had to force shut down with the computer's power button. When I restarted my computer and loaded Blam all my feeds was gone and replaced with the standard feeds that are included by default.
It seems that whenever Blam is forced to exit (killing with -9, killing X server, forcing poweroff) it doesn't save the changes made during that session.
That's OK, ie. that it doesn't save if you do changes and then kill it. However it's not OK that it creates a broken file. It autosaves after a five minutes of inactivity so it won't be all changes done during the entire session. Is this what happened to you? Was this your first session and you had made changes but never quit the application (or left it inactive for more than five minutes?).
No, the strange thing is that it wasn't my first session. I had used Blam for some weeks and then it crashed and broke my feeds. I have tried to crash it again with various methods but then it only deleted the non-saved feeds, it didn't replace everything with the defaults.
I think what happened was that you system went down at the exact wrong time when Blam was in the middle of writing the file. What you say suggest that the collection.xml was removed from your system, otherwise you wouldn't get the default settings. So I guess the old file was removed and before it had time to write the new file the system crashed. Not sure what can be done against that though except for always storing a backup.
any news on this? Shall we close it?
Marking this as duplicate of another bug, it's the same problem. *** This bug has been marked as a duplicate of 157149 ***