nautilus crashed with SIGSEGV in g_main_context_dispatch()

Bug #752696 reported by moma on 2011-04-06
This bug affects 6 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)

Bug Description

Binary package hint: brasero


ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: brasero 2.32.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 6 18:45:10 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110402)
ProcCmdline: nautilus
 Segfault happened at: 0x7ff7ad3798f8: andb $0xfe,0x1c(%rax)
 PC (0x7ff7ad3798f8) ok
 source "$0xfe" ok
 destination "0x1c(%rax)" (0x2e706f746b736580) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: brasero
 ?? () from /usr/lib/
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 g_main_loop_run () from /lib/x86_64-linux-gnu/
 gtk_dialog_run () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

moma (osmoma) wrote :

 brasero_io_return_result_idle (callback_data=<value optimized out>) at brasero-io.c:399
 g_main_dispatch (context=0xe13f70) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:2440
 g_main_context_dispatch (context=0xe13f70) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:3013
 g_main_context_iterate (context=0xe13f70, block=<value optimized out>, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:3091
 g_main_loop_run (loop=0x1fd6c50) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:3299

Changed in brasero (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:

Changed in brasero (Ubuntu):
status: New → Triaged
Changed in brasero:
importance: Unknown → Medium
status: Unknown → New
Changed in brasero:
importance: Medium → Critical

I was trying to burn a CD of Natty. I inserted a blank CD, and answered the popup that I wanted to burn a CD. I searched for the iso, copied it to the blank CD, and clicked on 'burn'. It asked if I wanted to burn the contents of the iso or burn it as a file. I answered with 'contents', and it crashed. This was repeatable.

However, if instead I first searched for the iso, right clicked and selected 'Burn with brasero', it worked fine.

Changed in brasero:
status: New → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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