Bug 169366 - KMail crashes when logging out
Summary: KMail crashes when logging out
Status: RESOLVED DUPLICATE of bug 163712
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.10.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-18 15:02 UTC by Eric Sorensen
Modified: 2008-08-18 15:32 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 Eric Sorensen 2008-08-18 15:02:52 UTC
Version:           1.10.0 (using 4.1.1 (KDE 4.1.0 (4.1 >= 20080722)) "release 27.1", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.25.11-0.1-default

when ever I exit my KDE (Logoff, Shutdown, Restart), KMail crashes.  The only way to exit KDE4 with out a crash is to completely exit KMail (Kontact).  Leaving it running in the System Tray still causes crashes.  If this is not well known, them my installation is probably just prety badly hacked.  Here is the Dump:


Anwendung: Kontact (kontact), Signal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f0c49451700 (LWP 3943)]
[KCrash handler]
#5  QList<QString>::append (this=0x7fff514a4af0, t=@0x1a757b0)
    at /usr/include/QtCore/qatomic_x86_64.h:123
#6  0x00007f0c320b82a1 in ~KMAcctImap (this=0xf2e250)
    at /usr/src/debug/kdepim-4.1.0/kmail/kmacctimap.cpp:95
#7  0x00007f0c3204a756 in ~AccountManager (this=0xce9d60)
    at /usr/include/QtCore/qalgorithms.h:352
#8  0x00007f0c3210fea3 in KMKernel::cleanup (this=0xc970e0)
    at /usr/src/debug/kdepim-4.1.0/kmail/kmkernel.cpp:1684
#9  0x00007f0c3273a80a in ~KMailPart (this=0x9825d0)
    at /usr/src/debug/kdepim-4.1.0/kmail/kmail_part.cpp:138
#10 0x00007f0c48e3f79a in ~MainWindow (this=0x6261a0)
    at /usr/src/debug/kdepim-4.1.0/kontact/src/mainwindow.cpp:248
#11 0x00007f0c43c24325 in QObject::event (this=0x6261a0, e=0x1ec4658)
    at kernel/qobject.cpp:1124
#12 0x00007f0c401e341c in QWidget::event (this=0x7f0c43edb6c0, event=0x196b6f0)
    at kernel/qwidget.cpp:7407
#13 0x00007f0c404b4d7b in QMainWindow::event (this=0x6261a0, event=0x196b6f0)
    at widgets/qmainwindow.cpp:1274
#14 0x00007f0c45c50708 in KXmlGuiWindow::event (this=0x7f0c43edb6c0, 
    ev=0x1ec4658)
    at /usr/src/debug/kdelibs-4.1.0/kdeui/xmlgui/kxmlguiwindow.cpp:122
#15 0x00007f0c40196ebd in QApplicationPrivate::notify_helper (this=0x626df0, 
    receiver=0x6261a0, e=0x196b6f0) at kernel/qapplication.cpp:3800
#16 0x00007f0c4019d28a in QApplication::notify (this=0x7fff514a5b90, 
    receiver=0x6261a0, e=0x196b6f0) at kernel/qapplication.cpp:3765
#17 0x00007f0c45b66ddb in KApplication::notify (this=0x7fff514a5b90, 
    receiver=0x6261a0, event=0x196b6f0)
    at /usr/src/debug/kdelibs-4.1.0/kdeui/kernel/kapplication.cpp:311
#18 0x00007f0c43c1678c in QCoreApplication::notifyInternal (
    this=0x7fff514a5b90, receiver=0x6261a0, event=0x196b6f0)
    at kernel/qcoreapplication.cpp:587
#19 0x00007f0c43c170bb in QCoreApplicationPrivate::sendPostedEvents (
    receiver=0x0, event_type=0, data=0x607620) at kernel/qcoreapplication.h:215
#20 0x00007f0c43c3d2f0 in QEventDispatcherUNIX::processEvents (this=0x6253b0, 
    flags={i = 1363826448}) at kernel/qeventdispatcher_unix.cpp:881
#21 0x00007f0c40217dca in QEventDispatcherX11::processEvents (this=0x6253b0, 
    flags={i = 1363827312}) at kernel/qeventdispatcher_x11.cpp:154
#22 0x00007f0c43c150e2 in QEventLoop::processEvents (
    this=<value optimized out>, flags={i = 1363827360})
    at kernel/qeventloop.cpp:149
#23 0x00007f0c43c15275 in QEventLoop::exec (this=0x7fff514a5ae0, flags=
      {i = 1363827440}) at kernel/qeventloop.cpp:196
#24 0x00007f0c43c17315 in QCoreApplication::exec ()
    at kernel/qcoreapplication.cpp:849
#25 0x0000000000404a7b in main (argc=1, argv=0x7fff514a6278)
    at /usr/src/debug/kdepim-4.1.0/kontact/src/main.cpp:218
#0  0x00007f0c3e57a230 in nanosleep () from /lib64/libc.so.6
Comment 1 Christophe Marin 2008-08-18 15:32:04 UTC

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