brasero crashed with SIGSEGV in brasero_volume_get_gvolume() after the eject happened while copying an audio disc

[Bruce Dudek]

I was making a copy of an audio disc. The copy process finished and then ejected the disc. The error took place then. The temporary files in /tmp did not get erased.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: brasero 2.32.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 22 21:54:32 2011
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/bin/brasero -c /dev/sr0
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0x7f5066eb5efa: movdqu (%rsi),%xmm2
 PC (0x7f5066eb5efa) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm2" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 brasero_volume_get_gvolume () from /usr/lib/libbrasero-media.so.1
 brasero_volume_get_mount_point () from /usr/lib/libbrasero-media.so.1
 brasero_volume_is_mounted () from /usr/lib/libbrasero-media.so.1
 ?? () from /usr/lib/libbrasero-burn.so.1
Title: brasero crashed with SIGSEGV in brasero_volume_get_gvolume()
UpgradeStatus: Upgraded to natty on 2011-04-29 (115 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

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