GNOME Bugzilla – Bug 128393
crash when removing empty row in spreadsheet
Last modified: 2018-06-29 20:39:13 UTC
Package: GnuCash Severity: major Version: 1.8.7-4 Synopsis: crash when removing empty row in spreadsheet Bugzilla-Product: GnuCash Bugzilla-Component: User Interface General Description: Description of Problem: it happens that you have four rows for one transaction. You want to empty the account field but instead it crashes. Steps to reproduce the problem: 1. Enter a transaction: transaction_number:description:account:amount from:amount to row#1: NULL:transcation_descr_1:source_account:1000Euro:NULL row#2: NULL:NULL:NULL:NULL:NULL row#3: NULL:transcation_descr_2:target_account:NULL:1000Euro row#4: NULL:NULL:NULL:NULL:NULL then you try to minimise the empty rows by copying the description and the amount to row#2: row#1: NULL:transcation_descr_1:source_account:1000Euro:NULL row#2: NULL:transcation_descr_2:NULL:NULL:1000Euro row#3: NULL:NULL:target_account:NULL:1000Euro row#4: NULL:NULL:NULL:NULL:NULL Either now or when you then empty the field with 1000Euro in row#3 the software crashes. You lose all your data that you have entered so far without saving. Actual Results: Crash. Expected Results: A safe possibility to remove empty rows. How often does this happen? Everytime. I can repeat it. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/guile-1.6' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 6018)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x400cdbb8 in waitpid () from /lib/libpthread.so.0
+ Trace 42251
Thread 1 (Thread 16384 (LWP 6018))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-02 16:24 ------- The original reporter (liste@garrecht.de) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, hampton@employees.org.
The supposed way to handle "empty rows" is that you click on the row, then click on the button "delete" to remove this (empty) transaction. From what I understand in your description, this is not what you tried to do. Copying the description from one "row" into another doesn't "delete" "rows"; instead, a row is only one view of a transaction and either a transaction is created or it is deleted. The user is not supposed to copy fields of a transaction into some other transaction if the other transaction should rather be deleted completely. Did I misunderstand anything here?
*** Bug 125089 has been marked as a duplicate of this bug. ***
*** Bug 122788 has been marked as a duplicate of this bug. ***
Since others have apparently also gotten this bug (using different methods), I'm marking as new, setting priority->high and severity->critical (it's a crasher), setting version->1.8.x, and adding the bugsquad keyword.
I couldn't reproduce this crash with CVS 1.8 branch head. After a while, I did, however, end up with a transaction with four splits, all of whose amounts were zero, and which gnucash was claiming to be unbalanced, and yet it couldn't balance, and thus, wouldn't allow me to leave the transaction. Deleting was the only way out. p.s. the 'transaction unbalanced' dialog options are confusing.
I encountered a bug which may be the same (still here in 1.8.9), in the recurrent transaction module. If i delete completely one of the scheduled transaction lines while in the last window when the transaction is due, guile segfaults. To reproduce it : - Have a recurrent transaction which is due today - When you launch GNUCash, it reminds you about this transaction - You pass two windows (the first where you select the transactions to create, the second named "to create transaction preparation") - At the last window, when you can review the created transaction, delete completelly one of the lines of the transaction (typically double-clic on the description, delete, tab, delete, tab, delete, tab, delete) - When, on the debit column, you press tab again to leave this (now empty) line, guile crashes with a segfault. This bug seems only present in the recurrent transaction window, i wasn't able to reproduce it in the general ledger window.
*** Bug 153310 has been marked as a duplicate of this bug. ***
I don't know when this was fixed, but I can't reproduce this with 1.9.2. The behavior I'm seeing in both 1.8.12 and 1.9.2 is that if you blank out a row, and then leave it, it is immediately deleted.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=128393. Please update any external references or bookmarks.