mkvmerge crashed with SIGABRT

Bug #1127199 reported by Daniel Winzen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mkvtoolnix (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

mkvmerge crashed while merging two files, because the disk had no space left and I clicked on cancel.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: mkvtoolnix 6.0.0-1
ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Sat Feb 16 13:39:05 2013
Disassembly: => 0x7fba3b37f037: Cannot access memory at address 0x7fba3b37f037
ExecutablePath: /usr/bin/mkvmerge
InstallationDate: Installed on 2012-04-03 (318 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120403)
MarkForUpload: True
ProcCmdline: mkvmerge @/tmp/mmg-mkvmerge-options-16241-1361018241
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: mkvtoolnix
Stacktrace:
 #0 0x00007fba3b37f037 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffb9db0de8
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 18052):
 #0 0x00007fba3b37f037 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffb9db0de8
Title: mkvmerge crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Daniel Winzen (q-d-deactivatedaccount) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007fba3b37f037 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffb9db0de8
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 18052):
 #0 0x00007fba3b37f037 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fffb9db0de8

Changed in mkvtoolnix (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1 version 1:4.7.2-21ubuntu3 required, but 1:4.7.2-22ubuntu3 is available
libk5crypto3 version 1.10.1+dfsg-3 required, but 1.10.1+dfsg-4 is available
libssl1.0.0 version 1.0.1c-4ubuntu3 required, but 1.0.1c-4ubuntu7 is available
mkvtoolnix version 6.0.0-1 required, but 6.1.0-1 is available
apt-utils version 0.9.7.7ubuntu1 required, but 0.9.7.7ubuntu3 is available
perl-base version 5.14.2-18 required, but 5.14.2-20 is available
libkrb5support0 version 1.10.1+dfsg-3 required, but 1.10.1+dfsg-4 is available
libkrb5-3 version 1.10.1+dfsg-3 required, but 1.10.1+dfsg-4 is available
gcc-4.7-base version 4.7.2-21ubuntu3 required, but 4.7.2-22ubuntu3 is available
libmagic1 version 5.11-2ubuntu1 required, but 5.11-2ubuntu4 is available
krb5-locales version 1.10.1+dfsg-3 required, but 1.10.1+dfsg-4 is available
libstdc++6 version 4.7.2-21ubuntu3 required, but 4.7.2-22ubuntu3 is available
libapt-pkg4.12 version 0.9.7.7ubuntu1 required, but 0.9.7.7ubuntu3 is available
libicu48 version 4.8.1.1-10 required, but 4.8.1.1-10ubuntu1 is available
libgssapi-krb5-2 version 1.10.1+dfsg-3 required, but 1.10.1+dfsg-4 is available
libapt-inst1.5 version 0.9.7.7ubuntu1 required, but 0.9.7.7ubuntu3 is available
openssl version 1.0.1c-4ubuntu3 required, but 1.0.1c-4ubuntu7 is available
libgnutls26 version 2.12.20-2ubuntu1 required, but 2.12.23-1ubuntu1 is available
libdb5.1 version 5.1.29-5ubuntu6 required, but 5.1.29-5ubuntu7 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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