brasero crashed with SIGSEGV in brasero_task_ctx_stop_progress()

[Raymond Bakker]

Known issue:

Burning CD stuck at 100% Creating image checksum
https://askubuntu.com/questions/308573/burning-cd-stuck-at-100-creating-image-checksum

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: brasero 3.12.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 28 18:14:40 2016
ExecutablePath: /usr/bin/brasero
InstallationDate: Installed on 2015-01-24 (429 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: brasero /mnt/5cf2c214-25a5-4ecd-8144-8c8f68fdfc68/Files/archive/images/Win10_1511_1_EnglishInternational_x64.iso
SegvAnalysis:
 Segfault happened at: 0x7f8c3e65b6be <brasero_task_ctx_stop_progress+46>: mov 0x50(%rbx),%rdi
 PC (0x7f8c3e65b6be) 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/x86_64-linux-gnu/libbrasero-burn3.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libbrasero-burn3.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libbrasero-burn3.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libbrasero-burn3.so.1
 ?? () from /usr/lib/x86_64-linux-gnu/libbrasero-burn3.so.1
Title: brasero crashed with SIGSEGV in brasero_task_ctx_stop_progress()
UpgradeStatus: Upgraded to xenial on 2016-03-24 (4 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1166540, 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.