Bug 123948 - kmail crash while mail receiving when modem connection broke down
Summary: kmail crash while mail receiving when modem connection broke down
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: disconnected IMAP (show other bugs)
Version: 1.9.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 106317 142639 145637 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-03-19 23:34 UTC by m.wege
Modified: 2009-12-25 19:09 UTC (History)
3 users (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 m.wege 2006-03-19 23:34:35 UTC
Version:           1.9.1 (using KDE 3.5.1, Debian Package 4:3.5.1-4 (testing/unstable))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15.6-kanotix-1

this crash happened while I was not actively working on the computer. The modem connection broke down while kmail was receiving mails (cached imap).

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1248765408 (LWP 2473)]
[New Thread -1280496720 (LWP 2600)]
[New Thread -1272108112 (LWP 2599)]
[New Thread -1263719504 (LWP 2598)]
[New Thread -1255330896 (LWP 2597)]
[KCrash handler]
#5  0xb7041e3a in QShared::ref () from /usr/lib/libqt-mt.so.3
#6  0xb74322fb in QString::QString () from /usr/lib/libqt-mt.so.3
#7  0xb744dc0c in QUType_QString::set () from /usr/lib/libqt-mt.so.3
#8  0xb7d55ef7 in KMail::ImapAccountBase::imapStatusChanged (this=0x834e808, 
    t0=0x41333d65, t1=@0x41333d65, t2=false) at imapaccountbase.moc:225
#9  0xb7d59d81 in KMail::ImapAccountBase::slotSetStatusResult (
    this=0x834e808, job=0x97c82a0)
    at /tmp/buildd/kdepim-3.5.1/build-tree/kdepim-3.5.1/kmail/imapaccountbase.cpp:1149
#10 0xb7d5ee38 in KMail::ImapAccountBase::qt_invoke (this=0x834e808, _id=10, 
    _o=0xbfdcf3c4) at imapaccountbase.moc:285
#11 0xb7d681a7 in KMAcctCachedImap::qt_invoke (this=0x834e808, _id=10, 
    _o=0xbfdcf3c4) at kmacctcachedimap.moc:97
#12 0xb711b7ff in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#13 0xb5b50212 in KIO::Job::result (this=0x97c82a0, t0=0x41333d65)
    at jobclasses.moc:162
#14 0xb5ba416c in KIO::Job::emitResult (this=0x97c82a0) at job.cpp:222
#15 0xb5ba42de in KIO::SimpleJob::slotFinished (this=0x97c82a0) at job.cpp:570
#16 0xb5b6b4f3 in KIO::SimpleJob::slotError (this=0x97c82a0, 
    error=1093877093, errorText=@0x41333d65) at job.cpp:581
#17 0xb5ba5ef3 in KIO::SimpleJob::qt_invoke (this=0x97c82a0, _id=14, 
    _o=0xbfdcf5e0) at jobclasses.moc:424
#18 0xb711b92c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#19 0xb5b4f1cf in KIO::SlaveInterface::error (this=0x967d8d8, t0=1093877093, 
    t1=@0x41333d65) at slaveinterface.moc:214
#20 0xb5bbe580 in KIO::SlaveInterface::dispatch (this=0x967d8d8, _cmd=102, 
    rawdata=@0xbfdcf7f0) at slaveinterface.cpp:280
#21 0xb5b636b7 in KIO::SlaveInterface::dispatch (this=0x967d8d8)
    at slaveinterface.cpp:173
#22 0xb5b682ab in KIO::Slave::gotInput (this=0x967d8d8) at slave.cpp:300
#23 0xb5b6845b in KIO::Slave::qt_invoke (this=0x967d8d8, _id=4, _o=0xbfdcf918)
    at slave.moc:113
#24 0xb711b7ff in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#25 0xb711c106 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#26 0xb74aa1f7 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#27 0xb713baaa in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#28 0xb70b2122 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#29 0xb70b2314 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#30 0xb77b5d4e in KApplication::notify (this=0xbfdcfef8, receiver=0x98ee618, 
    event=0xbfdcfc70) at kapplication.cpp:550
#31 0xb7043861 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#32 0xb70a3cdd in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#33 0xb7057542 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#34 0xb70cab01 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#35 0xb70caa26 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#36 0xb70b0c35 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#37 0x0804a098 in main (argc=1093877093, argv=0x41333d65)
    at /tmp/buildd/kdepim-3.5.1/build-tree/kdepim-3.5.1/kmail/main.cpp:110
#38 0xb787aeb0 in __libc_start_main () from /lib/tls/libc.so.6
#39 0x08049e11 in _start () at ../sysdeps/i386/elf/start.S:119
Comment 1 Tommi Tervo 2007-03-07 12:59:55 UTC
*** Bug 142639 has been marked as a duplicate of this bug. ***
Comment 2 Tommi Tervo 2007-03-07 13:00:33 UTC
*** Bug 106317 has been marked as a duplicate of this bug. ***
Comment 3 Thomas McGuire 2007-05-18 18:16:16 UTC
*** Bug 145637 has been marked as a duplicate of this bug. ***
Comment 4 Björn Ruberg 2009-12-25 19:09:33 UTC
I'm working with instable vpn-connections (similar to modem connections, I think) and kmail does not crash. At least not in KDE 4.