gtkpod crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

[Matteo Settenvini]

Binary package hint: gtkpod-aac

Crashed when I add a large number of tracks (>5000), ~3000 already into the database and quite a lot of dupes.
I've got UTF-8 (japanese, finnish and other enc) filenames, dunno if it's relevant.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gtkpod
Package: gtkpod-aac 0.99.12-1ubuntu1 [modified: usr/bin/gtkpod]
ProcAttrCurrent: unconfined
ProcCmdline: gtkpod
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/lib/colorgcc/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
Signal: 11
SourcePackage: gtkpod-aac
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: gtkpod crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy kmem lpadmin netdev plugdev powerdev pulse-rt sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
g_signal_emit () from /usr/lib/libgobject-2.0.so.0

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. Please install the debug symbol package "libglib2.0-0-dbgsym" or "libglib2.0-0-dbg" and try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Matteo Settenvini (tchernobog)]

Can't reproduce with latest version, maybe it got fixed?

[Jonathan Thomas (echidnaman)]

Feel free to reopen this if the bug reappears, but for now I think we can consider it as fixed.