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

Bug #611935 reported by dugurama
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kdebase

oksana byul

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: konqueror 4:4.4.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sat Jul 31 03:07:29 2010
ExecutablePath: /usr/bin/kfmclient
LiveMediaBuild: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: kfmclient openProfile webbrowsing
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7b1d490 <_ZN11QDataStreamrsERi+32>: mov 0x8(%esi),%eax
 PC (0x07b1d490) 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>>()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
dugurama (dugurama) wrote :
Revision history for this message
dugurama (dugurama) wrote :

oksaNA BYUL

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 QDataStream::operator>> (this=0x0, i=@0xbffd067c)
 KMimeTypeFactory (this=0x9fe3270)
 KMimeTypeFactory::self ()
 KMimeType::buildDefaultType ()
 KMimeType::checkEssentialMimeTypes ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kdebase (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
security vulnerability: yes → no
visibility: private → public
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.