After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 589954 - With MySQL backend, can't create new transactions in register after creating new account
With MySQL backend, can't create new transactions in register after creating ...
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: Register
2.3.x
Other Linux
: Low normal
: ---
Assigned To: David Hampton
Chris Shoemaker
: 611347 611729 631830 632106 (view as bug list)
Depends on:
Blocks: 611347
 
 
Reported: 2009-07-28 03:57 UTC by Bill Skellenger
Modified: 2018-06-29 22:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bill Skellenger 2009-07-28 03:57:07 UTC 
I have had this happen to me twice now in gnucash-2.3.3.  Basically while you are entering a transaction with the MySQL backend, you may get a notice that the account does not exist, would you like to create it?

If you answer yes, and legitimately create a new account, and then return to the register, you can no longer enter new transactions.

If you answer yes, and then hit cancel on the account creation dialog, you will return to the register where you can no longer enter new transactions.

Can anyone confirm this behavior?
Comment 1 Phil Longstaff 2009-09-07 20:54:09 UTC 
I just saw this too.  If you create a transaction, and while doing this, enter a new account name and create the account, the blank transaction does seem to disappear.  I closed the register and opened it again, and the blank transaction was back.  It appeared as though the transaction was saved properly, so I'm lowering this to lower priority.
Comment 2 Bill Skellenger 2010-01-21 03:04:51 UTC 
I am not sure this is limited to the MySQL backend.  I have moved back to the xml file format and I just had this happen again, (GC 2.3.7).  However, I did not really experiment with it this time...  As soon as it seemed like I could no longer new transactions I closed the account and reopened it.  This solved the problem.
Comment 3 Phil Longstaff 2010-05-16 20:54:43 UTC 
*** Bug 611729 has been marked as a duplicate of this bug. ***
Comment 4 Geert Janssens 2010-10-14 09:59:20 UTC 
@Whoever will fix this bug:
I'm not marking bug 611347 as a duplicate just yet. It describes this issue as well though, but it describes even more symptoms that may or may not be caused by the same bug. When fixing this bug, please also check if the fix cures all symptoms of bug 611347. If so that bug can be marked as a duplicate, instead of being blocked by this one.
Comment 5 Geert Janssens 2010-10-14 10:00:37 UTC 
*** Bug 631830 has been marked as a duplicate of this bug. ***
Comment 6 Geert Janssens 2010-10-14 10:01:44 UTC 
*** Bug 632106 has been marked as a duplicate of this bug. ***
Comment 7 John Ralls 2010-11-16 22:20:31 UTC 
This and 611347 look the same to me, too. I'm struggling with understanding the rather convoluted save process in the register.
Comment 8 John Ralls 2010-11-19 22:23:05 UTC 
Fixed, in r19847.
Comment 9 John Ralls 2010-11-19 22:23:38 UTC 
*** Bug 611347 has been marked as a duplicate of this bug. ***
Comment 10 John Ralls 2018-06-29 22:25:32 UTC 
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=589954. Please update any external references or bookmarks.