kfilemetadatareader crashed with SIGABRT

Bug #1299318 reported by Simon Andric
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

kfilemetadatareader crashed with SIGABRT

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: kdelibs-bin 4:4.12.95-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Mar 29 01:33:07 2014
Disassembly: No symbol "__abort_msg" in current context.
ExecutablePath: /usr/bin/kfilemetadatareader
InstallationDate: Installed on 2013-08-10 (231 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130724)
ProcCmdline: /usr/bin/kfilemetadatareader file:///media/b00x/workshop/videos/torrents_finished/00_bluray/00_bluray_extract/%5BBD.FULL%5D.BATTLESHIP.2012_iso/BDMV/BACKUP/JAR/00000.jar --file
ProcEnviron:
 LANGUAGE=sl:fa:en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=sl_SI.UTF-8
 SHELL=/bin/bash
Registers:
 #0 0x00007f8587a1bf79 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff57885808
Signal: 6
SourcePackage: kde4libs
Stacktrace: No symbol "__nih_abort_msg" in current context.
StacktraceTop:

ThreadStacktrace: No symbol "__glib_assert_msg" in current context.
Title: kfilemetadatareader crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Simon Andric (simonandric5) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f8587a1bf79 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff57885808
StacktraceSource: #0 0x00007f8587a1bf79 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 3347):
 #0 0x00007f8587a1bf79 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff57885808

Changed in kde4libs (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:

outdated debug symbol package for libqt4-dbus: package version 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 dbgsym version 4:4.8.4+dfsg-0ubuntu18.2
libdbusmenu-qt2 version 1:0.9.3+14.04.20140314-0~264+201403171417~ubuntu14.04.1 required, but 0.9.3+14.04.20140314-0ubuntu1 is available
readline-common version 6.3-4ubuntu1 required, but 6.3-4ubuntu2 is available
upower version 0.99.0-1~trusty1 required, but 0.9.23-2ubuntu1 is available
libx11-data version 2:1.6.2+git20131002.18a5278b-0ubuntu0ricotz2 required, but 2:1.6.2-1ubuntu2 is available
libxslt1.1 version 1.1.28-2+13.10~ricotz1 required, but 1.1.28-2build1 is available
libx11-6 version 2:1.6.2+git20131002.18a5278b-0ubuntu0ricotz2 required, but 2:1.6.2-1ubuntu2 is available
package libupower-glib2 does not exist, ignoring
libreadline6 version 6.3-4ubuntu1 required, but 6.3-4ubuntu2 is available
libdrm2 version 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt required, but 2.4.52-1 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.