brasero crashed with SIGSEGV in brasero_task_ctx_stop_progress()

Bug #1166540 reported by userDepth
40
This bug affects 5 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Medium
Unassigned

Bug Description

Brasero doesn't normalize the song from mp3 and when I close it I get this crash. So the way to reproduce this bug is trying to burn a Audio disc from mp3's and exiting while it is stalled.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: brasero 3.6.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Mon Apr 8 19:00:53 2013
ExecutablePath: /usr/bin/brasero
InstallationDate: Installed on 2013-03-29 (10 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
MarkForUpload: True
ProcCmdline: brasero
SegvAnalysis:
 Segfault happened at: 0x7f83fb34a20e <brasero_task_ctx_stop_progress+46>: mov 0x50(%rbx),%rdi
 PC (0x7f83fb34a20e) ok
 source "0x50(%rbx)" (0x00000050) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 brasero_task_ctx_stop_progress () from /usr/lib/libbrasero-burn3.so.1
 ?? () from /usr/lib/libbrasero-burn3.so.1
 ?? () from /usr/lib/libbrasero-burn3.so.1
 ?? () from /usr/lib/libbrasero-burn3.so.1
 ?? () from /usr/lib/libbrasero-burn3.so.1
Title: brasero crashed with SIGSEGV in brasero_task_ctx_stop_progress()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
userDepth (markonuvo) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 brasero_task_ctx_stop_progress (self=0x7f83bc019a30) at burn-task-ctx.c:1025
 brasero_task_run_loop (error=0x7fff0625db88, self=0x7f83bc019a30) at burn-task.c:466
 brasero_task_start_items (self=self@entry=0x7f83bc019a30, error=error@entry=0x7fff0625db88) at burn-task.c:582
 brasero_task_start (self=0x7f83bc019a30, fake=fake@entry=0, error=error@entry=0x7fff0625db88) at burn-task.c:623
 brasero_task_run (self=<optimized out>, error=error@entry=0x7fff0625db88) at burn-task.c:682

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in brasero (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in brasero (Ubuntu):
status: New → Confirmed
Revision history for this message
Michał Sawicz (saviq) wrote :

This same crash caused me to lose "progress" information on my burning process, fortunately growisofs is still running, so it looks like the burn will complete.

tags: added: trusty
Revision history for this message
Giorgio Dramis (jorged) wrote :

Same bug with Ubuntu 14.04 LTS

tags: added: xenial
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers