brasero crashed with SIGSEGV in g_type_check_instance_is_a()

Bug #595084 reported by Linus Hoppe on 2010-06-16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)

Bug Description

Binary package hint: brasero

Brasero crashed after succesfully burning a cd when trying to close the program.

ProblemType: Crash
Architecture: i386
Date: Sat Jun 12 23:43:42 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: fglrx wl
Package: brasero 2.28.2-0ubuntu1
ProcCmdline: brasero
ProcVersionSignature: Ubuntu 2.6.31-22.60-generic
 Segfault happened at: 0x656803 <g_type_check_instance_is_a+83>: testb $0x40,0x7(%edi)
 PC (0x00656803) ok
 source "$0x40" ok
 destination "0x7(%edi)" (0x6373654b) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: brasero
 g_type_check_instance_is_a ()
 brasero_session_span_get_max_space ()
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/
Title: brasero crashed with SIGSEGV in g_type_check_instance_is_a()
Uname: Linux 2.6.31-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

visibility: private → public

Reported bug Upstream.

Changed in brasero:
importance: Undecided → Unknown
status: New → Unknown
Changed in brasero:
status: Unknown → Incomplete
Pedro Villavicencio (pedro) wrote :

we need a backtrace, let's wait for the apport retracer to pick it up.

Changed in brasero (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete

StacktraceTop:g_type_check_instance_is_a ()
brasero_session_span_get_max_space (session=0xa09e9f8)
brasero_project_is_valid (session=0xa09e9f8,
g_cclosure_marshal_VOID__VOID ()
g_closure_invoke () from /usr/lib/

tags: removed: need-i386-retrace
Changed in brasero:
status: Incomplete → New
Changed in brasero (Ubuntu):
status: Incomplete → Triaged
Changed in brasero:
importance: Unknown → Critical
Changed in brasero:
status: New → Incomplete
Changed in brasero:
status: Incomplete → 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.