Ubuntu
brasero package

brasero crashed with SIGSEGV in brasero_track_data_cfg_add()

Bug #437708 reported by motang
26
This bug affects 4 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

After choosing to burn a disc via the auto prompt Brasero crashed.

ProblemType: Crash
Architecture: amd64
Date: Sun Sep 27 09:31:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 2.28.0-0ubuntu1
ProcCmdline: brasero burn:///
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x7f04d5b11c2a: mov (%rax),%rdi
 PC (0x7f04d5b11c2a) ok
 source "(%rax)" (0x2f6d61726d2f656d) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /usr/lib/libbrasero-burn.so.0
 ?? () from /usr/lib/libbrasero-burn.so.0
 brasero_track_data_cfg_add ()
 ?? ()
 brasero_project_set_data ()
Title: brasero crashed with SIGSEGV in brasero_track_data_cfg_add()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

lp:ubuntu/lucid/brasero
Revision history for this message
motang (mohan-ram) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:brasero_data_project_add_node_real (self=0x283b900,
brasero_data_project_add_loading_node_real (
brasero_track_data_cfg_add (
brasero_data_disc_add_uri (
brasero_project_set_data (project=0x26840e0,

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 the report, it has been sent upstream at : https://bugzilla.gnome.org/show_bug.cgi?id=596625

Changed in brasero (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Triaged
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

This has been fixed upstream now, thanks for reporting.

BTW the fix is available at: http://git.gnome.org/cgit/brasero/commit/?h=gnome-2-28&id=92695b0dbc1f9168252f6c9b15a18bdacb05fdf6 in case that someone wants to test it.

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.28.1-0ubuntu1

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

  * New upstream version:
    Highlights:
    - fix problems with drive/medium management
      (file descriptor leak preventing ejection, improved threading safety)
      (lp: #438065)
    - fix problems with libburn/libisofs
      (rare case data corruption, workaround TAO+dummy problem)
    - some crashes fixed (596625 among others) (lp: #425296, #437708)
    - memory leaks
    Updated translations:

 -- Sebastien Bacher <email address hidden> Mon, 05 Oct 2009 23:59:43 +0200

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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