On Tue, Jan 12, 2010 at 03:23:32PM +0100, Daniel Leidert wrote: > Am Montag, den 11.01.2010, 14:46 -0800 schrieb Nicholas Breen: > > I've experimented with this bug on a Lenny box, and it does operate without > > crashing when gchempaint versions as low as 0.10.4-1 are backported while > > So you can reproduce the issue? or did you just test with the 0.10 > series?
Yes, it's completely reproducible. > If you can reproduce it and provide a backtrace(?), maybe we can easily > fix it in stable. For the backtrace you only need to install libgcu-dbg. The backtrace is of limited utility, since the failure appears to be occuring in libgconf, which regrettably does not ship a -dbg package. (gdb) run Starting program: /usr/bin/gchempaint (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xa5f95a40 (LWP 18171)] (process:18171): GLib-GObject-CRITICAL **: /build/buildd-glib2.0_2.16.6-2-i386-PgybGk/glib2.0-2.16.6/gobject/gtype.c:2248: initialization assertion failed, use IA__g_type_init() prior to this function (process:18171): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (process:18171): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xa5f95a40 (LWP 18171)] 0xa7318943 in ?? () from /usr/lib/libgconf-2.so.4 (gdb) bt #0 0xa7318943 in ?? () from /usr/lib/libgconf-2.so.4 #1 0xa6c0b81c in ?? () from /usr/lib/libgobject-2.0.so.0 #2 0xa6c0d26c in __PRETTY_FUNCTION__.11002 () from /usr/lib/libgobject-2.0.so.0 #3 0xa6c0c4f6 in ?? () from /usr/lib/libgobject-2.0.so.0 #4 0xa73280d8 in ?? () from /usr/lib/libgconf-2.so.4 #5 0x00000000 in ?? () - Nicholas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
