GNOME Bugzilla – Bug 393383
Can't enter transactions after trying to remove transaction splits.
Last modified: 2018-06-29 21:21:27 UTC
Please describe the problem: Start entering new transaction. Auto-complete brings up a previous one, which has splits. Attempt to remove transaction splits. Get message "This transaction is already being edited in another register. Please finish editing it there first." After that, I can't enter the transaction or cancel it. The only way to enter new transactions is to exit GnuCash completely and start it again. Also, no other register is open, so the message seems inaccurate. Steps to reproduce: Please see steps above. This happens every time. Actual results: Please see problem description. Expected results: Please see problem description. Does this happen every time? yes Other information: OS is SuSE Linux 10.2 I have used GnuCash for several years, and the file I'm using was created/updated by previous versions.
I'm unable to reproduce with SVN. Are you able to repro with either 2.0.5 or 2.1.x? How are you invoking "Remove Transaction Splits"?
1. What is SVN? 2. I will upgrade from 2.0.2 and try again, then let you know. 3. How invoking: Transaction (from pulldown menu at top), then Remove Transaction Splits. Thanks for your help.
SVN is just another word for "the very latest development version", currently 2.1.1. We'd like to hear about whether this still exists in any newer version. Thanks a lot.
Trying to install 2.0.5 from source tarball. Satisfied some dependencies but now am stuck on g-wrap. Message from configure says: g-wrap does not appear to be installed correctly, or is not new enough. GnuCash requires at least version 1.3.3 to build, and 1.9.6 to build cleanly with GCC4. I run OpenSuSE 10.2, and rpm says: g-wrap-1.9.6-34 Looks like 2.1.1 doesn't use g-wrap, but is 2.1.1 stable? The problem I have with split transactions in 2.0.2 is easy to circumvent. Maybe I should stick with 2.0.2 until I install the next OpenSuSE release.
I can reproduce this problem in trunk. Here are the steps: 1. Open a register in transaction journal mode 2. Use the tab key to reach the Description field. 3. Type the first few letters of a description that already exists. The field fills with a previously entered description. Do NOT leave the description field. 4. Right-click the description field and click "Remove Transaction Splits" 5. A dialog box pops up. Click "Remove Splits". 6. A message box appears: "This transaction is already being edited in another register. Please finish editing it there first." Click OK. 7. Now you will be unable to enter new transactions even if you close the register and reopen it.
I have committed r17623 in trunk which will not get rid of the message box but does allow you to continue entering new transactions. The fact that the message box appears at all is still a bug. Also note that bug 426111 is probably related to this one (similar underlying cause).
I have just committed r17628, which prevents the message box from appearing. In combination with r17623, this fixes this bug and bug 426111. I'm not sure when these changes will get backported though, as changes to register code is particularly danger prone. So these changes may need to sit in trunk for a while until is seems likely that nothing else is mistakenly broken.
An update: r17628 fixes this bug but does *not* fix bug 426111 (because it is now known to be a completely separate problem.)
Changing target milestone to 2.3.x and marking as fixed by r17623 & r17628. This fix is unlikely to be backported for 2.2.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=393383. Please update any external references or bookmarks.