kmail crashed with SIGSEGV in KMKernel::findFolderById()

Bug #435711 reported by Jo
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdepim (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kdepim

In karmic after update yesterdy kontact and kmail don't start anymore.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Sep 24 09:55:33 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kmail
Package: kmail 4:4.3.1-0ubuntu3
ProcCmdline: /usr/bin/kmail -caption KMail
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SegvAnalysis:
 Segfault happened at: 0x111fa12: mov 0x18(%eax),%edx
 PC (0x0111fa12) ok
 source "0x18(%eax)" (0x00000024) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdepim
StacktraceTop:
 ?? () from /usr/lib/libkmailprivate.so.4
 KMKernel::findFolderById(QString const&) ()
 ?? () from /usr/lib/libkmailprivate.so.4
 ?? () from /usr/lib/libkmailprivate.so.4
 ?? () from /usr/lib/libkmailprivate.so.4
Title: kmail crashed with SIGSEGV in KMKernel::findFolderById()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare vboxusers

Revision history for this message
Jo (16303-gmx) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:KMFolderMgr::findIdString (this=0x0, folderId=@0xbff92674,
KMKernel::findFolderById (this=0xbff92f5c,
KMSearch::read (this=0x8eb3648, location=@0xbff926dc)
KMFolderSearch::readSearch (this=0x8eb2db8)
KMFolderSearch::open (this=0x8eb2db8)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdepim (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
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.