Ubuntu
brasero package

brasero crashed with SIGSEGV in g_closure_invoke()

Bug #410957 reported by ZeroBeat
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Brasero
Fix Released
Critical
brasero (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

I was burning a DVD iso image using the default settings.
The burning went well but in the end, Brasero came up with this error.
By the way, nautilus sometimes also came up with this error.
Best regards
ZB

Description: Ubuntu karmic (development branch)
Release: 9.10
Package: brasero (2.27.5-0ubuntu2) karmic

ProblemType: Crash
Architecture: amd64
Date: Sun Aug 9 09:33:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 2.27.5-0ubuntu2
ProcCmdline: brasero
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x7fab35f38c03: mov 0x10(%rax),%rax
 PC (0x7fab35f38c03) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /usr/lib/libbrasero-burn.so.0
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: brasero crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
ZeroBeat (zerobeat) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:brasero_data_session_disc_removed_cb (monitor=<value optimized out>,
IA__g_closure_invoke (closure=0x94a100,
signal_emit_unlocked_R (node=0x942ba0,
IA__g_signal_emit_valist (instance=0x905280,
IA__g_signal_emit (instance=0x8, signal_id=0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in brasero (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, this is known upstream and already fixed, the fix is included on brasero 2.27.90 which is due to be out soon: http://bugzilla.gnome.org/show_bug.cgi?id=586540

visibility: private → public
Changed in brasero (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in brasero:
status: Unknown → Fix Released
Chris Coulson (chrisccoulson)
Changed in brasero (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package brasero - 2.27.90-0ubuntu1

---------------
brasero (2.27.90-0ubuntu1) karmic; urgency=low

  * New upstream version (LP: #411926):
    - Bug fixing:
    - #590385 – Fails to recognize blank disk media (LP: #405544).
    - #587690 – brasero crashed with SIGSEGV in
      brasero_jacket_edit_freeze() (LP: #392805).
    - #590181 – Use Brasero as desktop file Name
    - #588902 – Port to SessionManager service
    - #589870 – nautilus crashed with SIGSEGV in g_hash_table_lookup()
      (LP: #404367).
    - #579508 – Cover editor: Prepend 0 to track numbers
    - #586540 – crash in Open Folder: nautilus crashes after I...
      (LP: #410957).
  * Refreshed patches:
    - 010_lpi.patch
    - 99_autoconf.patch
  * debian/rules:
    - Update DEB_DH_MAKESHLIBS_ARGS.
  * Also fixes LP: #401488.

 -- Chris Coulson <email address hidden> Thu, 13 Aug 2009 18:16:50 +0100

Changed in brasero (Ubuntu):
status: Fix Committed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in brasero:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.