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 680036 - Release 2.4.11 Postpone scheduled transaction causes crash
Release 2.4.11 Postpone scheduled transaction causes crash
Status: RESOLVED DUPLICATE of bug 672760
Product: GnuCash
Classification: Other
Component: Scheduled Transactions
2.4.x
Other Windows
: Normal critical
: ---
Assigned To: gnucash-core-maint
gnucash-core-maint
Depends on:
Blocks:
 
 
Reported: 2012-07-16 17:09 UTC by David Carlson
Modified: 2018-06-29 23:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Carlson 2012-07-16 17:09:20 UTC
In Windows 7 with standard data file.

1.  Open program with one or more transactions appearing in the Since last run window with status Reminder.

2.  Change a transaction from Reminder status to Postponed status.  Move highlight to another line.  This seems to be necessary in the Windows OS.

3.  Click on Close program icon in upper right corner.  Choose Save option while closing.

4.  Program crashes.

Trying another sequence:

1.  Open program with one or more transactions appearing in the Since last run window with the status Reminder.

2.  Change a transaction from Reminder status to Postponed status.  Move highlight to another line.

3.  Click File: Save

4.  Click Close Program.  Program closes without incident.

5.  Open Program.  Since Last Run does not appear with the postponed transaction.

6.  Reviewing the transaction with the Scheduled Transaction editor shows that the next instance should have appeared as it is still due less than indicated time into future.


Another sequence which I did not document fully did cause the postponed transaction to be entered withe the previous date rather than the future date.


David C
Comment 1 David Carlson 2012-07-16 17:17:16 UTC
I forgot to mention that in each case I clicked the box to review the created transactions and closed the Since last Run window by clicking OK.
Comment 2 David Carlson 2012-07-16 17:18:21 UTC
That was between steps 2 and 3.
Comment 3 David Carlson 2012-07-16 17:44:07 UTC
Release 2.4.10 also crashes with the first sequence, but with the second sequence re-opening the program correctly triggers the Since Last Run window and correctly shows the postponed status where previously set.  Changing status to To Create and moving the highlight to another line before selecting review created transactions and clicking OK causes the transactions to be created with the correct dates.
Comment 4 Geert Janssens 2015-02-11 10:17:22 UTC
This may be a duplicate of bug 672760 which will be fixed in 2.6.6.

Windowws users could already test this by downloading and installing a recent nightly build from http://code.gnucash.org/builds/win32/maint/

Or if you know how to build gnucash on linux, you can build the maint branch to run the same test.
Comment 5 John Ralls 2015-09-21 22:58:44 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 672760 ***
Comment 6 John Ralls 2017-09-24 22:48:06 UTC
Reassign version to 2.4.x so that individual 2.4 versions can be retired.
Comment 7 John Ralls 2018-06-29 23:09: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=680036. Please update any external references or bookmarks.