kfilemetadatareader crashed with SIGSEGV in KMimeType::comment()

Bug #948990 reported by AlbertH
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
New
Undecided
Unassigned

Bug Description

The crash happened on kde login.
At moment I don't hace more details.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: kdelibs-bin 4:4.8.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94-0ubuntu2
Architecture: amd64
Date: Wed Mar 7 15:11:13 2012
ExecutablePath: /usr/bin/kfilemetadatareader
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120228.1)
ProcCmdline: /usr/bin/kfilemetadatareader file:///home/username/Documenti
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
SegvAnalysis:
 Segfault happened at: 0x7fb863e93381 <_ZNK9KMimeType7commentERK4KUrl+1>: mov 0x10(%rsi),%rsi
 PC (0x7fb863e93381) ok
 source "0x10(%rsi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde4libs
StacktraceTop:
 KMimeType::comment(KUrl const&) const () from /usr/lib/libkdecore.so.5
 Nepomuk::Utils::formatPropertyValue(Nepomuk::Types::Property const&, Nepomuk::Variant const&, QList<Nepomuk::Resource> const&, QFlags<Nepomuk::Utils::PropertyFormatFlag>) () from /usr/lib/libnepomukutils.so.4
 _start ()
Title: kfilemetadatareader crashed with SIGSEGV in KMimeType::comment()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
AlbertH (alberthilbert) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
visibility: private → public
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.