brasero crashed with SIGSEGV in g_type_check_instance_cast()

[roadrunner777]

Binary package hint: brasero

Sorry, I can't back-trace this as no debugging symbols where installed at time of crash. It would be helpful if Devs would make a meta package for daily builds of Ubuntu that install all the debugging symbols. Or redesign the crash reporting application so that upon a crash it asks if you want to download the symbols for a more thorough analysis. This would avoid this circus of bug reporting and general fire hoop jumping.
Don't get me wrong, I loved watching those close all squeeze into a tiny car, it was enjoyable. This is a computer, it should be automated!!! FFS!
Oh wait... this is lin* simplicity isn't an option right?
I will install the symbols and hopefully it will crash again.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/brasero
Package: brasero 0.8.1-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: brasero
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: brasero
StacktraceTop:
 g_type_check_instance_cast ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_cclosure_marshal_VOID__VOID ()
Title: brasero crashed with SIGSEGV in g_type_check_instance_cast()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:g_type_check_instance_cast () from /usr/lib/libgobject-2.0.so.0
list_select_func (selection=0xaaaaaaaa, model=0x0, path=0x98fac80, path_currently_selected=-1221702029,
gtk_file_chooser_default_style_set (widget=0x9b5adc0, previous_style=0xb790fbd0)
shortcuts_add_bookmarks (impl=0x98fb240) at /build/buildd/gtk+2.0-2.13.6/gtk/gtkfilechooserdefault.c:2183
g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0

[Pedro Villavicencio (pedro)]

No need to, the trace is good enough. May you tell us a few steps in order to reproduce the crash? thanks.

[Pedro Villavicencio (pedro)]

I've sent this upstream at: http://bugzilla.gnome.org/show_bug.cgi?id=549355

[Pedro Villavicencio (pedro)]

this is fixed on jaunty.