[Bug 202632] New: Kmail (Kontact) crashes on close after IMAP folder could not be displayed

[Markus Straub]

https://bugs.kde.org/show_bug.cgi?id=202632

           Summary: Kmail (Kontact) crashes on close after IMAP folder
                    could not be displayed
           Product: kontact
           Version: unspecified
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: markus.straub.at at gmail.com


Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-02063004-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
Kontact crashed after the IMAP process could not fetch data for an account. I
have two different account, I could still open folders and view mails in one
account, but not for the other one.
Even after the crash kio_imap4 is running and using 100% CPU

more detail about the process:

kdeinit4: kio_imap4 [kdeinit] imap
local:/tmp/ksocket-markus/klauncherMT3769.slave-socket
local:/tmp/ksocket-markus/kontactFm4278.slave-socket

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0xb1222f5d in ?? () from /usr/lib/libkmailprivate.so.4
#7  0xb5bb7af5 in qDeleteInEventHandler (o=0xa954a50) at
kernel/qobject.cpp:3815
#8  0xb5bb93db in QObject::event (this=0xa954a50, e=0xa8550a8) at
kernel/qobject.cpp:1094
#9  0xb6069d3c in QApplicationPrivate::notify_helper (this=0x8d08cf8,
receiver=0xa954a50, e=0xa8550a8) at kernel/qapplication.cpp:4056
#10 0xb607203e in QApplication::notify (this=0xbf85a168, receiver=0xa954a50,
e=0xa8550a8) at kernel/qapplication.cpp:3603
#11 0xb6c635cd in KApplication::notify () from /usr/lib/libkdeui.so.5
#12 0xb5ba8bcb in QCoreApplication::notifyInternal (this=0xbf85a168,
receiver=0xbf85a168, event=0xa8550a8) at kernel/qcoreapplication.cpp:610
#13 0xb5ba9825 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0,
event_type=0, data=0x8cdd440) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#14 0xb5ba9a1d in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1140
#15 0xb5bd46af in postEventSourceDispatch (s=0x8d0b1b8) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#16 0xb4c7ab88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0xb4c7e0eb in ?? () from /usr/lib/libglib-2.0.so.0
#18 0xb4c7e268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0xb5bd42f8 in QEventDispatcherGlib::processEvents (this=0x8cdd028, flags={i
= -1081761736}) at kernel/qeventdispatcher_glib.cpp:327
#20 0xb610ba75 in QGuiEventDispatcherGlib::processEvents (this=0x8cdd028,
flags={i = -1081761688}) at kernel/qguieventdispatcher_glib.cpp:202
#21 0xb5ba71fa in QEventLoop::processEvents (this=0xbf85a0e0, flags={i =
-1081761624}) at kernel/qeventloop.cpp:149
#22 0xb5ba7642 in QEventLoop::exec (this=0xbf85a0e0, flags={i = -1081761560})
at kernel/qeventloop.cpp:201
#23 0xb5ba9ae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#24 0xb6069bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#25 0x0804bfef in _start ()

This bug may be a duplicate of or related to bug 201722

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.