Bug 210024 - sending a message hangs after server connection is reestablished
Summary: sending a message hangs after server connection is reestablished
Status: RESOLVED DUPLICATE of bug 204515
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-09 22:34 UTC by Ivan D Vasin
Modified: 2009-10-10 09:56 UTC (History)
0 users

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 Ivan D Vasin 2009-10-09 22:34:45 UTC
Application that crashed: kmail
Version of the application: 1.12.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
it often happens that KMail will pop up an annoying message saying "the connection to the server could not be established", or something along those lines, when performing an automatic mail check. this is despite the fact that my network connection is fine---of this i am certain, since i've checked my mail manually through a Web client immediately before, during, and after this message has popped up.

by itself this message isn't terrible since KDE's focus-stealing prevention usually prevents the message from interrupting me (except, notably, when i am running some applications in wine). it is annoying that i need to close it every time, which is numerous times per day. however, it seems that a consequence of this occurrence is that sometimes any subsequent messages that i attempt to send through KMail will hang indefinitely at 0%. i can click the '-' button to cancel the process, but the grayed-out message window remains. i can then click the close button on the message window, which prompts me to save a draft, but regardless of my choice, the window remains in its grayed-out state. the only way i have found to work around this is to kill KMail. it was such a workaround that produced the included backtrace.

 -- Backtrace:
Application: KMail (kmail), signal: Aborted
[KCrash Handler]
#33 0x00007f270017f496 in *__GI___poll (fds=0x3b800e0, nfds=6, timeout=460) at ../sysdeps/unix/sysv/linux/poll.c:87
#34 0x00007f26f7be877f in ?? () from /usr/lib/libglib-2.0.so.0
#35 0x00007f26f7be8a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0x00007f2700d30a8f in QEventDispatcherGlib::processEvents (this=0x1f046d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#37 0x00007f27014a9bdf in QGuiEventDispatcherGlib::processEvents (this=0x3b800e0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#38 0x00007f2700d05f42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 233393936}) at kernel/qeventloop.cpp:149
#39 0x00007f2700d06314 in QEventLoop::exec (this=0x7fff0de95070, flags={i = 233394544}) at kernel/qeventloop.cpp:201
#40 0x00007f27059064be in KWallet::Wallet::openWallet (name=@0x7fff0de951c0, w=<value optimized out>, ot=KWallet::Wallet::Synchronous) at /build/buildd/kde4libs-4.3.2/kdeui/util/kwallet.cpp:252
#41 0x00007f26fc8268cd in MailTransport::TransportManager::wallet (this=0x1f88630) at /build/buildd/kdepimlibs-4.3.2/mailtransport/transportmanager.cpp:420
#42 0x00007f26fc81c82d in MailTransport::Transport::readPassword (this=0x2100cd0) at /build/buildd/kdepimlibs-4.3.2/mailtransport/transport.cpp:245
#43 0x00007f26fc82547d in MailTransport::TransportManager::loadPasswords (this=0x1f88630) at /build/buildd/kdepimlibs-4.3.2/mailtransport/transportmanager.cpp:445
#44 0x00007f26fc81bafd in MailTransport::Transport::password (this=0x5b6d110) at /build/buildd/kdepimlibs-4.3.2/mailtransport/transport.cpp:76
#45 0x00007f26fc82d52e in MailTransport::SmtpJob::startSmtpJob (this=0x5bc6330) at /build/buildd/kdepimlibs-4.3.2/mailtransport/smtpjob.cpp:159
#46 0x00007f26fc82e66f in MailTransport::SmtpJob::doStart (this=0x5bc6330) at /build/buildd/kdepimlibs-4.3.2/mailtransport/smtpjob.cpp:114
#47 0x00007f26fc82482d in MailTransport::TransportJob::start (this=0x5bc6330) at /build/buildd/kdepimlibs-4.3.2/mailtransport/transportjob.cpp:129
#48 0x00007f2704a3ecfe in ?? () from /usr/lib/libkmailprivate.so.4
#49 0x00007f2704a400c2 in ?? () from /usr/lib/libkmailprivate.so.4
#50 0x00007f2704a3cd65 in ?? () from /usr/lib/libkmailprivate.so.4
#51 0x00007f27049c2f35 in ?? () from /usr/lib/libkmailprivate.so.4
#52 0x00007f27049d1a6c in ?? () from /usr/lib/libkmailprivate.so.4
#53 0x00007f2700d1cea2 in QMetaObject::activate (sender=0x3902df0, from_signal_index=<value optimized out>, to_signal_index=50, argv=0xffffffffffffffff) at kernel/qobject.cpp:3113
#54 0x00007f27049a78cf in ?? () from /usr/lib/libkmailprivate.so.4
#55 0x00007f27049a79a0 in ?? () from /usr/lib/libkmailprivate.so.4
#56 0x00007f27049d1a84 in ?? () from /usr/lib/libkmailprivate.so.4
#57 0x00007f2700d1cea2 in QMetaObject::activate (sender=0x5139bc0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xffffffffffffffff) at kernel/qobject.cpp:3113
#58 0x00007f2704c4b51f in ?? () from /usr/lib/libkmailprivate.so.4
#59 0x00007f2704c4b6f5 in ?? () from /usr/lib/libkmailprivate.so.4
#60 0x00007f2704c4b877 in ?? () from /usr/lib/libkmailprivate.so.4
#61 0x00007f2704c4b8b9 in ?? () from /usr/lib/libkmailprivate.so.4
#62 0x00007f2704c4b9fd in ?? () from /usr/lib/libkmailprivate.so.4
#63 0x00007f2700d1cea2 in QMetaObject::activate (sender=0x4fe3430, from_signal_index=<value optimized out>, to_signal_index=4, argv=0xffffffffffffffff) at kernel/qobject.cpp:3113
#64 0x00007f2700d2214f in QSingleShotTimer::timerEvent (this=0x4fe3430) at kernel/qtimer.cpp:298
#65 0x00007f2700d17263 in QObject::event (this=0x4fe3430, e=0x6) at kernel/qobject.cpp:1075
#66 0x00007f2701410f4d in QApplicationPrivate::notify_helper (this=0x1f98f90, receiver=0x4fe3430, e=0x7fff0de96ed0) at kernel/qapplication.cpp:4056
#67 0x00007f270141918a in QApplication::notify (this=0x7fff0de97350, receiver=0x4fe3430, e=0x7fff0de96ed0) at kernel/qapplication.cpp:4021
#68 0x00007f270587eabb in KApplication::notify (this=0x7fff0de97350, receiver=0x4fe3430, event=0x7fff0de96ed0) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#69 0x00007f2700d076ac in QCoreApplication::notifyInternal (this=0x7fff0de97350, receiver=0x4fe3430, event=0x7fff0de96ed0) at kernel/qcoreapplication.cpp:610
#70 0x00007f2700d34516 in QTimerInfoList::activateTimers (this=0x1f44320) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#71 0x00007f2700d30b2d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#72 0x00007f26f7be520a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#73 0x00007f26f7be88e0 in ?? () from /usr/lib/libglib-2.0.so.0
#74 0x00007f26f7be8a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#75 0x00007f2700d30a8f in QEventDispatcherGlib::processEvents (this=0x1f046d0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#76 0x00007f27014a9bdf in QGuiEventDispatcherGlib::processEvents (this=0x3b800e0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#77 0x00007f2700d05f42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 233402688}) at kernel/qeventloop.cpp:149
#78 0x00007f2700d06314 in QEventLoop::exec (this=0x7fff0de97180, flags={i = 233402768}) at kernel/qeventloop.cpp:201
#79 0x00007f2700d085e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#80 0x00000000004030db in _start ()

Reported using DrKonqi
Comment 1 Christophe Marin 2009-10-10 09:56:31 UTC

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