brasero crashed with SIGSEGV in g_closure_invoke()

Bug #883394 reported by Gionn
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
New
Undecided
Unassigned

Bug Description

Reproducibile with: burn an ISO, enable simulation, wait simulation complete and ask dialog appear to proceed to burning, click burn, brasero try to eject/inject tray (but this is a laptop), return an error. When I retry to burn (but without simulation) the same iso etc, when I press on burn it crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: brasero 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Sat Oct 29 08:51:24 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: brasero
SegvAnalysis:
 Segfault happened at: 0x45149c: mov 0x28(%r12),%rdi
 PC (0x0045149c) ok
 source "0x28(%r12)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.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
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: brasero crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Gionn (giovanni.toraldo) 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 #857413, 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
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.