Bug 211843 - Crash when simply closing Kontact/KMail
Summary: Crash when simply closing Kontact/KMail
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-25 23:19 UTC by Jos Geluk
Modified: 2018-09-04 18:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (3.69 KB, text/plain)
2010-06-06 08:50 UTC, Willy Gommel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jos Geluk 2009-10-25 23:19:46 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-16-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I closed KMail (or rather the mail component of Kontact) after viewing some mails, then it crashed. I have not seen this happen before. I closed it by clicking on the "close" button in the upper right corner of the window.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0xb117c877 in KMCommand::slotStart () from /usr/lib/libkmailprivate.so.4
#7  0xb116d453 in KMCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#8  0xb116d832 in KMSetStatusCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#9  0xb5c621b8 in QMetaObject::activate (sender=0xa53fc10, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#10 0xb5c62e42 in QMetaObject::activate (sender=0xa53fc10, m=0xb5d3e908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#11 0xb5c67f77 in QSingleShotTimer::timeout (this=0xa53fc10) at .moc/release-shared/qtimer.moc:76
#12 0xb5c6809c in QSingleShotTimer::timerEvent (this=0xa53fc10) at kernel/qtimer.cpp:298
#13 0xb5c5d16f in QObject::event (this=0xa53fc10, e=0xbfdbab5c) at kernel/qobject.cpp:1075
#14 0xb6110d3c in QApplicationPrivate::notify_helper (this=0x94d49f8, receiver=0xa53fc10, e=0xbfdbab5c) at kernel/qapplication.cpp:4056
#15 0xb611903e in QApplication::notify (this=0xbfdbae08, receiver=0xa53fc10, e=0xbfdbab5c) at kernel/qapplication.cpp:3603
#16 0xb6d0a49d in KApplication::notify (this=0xbfdbae08, receiver=0xa53fc10, event=0xbfdbab5c) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#17 0xb5c4cbcb in QCoreApplication::notifyInternal (this=0xbfdbae08, receiver=0xa53fc10, event=0xbfdbab5c) at kernel/qcoreapplication.cpp:610
#18 0xb5c7bd51 in QTimerInfoList::activateTimers (this=0x94d0e84) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 0xb5c783a0 in timerSourceDispatch (source=0x94d0e50) at kernel/qeventdispatcher_glib.cpp:165
#20 0xb4d1db88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb4d210eb in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb4d21268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb5c782f8 in QEventDispatcherGlib::processEvents (this=0x94b1028, flags={i = -1076122408}) at kernel/qeventdispatcher_glib.cpp:327
#24 0xb61b2a75 in QGuiEventDispatcherGlib::processEvents (this=0x94b1028, flags={i = -1076122360}) at kernel/qguieventdispatcher_glib.cpp:202
#25 0xb5c4b1fa in QEventLoop::processEvents (this=0xbfdbad80, flags={i = -1076122296}) at kernel/qeventloop.cpp:149
#26 0xb5c4b642 in QEventLoop::exec (this=0xbfdbad80, flags={i = -1076122232}) at kernel/qeventloop.cpp:201
#27 0xb5c4dae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0xb6110bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#29 0x0804bfef in _start ()

Reported using DrKonqi
Comment 1 Christophe Marin 2009-10-27 00:04:10 UTC
Unfortunately, the backtrace is not helpful.
If you can reproduce this bug, please install the debug package for kdepim and paste a better one.
More informations on this page: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Willy Gommel 2010-06-06 08:50:44 UTC
Created attachment 47729 [details]
New crash information added by DrKonqi

I had been rooting around in my Opera web browser for a couple of hours while Kmail was sitting open. Then I went to close Kmail immediately after closing Opera--and this resulted. I'm sorry that I cannot come up with anything more definite as to surrounding circumstances of its failure--but that's the way the cookie crumbles this time!

Thank you very much for all of your efforts! :)

-- 
Willy Gommel
www.wg3.net
Comment 3 Andrew Crouthamel 2018-09-04 18:20:40 UTC
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!