banshee.exe crashed with SIGSEGV in g_datalist_clear()

[mateusz]

Binary package hint: banshee

tak sie dzieje po aktualizacji

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Jun 28 08:28:33 2007
Disassembly: 0xb600bda8:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/banshee/banshee.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: cdrom
Package: banshee 0.12.1+dfsg-3ubuntu2
PackageArchitecture: i386
ProcCmdline: banshee /usr/lib/banshee/banshee.exe --play-enqueued --enqueue
ProcCwd: /home/mateusz
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pl_PL.UTF-8
 LANGUAGE=pl_PL.UTF-8
Signal: 11
SourcePackage: banshee
Stacktrace:
 #0 0xb600bda8 in ?? ()
 #1 0xb7e58408 in g_datalist_clear () from /usr/lib/libglib-2.0.so.0
 #2 0xb6452d58 in ?? () from /usr/lib/libgobject-2.0.so.0
 #3 0x0855ff20 in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 g_datalist_clear () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
Title: banshee.exe crashed with SIGSEGV in g_datalist_clear()
Uname: Linux mateusz-laptop 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev scanner tape video

[Apport retracing service (apport)]

StacktraceTop:?? ()
IA__g_datalist_clear (datalist=0x855ff20) at /build/buildd/glib2.0-2.13.5/glib/gdataset.c:120
g_object_finalize (object=0x855ff18) at /build/buildd/glib2.0-2.13.5/gobject/gobject.c:540
gnome_program_finalize (object=0x855ff18) at gnome-program.c:724
IA__g_object_unref (_object=0x855ff18) at /build/buildd/glib2.0-2.13.5/gobject/gobject.c:1793

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.