Bug 254775 - Crashes on exit after IMAP connection failure
Summary: Crashes on exit after IMAP connection failure
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 283099 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-10-20 16:56 UTC by SZÉKELYI Szabolcs
Modified: 2011-09-30 14:53 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 SZÉKELYI Szabolcs 2010-10-20 16:56:53 UTC
Application: kmail (1.13.5)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-22-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:

Exited KMail after an IMAP connection seemed stalled, however another one worked absolutely correct.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f1de09f4820 (LWP 5595))]

Thread 2 (Thread 0x7f1dbd2af710 (LWP 5600)):
#0  0x00007f1ddd44d1d3 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f1dd4508009 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f1dd450845c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007f1dddda71e6 in QEventDispatcherGlib::processEvents (this=0x1fd6d20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:417
#4  0x00007f1dddd79a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f1dddd79dec in QEventLoop::exec (this=0x7f1dbd2aecf0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007f1dddc842fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007f1dddd595f8 in QInotifyFileSystemWatcherEngine::run (this=0x1ef66a0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f1dddc8727e in QThreadPrivate::start (arg=0x1ef66a0) at thread/qthread_unix.cpp:266
#9  0x00007f1ddaf53971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#10 0x00007f1ddd45991d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f1de09f4820 (LWP 5595)):
[KCrash Handler]
#6  KPIM::ProgressItem::setComplete (this=0x8d86b30) at ../../libkdepim/progressmanager.cpp:52
#7  0x00007f1ddf2f7b78 in KMAccount::checkDone (this=0x1afa200, newmail=false, status=KMAccount::CheckOK) at ../../kmail/kmaccount.cpp:510
#8  0x00007f1ddf3f6300 in KMAcctImap::killAllJobs (this=0x1afa200, disconnectSlave=<value optimized out>) at ../../kmail/kmacctimap.cpp:204
#9  0x00007f1ddf3f3459 in KMAcctImap::cancelMailCheck (this=0x1afa200) at ../../kmail/kmacctimap.cpp:268
#10 0x00007f1ddf37a871 in KMail::AccountManager::cancelMailCheck (this=<value optimized out>) at ../../kmail/accountmanager.cpp:427
#11 0x00007f1ddf27ec0f in KMMainWin::~KMMainWin (this=0x5b6e8e0, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at ../../kmail/kmmainwin.cpp:103
#12 0x00007f1dddd8cc08 in QObject::event (this=0x5b6e8e0, e=0x1e82d18) at kernel/qobject.cpp:1202
#13 0x00007f1dde2bb6df in QWidget::event (this=0x5b6e8e0, event=0x57f4910) at kernel/qwidget.cpp:8646
#14 0x00007f1dde6a341b in QMainWindow::event (this=0x5b6e8e0, event=0x57f4910) at widgets/qmainwindow.cpp:1417
#15 0x00007f1de052a683 in KXmlGuiWindow::event (this=0x8d86b30, ev=0x1e82d18) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:130
#16 0x00007f1dde265fdc in QApplicationPrivate::notify_helper (this=0x1474640, receiver=0x5b6e8e0, e=0x57f4910) at kernel/qapplication.cpp:4396
#17 0x00007f1dde26baed in QApplication::notify (this=0x7fff1bb47690, receiver=0x5b6e8e0, e=0x57f4910) at kernel/qapplication.cpp:4277
#18 0x00007f1de040e156 in KApplication::notify (this=0x7fff1bb47690, receiver=0x5b6e8e0, event=0x57f4910) at ../../kdeui/kernel/kapplication.cpp:310
#19 0x00007f1dddd7acdc in QCoreApplication::notifyInternal (this=0x7fff1bb47690, receiver=0x5b6e8e0, event=0x57f4910) at kernel/qcoreapplication.cpp:732
#20 0x00007f1dddd7dc22 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x1430150) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x1430150) at kernel/qcoreapplication.cpp:1373
#22 0x00007f1dddda7653 in sendPostedEvents (s=0x1477d60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#23 postEventSourceDispatch (s=0x1477d60) at kernel/qeventdispatcher_glib.cpp:277
#24 0x00007f1dd4504342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007f1dd45082a8 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007f1dd450845c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007f1dddda7193 in QEventDispatcherGlib::processEvents (this=0x142f8a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#28 0x00007f1dde318a4e in QGuiEventDispatcherGlib::processEvents (this=0x8d86b30, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007f1dddd79a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#30 0x00007f1dddd79dec in QEventLoop::exec (this=0x7fff1bb474c0, flags=) at kernel/qeventloop.cpp:201
#31 0x00007f1dddd7debb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#32 0x0000000000403212 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:156

This bug may be a duplicate of or related to bug 231508.

Possible duplicates by query: bug 248439, bug 247424, bug 241976, bug 234992, bug 231508.

Reported using DrKonqi
Comment 1 Laurent Montel 2010-10-21 17:19:53 UTC
SVN commit 1188166 by mlaurent:

Fix Bug 254775 -  Crashes on exit after IMAP connection failure
BUG: 254775 (not necessary to backport to trunk)


 M  +4 -2      kmaccount.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1188166
Comment 2 Christophe Marin 2011-09-30 14:53:05 UTC
*** Bug 283099 has been marked as a duplicate of this bug. ***