brasero crashed with SIGSEGV in g_closure_invoke()

[tbds]

Binary package hint: brasero

brasero crashed with SIGSEGV in g_closure_invoke()

ProblemType: Crash
Architecture: amd64
Date: Wed Oct 28 12:55:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 2.28.1-0ubuntu1
ProcCmdline: brasero
ProcEnviron:
 LANGUAGE=nds_DE.UTF-8
 PATH=(custom, user)
 LANG=nds_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-13.45-generic
SegvAnalysis:
 Segfault happened at: 0x42f0d6: mov (%rax),%rdi
 PC (0x0042f0d6) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: brasero crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.28-13-generic x86_64
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:brasero_project_is_valid (session=0x7f1aec0221c0,
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()
g_signal_emit () from /usr/lib/libgobject-2.0.so.0

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually 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.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.