Bug 130844

Summary: kmail crash while I am reading my emails
Product: [Applications] kmail Reporter: Mathieu Jobin <opensource>
Component: IMAPAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kavol, michal
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Mathieu Jobin 2006-07-15 02:13:58 UTC
Version:           1.9.3 (using KDE 3.5.3, Gentoo)
Compiler:          gcc version 3.3.6 (Gentoo 3.3.6-r1, ssp-3.3.6-1.0, pie-8.7.8)
OS:                Linux (i686) release 2.6.16-suspend2-r5-justbudget

did anyone noticed kmail became very unstable since 3.4.0? if not, maybe it just don't like the fact I have 4 dIMAP and 3 IMAP account ???

anyway, it crashed (again)
I hope the stack trace will be usefull.
sorry to be a little bit sarcastic. but kmail used to be my favorite mail client (since KDE 1.0) and actually i dont like any other email client. and I am very sad I cannot use it anymore.

System configuration startup check disabled.

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 10175)]
[New Thread 32769 (LWP 10176)]
[New Thread 16386 (LWP 10177)]
[New Thread 32771 (LWP 10178)]
[New Thread 49156 (LWP 10179)]
[New Thread 65541 (LWP 10180)]
[KCrash handler]
#7  0x0898cebf in ?? ()
#8  0xb7c0dc3e in KMMessage::fromDwString (this=0x8a12c50, str=@0xb551facc, 
    aSetStatus=false) at kmmessage.cpp:411
#9  0xb7d667d8 in KMFolderMbox::readMsg (this=0x82cad20, idx=76)
    at kmfoldermbox.cpp:801
#10 0xb7ceb2c3 in FolderStorage::getMsg (this=0x82cad20, idx=76)
    at folderstorage.cpp:475
#11 0xb7d695dd in KMFolderImap::getMsg (this=0x82cad20, idx=76)
    at kmfolderimap.cpp:153
#12 0xb7cd147e in KMFolder::getMsg (this=0xb62481e8, idx=-1252918580)
    at kmfolder.cpp:310
#13 0xb7ce5062 in KMReaderWin::message (this=0x821a8a0, aFolder=0x0)
    at kmreaderwin.cpp:2332
#14 0xb7e668d0 in (anonymous namespace)::AttachmentURLHandler::statusBarMessage (this=0x85fde60, url=@0xbffae450, w=0x821a8a0) at urlhandlermanager.cpp:490
#15 0xb7e65b29 in KMail::URLHandlerManager::statusBarMessage (this=0x81ebe78, 
    url=@0xbffae450, w=0x821a8a0) at urlhandlermanager.cpp:312
#16 0xb7ce2201 in KMReaderWin::slotUrlOn (this=0x821a8a0, aUrl=@0x85bebc8)
    at kmreaderwin.cpp:1848
#17 0xb7ce603e in KMReaderWin::qt_invoke (this=0x821a8a0, _id=57, 
    _o=0xbffae5c0) at kmreaderwin.moc:290
#18 0xb5c2dfac in QObject::activate_signal (this=0x83cef48, clist=0x840d0e0, 
    o=0xbffae5c0) at qobject.cpp:2356
#19 0xb5c2e86e in QObject::activate_signal (this=0x83cef48, signal=8, param=
      {static null = {static null = <same as static member of an already seen type>, d = 0x804fe00, static shared_null = 0x804fe00}, d = 0x8952690, static shared_null = 0x804fe00}) at qobject.cpp:2451
#20 0xb779159f in KHTMLPart::onURL (this=0xb551facc, t0=@0xb551facc)
    at khtml_part.moc:410
#21 0xb777e190 in KHTMLPart::overURL (this=0x83cef48, url=@0x83f293c, 
    target=@0xbffaee80) at khtml_part.cpp:3716
#22 0xb778c96b in KHTMLPart::khtmlMouseMoveEvent (this=0x83cef48, event=0x0)
    at khtml_part.cpp:6464
#23 0xb778af64 in KHTMLPart::customEvent (this=0x83cef48, event=0xbffaf390)
    at khtml_part.cpp:5936
#24 0xb5c2b222 in QObject::event (this=0x83cef48, e=0xbffaf390)
    at qobject.cpp:755
#25 0xb5bbd28f in QApplication::internalNotify (this=0xbffb0090, 
    receiver=0x83cef48, e=0xbffaf390) at qapplication.cpp:2635
#26 0xb5bbc4d1 in QApplication::notify (this=0xbffb0090, receiver=0x83cef48, 
    e=0xbffaf390) at qapplication.cpp:2358
#27 0xb6430e3f in KApplication::notify (this=0xbffb0090, receiver=0x83cef48, 
    event=0xbffaf390) at kapplication.cpp:550
#28 0xb7768a1f in QApplication::sendEvent (receiver=0xb551facc, event=0x28)
    at qapplication.h:496
#29 0xb77513b5 in KHTMLView::viewportMouseMoveEvent (this=0x83ec8e8, 
    _mouse=0xbffafb10) at khtmlview.cpp:1257
#30 0xb5d7d81b in QScrollView::eventFilter (this=0x83ec8e8, obj=0x83f0fc0, 
    e=0xbffafb10) at qscrollview.cpp:1511
#31 0xb775394b in KHTMLView::eventFilter (this=0x83ec8e8, o=0x83f0fc0, 
    e=0xbffafb10) at khtmlview.cpp:1977
#32 0xb5c2b2d6 in QObject::activate_filters (this=0x83f0fc0, e=0xbffafb10)
    at qobject.cpp:903
#33 0xb5c2b153 in QObject::event (this=0x83f0fc0, e=0xbffafb10)
    at qobject.cpp:735
#34 0xb5c710d7 in QWidget::event (this=0x83f0fc0, e=0xbffafb10)
    at qwidget.cpp:4659
#35 0xb5bbd28f in QApplication::internalNotify (this=0xbffb0090, 
    receiver=0x83f0fc0, e=0xbffafb10) at qapplication.cpp:2635
#36 0xb5bbc7c1 in QApplication::notify (this=0xbffb0090, receiver=0x83f0fc0, 
    e=0xbffafb10) at qapplication.cpp:2421
#37 0xb6430e3f in KApplication::notify (this=0xbffb0090, receiver=0x83f0fc0, 
    event=0xbffafb10) at kapplication.cpp:550
#38 0xb5b44748 in QApplication::sendSpontaneousEvent (receiver=0x83f0fc0, 
    event=0xbffafb10) at qapplication.h:499
#39 0xb5b3c48a in QETWidget::translateMouseEvent (this=0x83f0fc0, 
    event=0xbffafed0) at qapplication_x11.cpp:4296
#40 0xb5b39d52 in QApplication::x11ProcessEvent (this=0xbffb0090, 
    event=0xbffafed0) at qapplication_x11.cpp:3447
#41 0xb5b57e19 in QEventLoop::processEvents (this=0x8130580, flags=4)
    at qeventloop_x11.cpp:192
#42 0xb5bd47f9 in QEventLoop::enterLoop (this=0x8130580) at qeventloop.cpp:198
#43 0xb5bd4712 in QEventLoop::exec (this=0x8130580) at qeventloop.cpp:145
#44 0xb5bbd431 in QApplication::exec (this=0xbffb0090)
    at qapplication.cpp:2758
#45 0x0804aa4b in main (argc=-1252918580, argv=0xb551facc) at main.cpp:110
Comment 1 kavol 2006-08-31 12:00:46 UTC
> did anyone noticed kmail became very unstable since 3.4.0?

no, I did not notice because kmail was always VERY unstable with IMAP :-(

I just experienced another crash; doing bugzilla search for duplicates, and I am not sure where to put my comments since there are tons of crash reports :-(
Comment 2 Mathieu Jobin 2006-08-31 13:47:49 UTC
I have been using kmail since 1.0, and IMAP intensively from 3.1 until 3.4 and it was very stable, from 3.4 it became unusable for some reasons. I just stopped using it entirely, its not the workaround I'm the most happy with. but ....

Comment 3 Tommi Tervo 2006-09-14 09:36:19 UTC
*** Bug 134053 has been marked as a duplicate of this bug. ***
Comment 4 Stefan Monov 2007-02-06 01:10:14 UTC
*** Bug 140928 has been marked as a duplicate of this bug. ***
Comment 5 Ronny Standtke 2007-05-21 16:14:03 UTC
I just wanted to add that I just had the same crash with KDE-3.5.5 (Debian testing).
One (maybe) interesting side note: my incoming folder showed one unread mail but I could not see any unread message in the list. So I wanted to select the first message and search for the next unread message. After clicking on the first message kmail crashed...
Comment 6 Thomas McGuire 2007-11-02 19:59:06 UTC
From the backtrace, it looks like this probably is the same as bug 128357.

*** This bug has been marked as a duplicate of 128357 ***