brasero crashed with SIGSEGV in strcmp()

[Oded Arbel]

Binary package hint: brasero

Brasero crashed after the following process:
1. Started brasero with an empty DVD in the drive.
2. Selected new data project
3. Added some files.
4. Brasero showed that it will burn to empty DVD that has 3.9GB more free space
5. Extracted DVD
6. Put in an empty CD
7. Brasero display did not update
8. Opened brasero target selector that offered the following options: empty line with a DVD icon that is currently selected, "image" and "empty CD".
9. chosen the empty CD option.
Brasero then froze for about half a minute and the crashed.

ProblemType: Crash
Architecture: amd64
Date: Fri Oct 2 20:44:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
Package: brasero 2.28.0-0ubuntu1
ProcCmdline: brasero
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x7fcef4bdfe22 <strcmp+2>: cmp (%rsi),%al
 PC (0x7fcef4bdfe22) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 strcmp () from /lib/libc.so.6
 brasero_volume_get_gvolume ()
 brasero_volume_get_name ()
 ?? () from /usr/lib/libbrasero-burn.so.0
 ?? () from /usr/lib/libbrasero-media.so.0
Title: brasero crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare vboxusers video

[Apport retracing service (apport)]

StacktraceTop:strcmp () at ../sysdeps/x86_64/strcmp.S:30
brasero_volume_get_type () at brasero-volume.c:54
?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file 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!.