kfmclient crashed with SIGSEGV in QDataStream::operator>>()

[Dylan Taylor]

Binary package hint: kdebase

Have no idea how this bug occured... :/ Sorry.

ProblemType: Crash
Architecture: i386
Date: Tue Sep 8 21:35:40 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kfmclient
Package: konqueror 4:4.3.1-0ubuntu1
ProcCmdline: kfmclient openProfile webbrowsing
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.30-generic
SegvAnalysis:
 Segfault happened at: 0xc98aa0 <_ZN11QDataStreamrsERi+32>: mov 0x8(%esi),%eax
 PC (0x00c98aa0) ok
 source "0x8(%esi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 QDataStream::operator>>(int&) ()
 KMimeTypeFactory::KMimeTypeFactory() ()
 KMimeTypeFactory::self() () from /usr/lib/libkdecore.so.5
 KMimeType::buildDefaultType() ()
 KMimeType::checkEssentialMimeTypes() ()
Title: kfmclient crashed with SIGSEGV in QDataStream::operator>>()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:QDataStream::operator>> () from /usr/lib/libQtCore.so.4
KMimeTypeFactory (this=0x9287fc8)
KMimeTypeFactory::self ()
KMimeType::buildDefaultType ()
KMimeType::checkEssentialMimeTypes ()

[Jonathan Thomas (echidnaman)]

Err, wrong report. Oops.

[Jonathan Thomas (echidnaman)]

From the looks of it, konqueror crashed. Does this crash happen every time you try to run konqueror?

[Dylan Taylor (dylanmtaylor)]

... Yeah. Just got exact same error when trying to run Konqueror.

[Harald Sitter (apachelogger)]

Hi Dylan!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!