[Bug 245790] New: kmail crashed after adding a new subfolder and copying a mail into it. (IMAP disconnected)

[Alain BAECKEROOT]

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

           Summary: kmail crashed after adding a new subfolder and copying
                    a mail into it. (IMAP disconnected)
           Product: kmail
           Version: unspecified
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: alain.baeckeroot at laposte.net


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.31-22-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
One disconnected IMAP account

I created a new subfolder, then copied a mail from inbox. So far so good.
When i clicked on the mail (inside the new subfolder) kmail crashed

i guess this has to do with synchronisation with the imap server.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0x00000008 in ?? ()
#7  0x0103d4d9 in ?? () from /usr/lib/libkmailprivate.so.4
#8  0x0103d6cb in ?? () from /usr/lib/libkmailprivate.so.4
#9  0x0104a9d4 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0x02a2f263 in QMetaObject::activate (sender=0x9bb2080, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#11 0x02a2fec2 in QMetaObject::activate (sender=0x9bb2080, m=0x2b0a904,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#12 0x02a69667 in QTimer::timeout (this=0x9bb2080) at
.moc/release-shared/moc_qtimer.cpp:128
#13 0x02a349ae in QTimer::timerEvent (this=0x9bb2080, e=0xbf8062d0) at
kernel/qtimer.cpp:261
#14 0x02a293bf in QObject::event (this=0x9bb2080, e=0xbf8062d0) at
kernel/qobject.cpp:1075
#15 0x03040f54 in QApplicationPrivate::notify_helper (this=0x98e13a0,
receiver=0x9bb2080, e=0xbf8062d0) at kernel/qapplication.cpp:4056
#16 0x0304867c in QApplication::notify (this=0xbf8066d0, receiver=0x9bb2080,
e=0xbf8062d0) at kernel/qapplication.cpp:3603
#17 0x00ce3bfa in KApplication::notify (this=0xbf8066d0, receiver=0x9bb2080,
event=0xbf8062d0) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x02a196cb in QCoreApplication::notifyInternal (this=0xbf8066d0,
receiver=0x9bb2080, event=0xbf8062d0) at kernel/qcoreapplication.cpp:610
#19 0x02a467ce in QCoreApplication::sendEvent (this=0x98e399c) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 QTimerInfoList::activateTimers (this=0x98e399c) at
kernel/qeventdispatcher_unix.cpp:572
#21 0x02a440e0 in timerSourceDispatch (source=0x98e3968) at
kernel/qeventdispatcher_glib.cpp:165
#22 0x0204ee88 in g_main_dispatch (context=0x98e3290) at
/build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#23 IA__g_main_context_dispatch (context=0x98e3290) at
/build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#24 0x02052730 in g_main_context_iterate (context=0x98e3290, block=<value
optimized out>, dispatch=1, self=0x98e09b8) at
/build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#25 0x02052863 in IA__g_main_context_iteration (context=0x98e3290, may_block=1)
at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#26 0x02a4402c in QEventDispatcherGlib::processEvents (this=0x98bb180,
flags=...) at kernel/qeventdispatcher_glib.cpp:327
#27 0x030e1be5 in QGuiEventDispatcherGlib::processEvents (this=0x98bb180,
flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#28 0x02a17c79 in QEventLoop::processEvents (this=0xbf806594, flags=) at
kernel/qeventloop.cpp:149
#29 0x02a180ca in QEventLoop::exec (this=0xbf806594, flags=...) at
kernel/qeventloop.cpp:201
#30 0x02a1a53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#31 0x03040dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#32 0x0804a702 in _start ()

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.