brasero crashed with SIGSEGV in brasero_track_data_cfg_add()

[ermal lamcaj]

Binary package hint: brasero

replay
---------
(all this was happening in/through nautilus)
1) an iso was copied to the empty cd-rom folder
2) brasero successfully burned the image to cd
3) the iso file showing in the empty cd-rom folder was moved to trash (with shift pressed)
4) the burned cd was taken out
5) navigated to different folder
6) got crash message from/for brasero

end

ProblemType: Crash
Architecture: i386
Date: Sun Oct 4 13:54:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 2.28.0-0ubuntu1
ProcCmdline: brasero burn:///
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-15.49-generic
SegvAnalysis:
 Segfault happened at: 0xb7fc9a65: mov (%eax),%eax
 PC (0xb7fc9a65) ok
 source "(%eax)" (0x0000000f) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /usr/lib/libbrasero-burn.so.0
 ?? () from /usr/lib/libbrasero-burn.so.0
 brasero_track_data_cfg_add ()
 ?? ()
 brasero_project_set_data ()
Title: brasero crashed with SIGSEGV in brasero_track_data_cfg_add()
Uname: Linux 2.6.28-15-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:2378): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2423): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2399): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #437708, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.