Bug 101814 - kmail crashes after failing to connect to imap server
Summary: kmail crashes after failing to connect to imap server
Status: RESOLVED DUPLICATE of bug 88949
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 113724 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-18 15:40 UTC by Waldo Bastian
Modified: 2007-09-14 12:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Waldo Bastian 2005-03-18 15:40:29 UTC
Version:            (using KDE KDE 3.4.0)
Installed from:    Compiled From Sources
OS:                Linux

After attempting to connect what was probably the wrong server/port (my fault) I clicked on the red stop sign of the progress bar in the lower-left corner. Somewhat later I got a message box that said that KMail could not connect to the IMAP server. After clicking OK on the message box, kmail crashed.
I suspect that the progressitem that it tries to update had already been deleted.

[KCrash handler]
#3  0x40c53807 in KPIM::ProgressItem::setComplete (this=0x82aa998)
    at qmap.h:722
#4  0x40208039 in KMail::ListJob::slotConnectionResult (this=0x82b7858,
    errorCode=23, errorMsg=@0x818a240) at listjob.cpp:146
#5  0x402080e2 in KMail::ListJob::qt_invoke (this=0x82b7858, _id=4,
    _o=0xbfffe200) at qucom_p.h:388
#6  0x41d37b1b in QObject::activate_signal (this=0x815f488, clist=0x82d1a10,
    o=0xbfffe200) at qobject.cpp:2357
#7  0x402bfe99 in KMail::ImapAccountBase::connectionResult (this=)
    at imapaccountbase.moc:172
#8  0x402c5ca4 in KMail::ImapAccountBase::slotSchedulerSlaveError (
    this=0x815f488, aSlave=0x8339920, errorCode=23, errorMsg=@0x8374b50)
    at imapaccountbase.cpp:505
#9  0x402c5dfd in KMail::ImapAccountBase::qt_invoke (this=0x815f488, _id=8,
    _o=0xbfffe3c0) at qucom_p.h:312
#10 0x402cad3c in KMAcctImap::qt_invoke (this=0x815f488, _id=8, _o=0xbfffe3c0)
    at kmacctimap.moc:103
#11 0x41d37b1b in QObject::activate_signal (this=0x815dd58, clist=0x815d6a8,
    o=0xbfffe3c0) at qobject.cpp:2357
#12 0x4121b3d1 in KIO::Scheduler::slaveError (this=0x815dd58, t0=0x8339920,
    t1=23, t2=@0x82b7a30) at scheduler.moc:153
#13 0x4121c0fe in KIO::Scheduler::slotSlaveError (this=0x815dd58, errorNr=23,
    errorMsg=@0x82b7a30) at scheduler.cpp:789
#14 0x41220b08 in KIO::Scheduler::qt_invoke (this=0x815dd58, _id=7,
    _o=0xbfffe500) at qucom_p.h:388
#15 0x41d37b1b in QObject::activate_signal (this=0x8339920, clist=0x8374768,
    o=0xbfffe500) at qobject.cpp:2357
#16 0x41214c9c in KIO::SlaveInterface::error (this=0x8339920, t0=23,
    t1=@0xbfffe790) at slaveinterface.moc:214
#17 0x41217db1 in KIO::SlaveInterface::dispatch (this=0x8339920, _cmd=102,
    rawdata=@0xbfffe810) at slaveinterface.cpp:280
#18 0x412188fd in KIO::SlaveInterface::dispatch (this=0x8339920)
    at slaveinterface.cpp:173
#19 0x4121068e in KIO::Slave::gotInput (this=0x8339920) at slave.cpp:300
#20 0x41213e0c in KIO::Slave::qt_invoke (this=0x8339920, _id=4, _o=0xbfffe990)
    at slave.moc:113
#21 0x41d37b1b in QObject::activate_signal (this=0x8363ed8, clist=0x8331510,
    o=0xbfffe990) at qobject.cpp:2357
#22 0x41d37e8d in QObject::activate_signal (this=0x8363ed8, signal=2, param=20)
    at qobject.cpp:2450
#23 0x42090bed in QSocketNotifier::activated (this=0x8363ed8, t0=20)
    at moc_qsocketnotifier.cpp:85
#24 0x41d57d70 in QSocketNotifier::event (this=0x8363ed8, e=0xbfffec80)
    at qsocketnotifier.cpp:280
#25 0x41cd4a3f in QApplication::internalNotify (this=0xbfffeff0,
    receiver=0x8363ed8, e=0xbfffec80) at qapplication.cpp:2635
#26 0x41cd3efc in QApplication::notify (this=0xbfffeff0, receiver=0x8363ed8,
    e=0xbfffec80) at qapplication.cpp:2358
#27 0x417fdd3a in KApplication::notify (this=0xbfffeff0, receiver=0x8363ed8,
    event=0xbfffec80) at kapplication.cpp:549
#28 0x41c6a2c9 in QApplication::sendEvent (receiver=0x8363ed8,
    event=0xbfffec80) at qapplication.h:491
#29 0x41cc2d96 in QEventLoop::activateSocketNotifiers (this=0x8096d78)
    at qeventloop_unix.cpp:580
#30 0x41c7c03e in QEventLoop::processEvents (this=0x8096d78, flags=4)
    at qeventloop_x11.cpp:383
#31 0x41ce8ca6 in QEventLoop::enterLoop (this=0x8096d78) at qeventloop.cpp:198
#32 0x41ce8bc2 in QEventLoop::exec (this=0x8096d78) at qeventloop.cpp:145
#33 0x41cd4bbf in QApplication::exec (this=0xbfffeff0) at qapplication.cpp:2758
Comment 1 Carsten Burghardt 2005-05-23 20:47:43 UTC
Can you reproduce that? Do you know what progress you interrupted (folder listing or something)?
Comment 2 Stephan Kulow 2005-10-03 10:20:45 UTC
*** Bug 113724 has been marked as a duplicate of this bug. ***
Comment 3 Andreas Kling 2006-07-31 22:55:46 UTC

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