brasero crashed with SIGSEGV in g_type_value_table_peek()

Bug #834015 reported by Simon Körner on 2011-08-25
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)

Bug Description

I wanted to burn an ISO to a CD

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: brasero 3.0.0-1ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Aug 25 20:43:49 2011
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
ProcCmdline: brasero /home/username/tmp/remaster-new-files/livecd.iso
 PATH=(custom, no user)
 Segfault happened at: 0x7fddff551119 <g_type_value_table_peek+217>: mov (%rax),%rbx
 PC (0x7fddff551119) ok
 source "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: brasero
 g_type_value_table_peek () from /usr/lib/x86_64-linux-gnu/
 g_value_init () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 brasero_burn_record () from /usr/lib/
Title: brasero crashed with SIGSEGV in g_type_value_table_peek()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Simon Körner (lub) wrote :

 g_type_value_table_peek (type=140591124055200) at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c:4156
 g_value_init (value=0x7fffd54aa420, g_type=140591124055200) at /build/buildd/glib2.0-2.29.16/./gobject/gvalue.c:174
 brasero_burn_emit_eject_failure_signal (drive=0xc4c060, burn=0xd4f040) at brasero-burn.c:362
 brasero_burn_eject (error=<optimized out>, drive=0xc4c060, self=0xd4f040) at brasero-burn.c:436
 brasero_burn_eject (self=0xd4f040, drive=0xc4c060, error=<optimized out>) at brasero-burn.c:384

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

Thanks for the report, i've sent it to

visibility: private → public
Changed in brasero (Ubuntu):
status: New → Triaged
Changed in brasero:
importance: Unknown → Critical
status: Unknown → New
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.