Natty - brasero crashed with SIGSEGV in g_type_instance_get_private()

Bug #756805 reported by CANESIN, F. C.
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: brasero

Look the same of some old bug reports, but this time on natty 11.04 iso from 10/04/2011

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: brasero 2.32.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sun Apr 10 16:26:01 2011
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110408)
ProcCmdline: brasero /home/username/Downloads/natty-desktop-amd64+mac.iso
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6b77e19d01 <g_type_instance_get_private+33>: cmpq $0x0,(%rdi)
 PC (0x7f6b77e19d01) ok
 source "$0x0" ok
 destination "(%rdi)" (0x4da20449) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 g_type_instance_get_private () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 unique_marshal_ENUM__INT_BOXED_UINT () from /usr/lib/libunique-1.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: brasero crashed with SIGSEGV in g_type_instance_get_private()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
CANESIN, F. C. (fc-canesin) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #742930, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
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.