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

[Mario Bosco]

Binary package hint: kdebase

Konqueror doesn't start in a normal way: from icon, from the internet applications, from terminal . But if I give sudo konqueror, it start

ProblemType: Crash
Architecture: i386
Date: Sun Nov 1 19:30:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kfmclient
Package: konqueror 4:4.3.2-0ubuntu3
ProcCmdline: kfmclient openProfile webbrowsing
ProcEnviron:
 LANGUAGE=it_IT.UTF-8
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x1965aa0 <_ZN11QDataStreamrsERi+32>: mov 0x8(%esi),%eax
 PC (0x01965aa0) 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-14-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner video
XsessionErrors:
 (gnome-settings-daemon:2349): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2349): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2462): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2443): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #426578, 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.