brasero crashed with SIGSEGV in g_atomic_int_exchange_and_add()

[Patrick le Roux]

Binary package hint: brasero

Crashed whilst trying to burn an image to disk.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: brasero 2.31.92-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-server 2.6.35.4
Uname: Linux 2.6.35-22-server x86_64
Architecture: amd64
Date: Tue Sep 28 10:23:30 2010
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcCmdline: brasero
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f19ab4dbb72 <g_atomic_int_exchange_and_add+2>: lock xadd %eax,(%rdi)
 PC (0x7f19ab4dbb72) ok
 source "%eax" ok
 destination "(%rdi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 g_atomic_int_exchange_and_add () from /lib/libglib-2.0.so.0
 g_variant_unref () from /lib/libglib-2.0.so.0
 brasero_inhibit_suspend () from /usr/lib/libbrasero-burn.so.1
 ?? () from /usr/lib/libbrasero-burn.so.1
 brasero_burn_record () from /usr/lib/libbrasero-burn.so.1
Title: brasero crashed with SIGSEGV in g_atomic_int_exchange_and_add()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[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.