Is there a way to repair/reindex the .mny file so the error is corrected? Is there a hidden backup to restore last known good data? Thanks. Reproducible: Didn't try
Oh, dear. There is not likely to be a backup unless you configured them in your settings. I would set that up right now. You don't want to lose what you have. What console output was produced when the crash occured? Was a back-trace produced? Can you run the consistency check, from the Tools menu? In what way are the balances wrong? Can you give an example.
Created attachment 93966 [details] attachment-22605-0.html Thanks for reply but it looks like a total loss of 3 years data. Apparently there is a documents file found but it was re On Aug 9, 2015 6:05 PM, "allan" <agander93@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=351139 > > allan <agander93@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |agander93@gmail.com > > --- Comment #1 from allan <agander93@gmail.com> --- > Oh, dear. There is not likely to be a backup unless you configured them in > your settings. I would set that up right now. You don't want to lose > what you > have. > > What console output was produced when the crash occured? Was a back-trace > produced? > > Can you run the consistency check, from the Tools menu? > > In what way are the balances wrong? Can you give an example. > > -- > You are receiving this mail because: > You reported the bug. >
I think something went wrong with your reply. Your comment ended "...there is a documents file found but it was re". Also, your attachment appears to be an extract from this bug report. I might be inclined to save your file as XML, and open it in Firefox, to see if you can spot anything recent. You don't have an oldish PC that might have anything more recent? Allan
Created attachment 93967 [details] attachment-24142-0.html Sorry. The file size is 40 bytes total. Consistency check was good. For 3 years of data I see it was lost. I already had backups set to 3 but they are all 0 bytes. Time to start again. On Aug 9, 2015 7:32 PM, "allan" <agander93@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=351139 > > --- Comment #3 from allan <agander93@gmail.com> --- > I think something went wrong with your reply. > > Your comment ended "...there is a documents file found but it was re". > > Also, your attachment appears to be an extract from this bug report. > > I might be inclined to save your file as XML, and open it in Firefox, to > see if > you can spot anything recent. > > You don't have an oldish PC that might have anything more recent? > > Allan > > -- > You are receiving this mail because: > You reported the bug. >
I doubt that the crash during reconciliation has an impact on the loss of any data in the file unless you have the autosave option turned on. Is that the case? The backups being of 0 length does not sound right either. Very strange. If you start from scratch, please consider to upgrade KMyMoney to some more recent version (e.g. 4.7.2)
There are some things here that do not make sense. First, you mention a .mny file. KMM uses a .kmy file - if this is just a typo, no problem, but I want to be sure you have the right file. You also mention a documents file was found. Do you mean your data file? Also, you say the file is only 40 bytes, and it passes the consistency check. I do not believe it is possible to have a .kmy file with any data in it that small. Did you mean 40KBytes? Unless you have autosave turned on, KMM only saves the file when you explicitly tell it to, so a crash would leave the file untouched, and only lose what you entered in that session. That could show up as scheduled transactions you entered in that session still needing to be entered. Balances would revert to what they were at the start of the previous session, since nothing would have been saved.
Old version. Very little info. This bug report is near to useless.