brasero crashed with SIGSEGV in g_type_instance_get_private()

[Seba78]

Binary package hint: brasero

I burn a DVD iso file a a try to open another burn session simultanously.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: brasero 2.32.0-0ubuntu2.2
ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
Architecture: i386
Date: Sun Apr 17 17:17:06 2011
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: brasero
ProcEnviron:
 LANG=es_UY.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4087f2 <g_type_instance_get_private+34>: mov (%eax),%edx
 PC (0x004087f2) ok
 source "(%eax)" (0x4dab4ac1) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 g_type_instance_get_private (instance=0x4dab4ac1, private_type=157409576) at /build/buildd/glib2.0-2.26.1/gobject/gtype.c:4483
 ?? ()
 unique_marshal_ENUM__INT_BOXED_UINT () from /usr/lib/libunique-1.0.so.0
 g_closure_invoke (closure=0x9748010, return_value=0xbff21e24, n_param_values=4, param_values=0x9748010, invocation_hint=0xbff21e10) at /build/buildd/glib2.0-2.26.1/gobject/gclosure.c:766
 signal_emit_unlocked_R (node=<value optimized out>, detail=<value optimized out>, instance=0x943aac8, emission_return=0xbff21f7c, instance_and_params=0x9748010) at /build/buildd/glib2.0-2.26.1/gobject/gsignal.c:3252
Title: brasero crashed with SIGSEGV in g_type_instance_get_private()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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 #763745, 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.