GNOME Bugzilla – Bug 370802
crash in GnuCash Finance Management: Deleting a split
Last modified: 2018-06-29 21:14:59 UTC
What were you doing when the application crashed? Deleting a split Distribution: Fedora Core release 6 (Rawhide) Gnome Release: 2.16.1 2006-10-21 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors (16919 sec old) --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c037cb (2006nov-de) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c01e93 (trapezium-) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c01e93 (trapezium-) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c01e93 (trapezium-) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c01e93 (trapezium-) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4c01e93 (trapezium-) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. closing closing -------------------------------------------------- Memory status: size: 119525376 vsize: 0 resident: 119525376 share: 0 rss: 39858176 rss_rlim: 0 CPU usage: start_time: 1162686675 rtime: 0 utime: 1655 stime: 0 cutime:1628 cstime: 0 timeout: 27 it_real_value: 0 frequency: 7 Backtrace was generated from '/usr/bin/gnucash' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208187184 (LWP 27767)] (no debugging symbols found) 0x00aad402 in __kernel_vsyscall ()
+ Trace 83013
Thread 1 (Thread -1208187184 (LWP 27767))
More details: I started a new transaction for Name Badge Company and got 4 splits from an old transaction: 1) Namebadge for Foo Liability:Namebadges 2) Namebadge for Bar Liability:Namebadges 3) Invoice #NNNNN Assests:Checking Account 4) Namebadges (x2) Income:Namebadges I then proceeded to update (1) from Foo to Joe. Then changed (2) to "jump bar" and the account to Expenses:Miscellaneous, and then changed that cost. This created a new split. I updated the Invoice # in (3) and also changed the cost. Since (1) plus (2) now equalled (3), I tried to delete (4). The values in (4) and the 5th, new, split were equal. When I attempted to delete (4) I got a message something like "You have two views open, close the other before deleting this split". I then selected another transaction, then returned to this transaction and attempted to delete the split again. BOOM!
Thanks for the bug report. 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 361227 ***
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=370802. Please update any external references or bookmarks.