nautilus crashed with SIGSEGV in brasero_burn_session_set_image_output_format()

Bug #448328 reported by Jawher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: brasero

The sequance was :
- I opened the output file dialog
- I double clicked on an exisiting iso file while the format was set on drao
- I was asked if I wanted to change or keep the file extension. I closed this dialog using the cross button
- I then clicked on the format combo to change it

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Oct 10 23:40:22 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: libbrasero-media0 2.28.1-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.41-generic
SegvAnalysis:
 Segfault happened at: 0x4acc3fe: repz cmpsb %es:(%edi),%ds:(%esi)
 PC (0x04acc3fe) ok
 source "%es:(%edi)" (0x0000007b) not located in a known VMA region (needed readable region)!
 destination "%ds:(%esi)" (0x04af4117) in non-writable VMA region: 0x04a86000-0x04b09000 r-xp /usr/lib/libbrasero-burn.so.0.2.0
SegvReason:
 reading NULL VMA
 writing VMA /usr/lib/libbrasero-burn.so.0.2.0
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /usr/lib/libbrasero-burn.so.0
 brasero_burn_session_set_image_output_format ()
 ?? () from /usr/lib/libbrasero-burn.so.0
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in brasero_burn_session_set_image_output_format()
Uname: Linux 2.6.31-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jawher (djo-mos-contact) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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.

Changed in brasero (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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

Changed in brasero (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.