brasero crashed with SIGSEGV in g_closure_invoke() / while trying to burn an oversized iso on a regular CD
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
brasero (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
As far as I can remember:
I was trying to burn an a 707Mb iso on a 702Mb blank support.
I tried to confirm (maybe I clicked on the wrong button?) Brasero ejected the CD, I closed the tray and make it retry , I clicked cancel, and I landed on the new project page and when I tried to create a new project, it failed.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: brasero 2.32.1-0ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat Oct 15 14:42:56 2011
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: brasero
ProcEnviron:
LANGUAGE=fr_FR:en
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x45272c: mov 0x28(%r12),%rdi
PC (0x0045272c) 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/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: brasero crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare
XsessionErrors:
(brasero:4867): GLib-CRITICAL **: the GVariant format string `(u)' has a type of `(u)' but the given value has a type of `()'
(brasero:4867): GLib-CRITICAL **: g_variant_get: assertion `valid_
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.