brasero crashed with SIGSEGV in g_object_ref()

Bug #897647 reported by Shock on 2011-11-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)

Bug Description

I don't know why it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: brasero 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Nov 29 14:16:42 2011
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: brasero
 Segfault happened at: 0x7f9575ef6a41 <g_object_ref+17>: cmpq $0x50,(%rax)
 PC (0x7f9575ef6a41) ok
 source "$0x50" ok
 destination "(%rax)" (0x48241c8b48e7894c) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: brasero
 g_object_ref () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
Title: brasero crashed with SIGSEGV in g_object_ref()
UpgradeStatus: Upgraded to oneiric on 2011-11-22 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Shock (mmiron) wrote :

 g_object_ref (_object=0x7f957745a649) at /build/buildd/glib2.0-2.30.0/./gobject/gobject.c:2648
 brasero_drive_selection_set_current_drive (self=0x32629d0, iter=0x7fff2b60ce40) at brasero-drive-selection.c:119
 brasero_drive_selection_drive_added_cb (monitor=<optimized out>, drive=0x2c41960, self=0x32629d0) at brasero-drive-selection.c:445
 g_closure_invoke (closure=0x30cb0a0, return_value=0x0, n_param_values=2, param_values=0x336a830, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.30.0/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0x2817b80, emission_return=0x0, instance_and_params=0x336a830) at /build/buildd/glib2.0-2.30.0/./gobject/gsignal.c:3272

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 → Critical
status: Unknown → New
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.

Other bug subscribers

Remote bug watches

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