Receivables Aging Odd on Customer Report

[Geert Janssens]

On Wednesday 21 January 2015 20:34:41 Liz wrote:
> On Wed, 21 Jan 2015 10:16:24 +0100
> 
> Geert Janssens <geert.gnucash at kobaltwit.be> wrote:
> > Can you run gnucash from gdb and post the stack trace of this crash
> > [1] ?
> 
> had to install gdb to do this ;)
> 
> (gdb) run
> Starting program: /usr/bin/gnucash
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library
> "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1". [New Thread
> 0xb0a34b40 (LWP 4672)] [New Thread 0xb00ffb40 (LWP 4673)]
> Traceback (most recent call last):
>   File "/usr/share/gnucash/python/init.py", line 3, in <module>
>     from gnucash import *
> ImportError: No module named gnucash
> [New Thread 0xaef5db40 (LWP 4681)]
> Found Finance::Quote version 1.35
> [New Thread 0xae50eb40 (LWP 4684)]
> [Thread 0xae50eb40 (LWP 4684) exited]
> [New Thread 0xae50eb40 (LWP 4689)]
> [New Thread 0xada58b40 (LWP 4690)]
> [New Thread 0xa9c2db40 (LWP 4692)]
> [New Thread 0xa942cb40 (LWP 4693)]
> [New Thread 0xa8affb40 (LWP 4694)]
> [New Thread 0xa80ffb40 (LWP 4695)]
> [New Thread 0xa72ffb40 (LWP 4696)]
> [Thread 0xa72ffb40 (LWP 4696) exited]
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0xb7cbd7e7 in gnc_lot_get_account ()
>    from /usr/lib/i386-linux-gnu/gnucash/gnucash/libgncmod-engine.so
> (gdb) bt
> #0  0xb7cbd7e7 in gnc_lot_get_account ()
>    from /usr/lib/i386-linux-gnu/gnucash/gnucash/libgncmod-engine.so
> #1  0xb17c8798 in ?? ()
>    from
> /usr/lib/i386-linux-gnu/gnucash/gnucash/libgncmod-business-gnome.so
> #2  0xb77649aa in gtk_tree_selection_selected_foreach ()
>    from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
> #3  0xb17c9147 in ?? ()
>    from
> /usr/lib/i386-linux-gnu/gnucash/gnucash/libgncmod-business-gnome.so
> #4  0xb17c9b7f in gnc_payment_dialog_document_selection_changed_cb ()
> from
> /usr/lib/i386-linux-gnu/gnucash/gnucash/libgncmod-business-gnome.so
> #5  0xb6e7a4e7 in g_cclosure_marshal_VOID__VOIDv ()
>    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #6  0xb6e78a5f in ?? () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #7  0xb6e927f9 in
> g_signal_emit_valist ()
>    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #8  0xb6e93575 in g_signal_emit_by_name ()
>    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #9  0xb7772888 in ?? () from
> /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 #10 0xb6e7b3fc in
> g_cclosure_marshal_VOID__BOXED ()
>    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #11 0xb6e7883b in g_closure_invoke ()
>    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #12 0xb6e8a855 in ?? () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 #13 0xb6e92eda in
> g_signal_emit_valist ()
> ---Type <return> to continue, or q <return> to quit---
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

Thanks Liz.

The stack trace is truncated and missing debug symbols. It does show 
enough though to make it look like a variation of 
https://bugzilla.gnome.org/show_bug.cgi?id=740471

I had already committed a fix for that bug but it's not released yet. To 
get the fixes you'd need to build the current maint branch or wait for 
gnucash 2.6.6 to be released (currently expected in March 2015).

Out of curiosity: do you see any difference between the failing 
combination and those that work ?
Things like: number of involved items (invoices, credit notes, payments/ 
one payment vs several payments/ one document vs several documents), 
sequence of involved items (invoice older than payment or the other way 
around),...

Geert