GnuCash
Contact   Instructions
Bug 797351 - General ledger register transaction becomes "zombie" after deletion
Summary: General ledger register transaction becomes "zombie" after deletion
Status: RESOLVED FIXED
Alias: None
Product: GnuCash
Classification: Unclassified
Component: Register (show other bugs)
Version: 3.5
Hardware: PC Linux
: Normal normal
Target Milestone: ---
Assignee: ui
QA Contact: ui
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-17 06:13 EDT by lmat
Modified: 2020-04-25 22:25 EDT (History)
6 users (show)

See Also:


Attachments
Video of erroneous behaviour (232.50 KB, video/x-matroska)
2019-08-17 06:14 EDT, lmat
no flags Details

Description lmat 2019-08-17 06:13:33 EDT
Reproduction instructions:

1. Open General Ledger
2. Enter a transaction with a few splits
3. Select the transaction description
4. Click "Delete" on the toolbar
5. Type a new transaction description
6. Tab away from the description

The erroneous behaviour is that the description will disappear, but it should not. Any information entered into this new "zombie" transaction is sucked into /dev/null.

Closing and re-opening the General Ledger is a workaround.

Here is a video of the behaviour: https://www.youtube.com/watch?v=Kx7LMF-niL4
Comment 1 lmat 2019-08-17 06:14:19 EDT
Created attachment 373357 [details]
Video of erroneous behaviour
Comment 2 lmat 2019-08-17 06:14:55 EDT
I removed the youtube video mentioned in the first comment, but I don't see a way to edit that comment.
Comment 3 Jean Laroche 2020-04-23 00:44:13 EDT
I can repro the behavior, I'll see if I can fix that.
Comment 4 Christopher Lam 2020-04-25 22:03:46 EDT
fixed in maint, please verify next nightly.

https://github.com/Gnucash/gnucash/commit/18a4824bb4af9c0e802770e85e3b05e38c3f2db6
Comment 5 lmat 2020-04-25 22:25:52 EDT
Just reproduced on "Build ID: 3.8b+(2019-12-29)", then built the mentioned commit, 18a4824bb, and verified the fix is good.

My hat is off to Monsieur Jean (and Chris for the comment, and John for his help getting this in the code base).

Note You need to log in before you can comment on or make changes to this bug.