Your message dated Wed, 28 Feb 2007 09:13:45 -0800
with message-id <[EMAIL PROTECTED]>
and subject line [Fwd: Bug#407717: Resolved in 2.0.5-1]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gnucash
Version: 2.0.2-3
When opening an account ledger from the account tree view, gnucash crashes
without further output on the console.
Version 2.0.2 used to crash sometimes (more often than not), 2.0.2-3 crashes
always.
My system is debian-arm on a Sharp Zaurus 3100.
gdb output:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7438)]
0x414ca254 in g_type_check_instance () from /usr/lib/libgobject-2.0.so.0
(gdb) bt
#0 0x414ca254 in g_type_check_instance () from /usr/lib/libgobject-2.0.so.0
#1 0x414c755c in g_signal_handlers_block_matched ()
from /usr/lib/libgobject-2.0.so.0
#2 0x40194920 in gnc_date_cell_new ()
from /usr/lib/gnucash/gnucash/libgncmod-register-gnome.so.0
#3 0x004d3f00 in ?? ()
Cannot access memory at address 0x0
regards
Alan Krempler
--- End Message ---
--- Begin Message ---
Version: 2.0.5-1
--- Begin Message ---
It works fine in version 2.0.5-1.
As for me, the bug can be closed.
Regards
Alan Krempler
--- End Message ---
signature.asc
Description: This is a digitally signed message part
--- End Message ---
