Description of problem: I entered some values for an investment instrument, then a message box popped up letting me know that the values didn't match, and asking whether I wanted to adjust the number of shares, the price, or the dollar amount. I looked more closely and saw that I had typed the decimal point on the dollar amount in the wrong position. I hit the cancel button on the dialog. I was returned to the ledger, in what appeared to be a copy of the last entry. I thought that was strange, but edited the entry to match what I had intended to enter in the first place. Upon trying to finalize the entry, the crash occurred, and the following appeared on the console: gnc.register.ledger:ERROR:split-register.c:1699:gnc_split_register_save: assertion failed: (xaccTransIsOpen(blank_trans)) Version-Release number of selected component: gnucash-2.6.2-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: gnucash crash_function: _g_log_abort executable: /usr/bin/gnucash kernel: 3.13.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at gmessages.c:255 #5 gnc_split_register_save at split-register.c:1699 #6 gnc_split_register_move_cursor at split-register-control.c:447 #7 gnc_table_move_cursor_internal at table-allgui.c:792 #8 gnc_table_move_cursor_gui at table-allgui.c:911 #9 gnc_table_verify_cursor_position at table-allgui.c:939 #10 gnc_table_wrap_verify_cursor_position at table-allgui.c:1002 #11 gnucash_sheet_cursor_move at gnucash-sheet.c:333 #12 gnucash_sheet_key_press_event_internal at gnucash-sheet.c:1863 #13 gnucash_sheet_key_press_event at gnucash-sheet.c:1906
Created attachment 883416 [details] File: backtrace
Created attachment 883417 [details] File: cgroup
Created attachment 883418 [details] File: core_backtrace
Created attachment 883419 [details] File: dso_list
Created attachment 883420 [details] File: environ
Created attachment 883421 [details] File: limits
Created attachment 883422 [details] File: maps
Created attachment 883423 [details] File: open_fds
Created attachment 883424 [details] File: proc_pid_status
Created attachment 883425 [details] File: var_log_messages
I assume the 2.6.3 in updates-testing also crashes?
I don't know. I will install 2.6.3 when I get home tonight and give it a try.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.