GNOME Bugzilla – Bug 639190
Transactions corrupted in 2.4.0 from 2.2.9-datafile
Last modified: 2018-06-29 22:51:34 UTC
Created attachment 177998 [details] tar file containing screenshots and data file I have balanced, working transactions in my data file generated w/ 2.2.9. When I open the file in 2.4.0 some transactions that were OK are now unbalanced. Example, from transaction register showing split 1st split line, stockAcct shares=10 Price=1 buy=10 2nd line: fundingAcct sell=100 3rd line: nothing in the Account field, price=1, Buy=90 In addition, I cannot fix the transaction, the Price is always=1. Attached is gc_test_2.2.9.png which shows the transaction register in gc 2.2.9, it's OK. Attached is gc_test_2.4.png, the same data file loaded up in 2.4.0 r200048. I get the same result w/ release from get_deb.net. Attached is the datafile, test2. I'm using ubuntu 10.04
In the log file, opening my test2 file w/ 2.2.9 I get these 4 warnings. * 13:21:44 WARN <gnc.scrub> [xaccTransFindOldCommonCurrency()] unable to find a common currency in txn 90663a5db35b03e597931a3f79c50941, and that is strange. * 13:21:44 WARN <gnc.scrub> [xaccTransScrubCurrency()] no common transaction currency found for trans="REINVESTMENT" (90663a5db35b03e597931a3f79c50941) * 13:21:44 WARN <gnc.scrub> [xaccTransScrubCurrency()] split="" account="FIDELITY EMERGING MARKETS" commodity="FEMKX" * 13:21:44 WARN <gnc.scrub> [xaccTransScrubCurrency()] split="REINVESTMENT" account="cash" commodity="USD" When I open up the file w/ 2.4.0 I get only this warning * 13:24:07 WARN <gnc.engine.scrub> [xaccTransScrubCurrency()] Adjusted split with mismatched values, desc="REINVESTMENT" memo="" old amount 473500/100000 FEMKX, new amount 10639000/100000 When I try to change the price in the split this is the INFO msg from the log. * 13:36:07 INFO <gnc.engine.scrub> [xaccSplitScrub] Adjusted split with mismatched values, desc="REINVESTMENT" memo="" old amount 236750/100000 FEMKX, new amount 473500/100000
My data file (not the test file) had many of these WARN msgs From a search back in the list I found that running 'check & repair' would fix this & it did. Hooray. I can run 2.4.0 now. I think this might have been caused by replaying a log file about a year+ ago. I'll update bugzilla, but I think there is still a bug here. If it was indeed caused by replaying a log file, I think this option should not be available, especially since Derek has stated that it should never be used. Also, even tho the transactions were corrupted w/ 2.2.9, it still held together, but was broken under 2.4.0. The solution might just be a suggestion in the upgrade notes to run 'check & repair'.
Your report has been a while, but I only came across it now. Can you add a link to the relevant thread in the mailing list ? That would be helpful additional information. Note: since you have found a usable workaround, I'll reduce the severity from major to normal. There's no more data loss involved here.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=639190. Please update any external references or bookmarks.