kfilemetadatareader crashed with SIGSEGV in KMimeType::comment()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kde4libs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
kfilemetadatareader crashed with SIGSEGV in KMimeType:
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kdelibs-bin 4:4.8.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-18-
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Thu Mar 15 18:49:14 2012
ExecutablePath: /usr/bin/
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=de_DE
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb71d9d50 <_ZNK9KMimeType
PC (0xb71d9d50) ok
source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde4libs
StacktraceTop:
KMimeType:
Nepomuk:
_start ()
Title: kfilemetadatareader crashed with SIGSEGV in KMimeType:
UpgradeStatus: Upgraded to precise on 2012-02-13 (30 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
GLib-GObject-
Gdk-WARNING **: XID collision, trouble ahead
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 #948973, 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.