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 470257 - crash in GnuCash Finance Management: I was in the SLR dialog,...
crash in GnuCash Finance Management: I was in the SLR dialog,...
Status: VERIFIED DUPLICATE of bug 366468
Product: GnuCash
Classification: Other
Component: General
2.0.x
Other All
: High critical
: ---
Assigned To: Andreas Köhler
Andreas Köhler
Depends on:
Blocks:
 
 
Reported: 2007-08-25 18:11 UTC by Chris Shoemaker
Modified: 2018-06-29 21:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Chris Shoemaker 2007-08-25 18:11:01 UTC 
What were you doing when the application crashed?
I was in the SLR dialog, on the Created Transaction Review screen.
In the blank split of the first transaction, I entered a non-existing account name.  The New Account dialog opened, and I accepted the defaults.  Clicking on "Ok" in the New Account dialog triggered the crash.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2962.fc6 #1 SMP Tue Jun 19 18:50:05 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled

Memory status: size: 512913408 vsize: 512913408 resident: 95879168 share: 34316288 rss: 95879168 rss_rlim: -1
CPU usage: start_time: 1188058869 rtime: 8446 utime: 8182 stime: 264 cutime:25 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnucash'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496369152 (LWP 28913)]
0x0000003631c0d9c5 in waitpid () from /lib64/libpthread.so.0

+ Trace 157872

Thread 1 (Thread 46912496369152 (LWP 28913))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #2 <signal handler called>
  • #3 gnc_main_window_disconnect
    at gnc-main-window.c line 1979
  • #4 gnc_main_window_close_page
    at gnc-main-window.c line 2184
  • #5 gppr_account_destroy_cb
    at gnc-plugin-page-register.c line 2837
  • #6 aw_call_destroy_callbacks
    at dialog-account.c line 146
  • #7 gnc_finish_ok
    at dialog-account.c line 315
  • #8 gnc_account_window_response_cb
    at dialog-account.c line 852
  • #9 gnc_ui_new_accounts_from_name_with_defaults
    at dialog-account.c line 1592
  • #10 gnc_split_register_get_account_by_name
    at split-register.c line 1517
  • #11 gnc_split_register_traverse
    at split-register-control.c line 1321
  • #12 gnc_table_traverse_update
    at table-allgui.c line 1781
  • #13 gnucash_sheet_key_press_event
    at gnucash-sheet.c line 1716
  • #14 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #15 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_chain_from_overridden
    from /lib64/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #19 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #20 IA__gtk_window_propagate_key_event
    at gtkwindow.c line 4670
  • #21 gtk_window_key_press_event
    at gtkwindow.c line 4700
  • #22 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #23 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #24 g_signal_chain_from_overridden
    from /lib64/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #27 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #28 IA__gtk_propagate_event
    at gtkmain.c line 2315
  • #29 IA__gtk_main_do_event
    at gtkmain.c line 1575
  • #30 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #31 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #32 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #34 IA__gtk_main
    at gtkmain.c line 1154
  • #35 gnc_ui_start_event_loop
    at gnc-gnome-utils.c line 375
  • #36 inner_main
    at gnucash-bin.c line 479
  • #37 invoke_main_func
    at init.c line 367
  • #38 c_body
    at continuations.c line 366
  • #39 scm_c_catch
    at throw.c line 204
  • #40 scm_i_with_continuation_barrier
    at continuations.c line 342
  • #41 scm_c_with_continuation_barrier
    at continuations.c line 384
  • #42 scm_i_with_guile_and_parent
    at threads.c line 649
  • #43 scm_boot_guile
    at init.c line 350
  • #44 main
    at gnucash-bin.c line 515
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (72621 sec old) ---------------------
(gnome-terminal:3115): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:3115): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:3115): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Window manager warning: last_user_time (32) is greater than comparison timestamp (2473182707).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE
Window manager warning: 0xe0002f (Bottom Pan) appears to be one of the offending windows with a timestamp of 32.  Working around...
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220005b (OpenOffice)
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 0x220005b (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: last_focus_time (2557068273) is greater than comparison timestamp (2557068249).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _N
(gnome-terminal:3115): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
--------------------------------------------------
Comment 1 Chris Shoemaker 2007-08-25 18:14:48 UTC 

*** This bug has been marked as a duplicate of 366468 ***
Comment 2 John Ralls 2018-06-29 21:46:51 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=470257. Please update any external references or bookmarks.