kmail crashed with SIGSEGV in QString::replace()

Bug #436088 reported by Michael Marley
This bug affects 12 people
Affects Status Importance Assigned to Milestone
kdepim (Ubuntu)

Bug Description

Binary package hint: kdepim

After a recent update, Kmail on Kubuntu Karmic x64 crashes very often when switching to the "Inbox" folder of either of the two Disconnected IMAP accounts I have it configured to check.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 24 14:15:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kmail
NonfreeKernelModules: nvidia
Package: kmail 4:4.3.1-0ubuntu4
ProcCmdline: /usr/bin/kmail -caption KMail
 Segfault happened at: 0x7ffa24fadb5d <_ZN7QString7replaceE5QCharRKS_N2Qt15CaseSensitivityE+29>: mov %si,0x10(%rsp)
 PC (0x7ffa24fadb5d) ok
 source "%si" ok
 destination "0x10(%rsp)" (0x7fff8abdee30) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: kdepim
 QString::replace(QChar, QString const&, Qt::CaseSensitivity) ()
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
Title: kmail crashed with SIGSEGV in QString::replace()
Uname: Linux 2.6.31-zen0 x86_64
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
Michael Marley (mamarley) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:QString::replace (this=0x7fff8abdfeb0, ch=Cannot access memory at address 0x7fff8abdee30
KMFolder::idString (this=<value optimized out>)
KMFolderCachedImap::readConfig (this=0x993ab0)
FolderStorage::countUnread (this=0x7fff8abdfeb0)
KMFolder::updateIndicator (this=0x993790)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdepim (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Andres Freund (andres-anarazel) wrote :

I see the issue as well - directly after startup. No accounts are configured to automatically update -> Its not related to fetching email.

Changed in kdepim (Ubuntu):
status: New → Confirmed
Revision history for this message
desert rover (desertrover) wrote :

Same Issue. Crashes after finishing fetching new mail on startup.

Revision history for this message
Arthur Schiwon (blizzz) wrote :

Same problem on 32Bit system. Startup works, but it crashes when fetching email (no auto-fetching).

Revision history for this message
Michal (mikeos) wrote :

Same issue with kmail on karmic x64, when accessing IMAP folders. Appeared on upgrade to package version *ubuntu4. Downgrading kmail and dependent packages to *ubuntu3 makes it stable again.

dpkg -i libkleo4_4%3a4.3.1-0ubuntu3_amd64.deb libkdepim4_4%3a4.3.1-0ubuntu3_amd64.deb libkontactinterfaces4_4%3a4.3.1-0ubuntu3_amd64.deb libkpgp4_4%3a4.3.1-0ubuntu3_amd64.deb libksieve4_4%3a4.3.1-0ubuntu3_amd64.deb libmimelib4_4%3a4.3.1-0ubuntu3_amd64.deb kmail_4%3a4.3.1-0ubuntu3_amd64.deb

Revision history for this message
Nick Sanders (nicksanders11) wrote :

I can confirm this works on 32bit as well
cd /var/cache/apt/archives/
sudo dpkg -i libkleo4_4%3a4.3.1-0ubuntu3_i386.deb libkdepim4_4%3a4.3.1-0ubuntu3_i386.deb libkontactinterfaces4_4%3a4.3.1-0ubuntu3_i386.deb libkpgp4_4%3a4.3.1-0ubuntu3_i386.deb libksieve4_4%3a4.3.1-0ubuntu3_i386.deb libmimelib4_4%3a4.3.1-0ubuntu3_i386.deb kmail_4%3a4.3.1-0ubuntu3_i386.deb
Fixes the problem for me

Revision history for this message
gurubook (l-sacchi) wrote :

Me too (Karmic 32bit)
downgrade to ububtu3 packages as suggested by mikeos and Nick Sandes made kdepim suite work again..

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kdepim - 4:4.3.1-0ubuntu5

kdepim (4:4.3.1-0ubuntu5) karmic; urgency=low

  * Update kubuntu-message-indicator/ patches from, Closes LP: #436088

 -- Jonathan Riddell <email address hidden> Fri, 25 Sep 2009 16:14:35 +0100

Changed in kdepim (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers