[GNC] Canceling QIF Import Erases ALL Transactions

[John Ralls]

> On Mar 21, 2020, at 12:53 AM, Eric H. Bowen via gnucash-user <gnucash-user at gnucash.org> wrote:
> 
> Yesterday I ran into this...I was attempting a .QIF import of transactions from my credit card company. The import seemed to progress normally, up until the "Match Transactions" stage. When it got there, every single one of the transactions which I had entered over the past 2+ years appeared in the list. I hit the cancel button in the requester, got the "busy" icon...and when Gnucash resumed, about ten minutes later, every one of my transactions in every account had vanished (with the sole exceptions of customer invoices and vendor bills)!
> 
> I did have a fairly recent backup file available, so I restored to that and tried the import again. The same thing happened a second time.
> 
> My NAS keeps track of file history and automatically saves the most recent versions every twenty minutes or so, so I do have versions from before and after the failed import saved (to a new file under a new name) as well as all of my log files. At the time of the import I was running Build ID: 3.8b+(2019-12-29) on Ubuntu 18.04.4 LTS in a homebuilt machine with AMD FX-4100 CPU, 8 GB RAM, and an ASUS M5A88-M motherboard and using the SQLite3 backend.
> 
> I opened a Bugzilla account and reported this (Bug 797651), but as reconstructing this may mean sharing my personal financial data I restricted the view access to the developer list. I have reconstructed my working account file from my backup, so there's been no loss of critical data. I'm sharing this for visibility and to ask if there is any additional information I should provide in the bug report to facilitate a permanent resolution to this problem. Thanks for any advice----Eric.

Chris has already responded to you on the bug report and will ask there for any additional information he needs.

A general note: I wouldn't trust the view access settings to protect anything, it's at best security-by-obscurity. If one of us decides he needs to look at your book he'll provide a direct email address to send it to.

Regards,
John Ralls