[Bug 251128] New: kontact crashes when starting after being closed while checking an IMAP account

[bugs.lfk at gmail.com]

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

           Summary: kontact crashes when starting after being closed while
                    checking an IMAP account
           Product: kontact
           Version: unspecified
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: bugs.lfk at gmail.com


Application: kontact (4.4.6)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.6.3
Operating System: Linux 2.6.34.4-0.1-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I just lauched kontact and it crased. This appens when just before kontact was
closed while still checking mail on the gmail.com IMAP server (hanging a bit).

- Custom settings of the application:
2 google IMAP accounts, 1 professional POP account & 1 professionnal IMAP
account.
Launched with the command: "kontact --graphicssystem raster".

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f8c91a1619e in KMFolderMaildir::open (this=0x1f29050) at
/usr/src/debug/kdepim-4.4.6/kmail/kmfoldermaildir.cpp:113
#7  0x00007f8c9192fc18 in KMFolder::remove (this=0x1cce9e0) at
/usr/src/debug/kdepim-4.4.6/kmail/kmfolder.cpp:584
#8  0x00007f8c9197d0e3 in KMFolderMgr::remove (this=0x83bb30,
aFolder=0x1cce9e0) at /usr/src/debug/kdepim-4.4.6/kmail/kmfoldermgr.cpp:354
#9  0x00007f8c91962238 in KMail::ActionScheduler::~ActionScheduler
(this=0x1b2b3d0, __in_chrg=<value optimized out>) at
/usr/src/debug/kdepim-4.4.6/kmail/actionscheduler.cpp:136
#10 0x00007f8c91962369 in KMail::ActionScheduler::~ActionScheduler
(this=0x1b2b3d0, __in_chrg=<value optimized out>) at
/usr/src/debug/kdepim-4.4.6/kmail/actionscheduler.cpp:144
#11 0x00007f8cac18552d in QObject::event(QEvent*) () from
/usr/lib64/libQtCore.so.4
#12 0x00007f8cab5654d4 in QApplicationPrivate::notify_helper (this=0x6472f0,
receiver=0x1b2b3d0, e=0xb26220) at kernel/qapplication.cpp:4302
#13 0x00007f8cab56daca in QApplication::notify (this=<value optimized out>,
receiver=0x1b2b3d0, e=0xb26220) at kernel/qapplication.cpp:4185
#14 0x00007f8caca991e6 in KApplication::notify (this=0x7fffc3d8f150,
receiver=0x1b2b3d0, event=0xb26220) at
/usr/src/debug/kdelibs-4.5.1/kdeui/kernel/kapplication.cpp:310
#15 0x00007f8cac173e4c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQtCore.so.4
#16 0x00007f8cac1775ba in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#17 0x00007f8cac19c173 in ?? () from /usr/lib64/libQtCore.so.4
#18 0x00007f8ca37bda93 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#19 0x00007f8ca37be270 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f8ca37be510 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#21 0x00007f8cac19c67f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/libQtCore.so.4
#22 0x00007f8cab60614e in QGuiEventDispatcherGlib::processEvents (this=<value
optimized out>, flags=<value optimized out>) at
kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007f8cac173292 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQtCore.so.4
#24 0x00007f8cac173495 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQtCore.so.4
#25 0x00007f8cac17788b in QCoreApplication::exec() () from
/usr/lib64/libQtCore.so.4
#26 0x000000000040417e in main (argc=1, argv=0x7fffc3d8f738) at
/usr/src/debug/kdepim-4.4.6/kontact/src/main.cpp:224

Possible duplicates by query: bug 215928, bug 212369, bug 212258, bug 206968,
bug 203579.

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.