Bug 205727

Summary:	Kmail crashed when closed with the window's close button
Product:	[Unmaintained] kmail	Reporter:	Szczepan Hołyszewski <rulatir>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Szczepan Hołyszewski 2009-08-30 21:38:23 UTC

Application that crashed: kmail
Version of the application: 1.12.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-ARCH i686

What I was doing when the application crashed:
This might be a duplicate of 179216, but then maybe not, given that my gpgme is at 1.2.


 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  0xb7585fe0 in KMail::ObjectTreeParser::writeOpaqueOrMultipartSignedData () from /usr/lib/libkmailprivate.so.4
#7  0xb75892de in KMail::ObjectTreeParser::processMultiPartSignedSubtype () from /usr/lib/libkmailprivate.so.4
#8  0xb759029b in (anonymous namespace)::MultiPartSignedBodyPartFormatter::process () from /usr/lib/libkmailprivate.so.4
#9  0xb75818d8 in KMail::ObjectTreeParser::parseObjectTree () from /usr/lib/libkmailprivate.so.4
#10 0xb73e7b37 in KMReaderWin::parseMsg () from /usr/lib/libkmailprivate.so.4
#11 0xb73d57f9 in KMReaderWin::displayMessage () from /usr/lib/libkmailprivate.so.4
#12 0xb73d59eb in KMReaderWin::updateReaderWin () from /usr/lib/libkmailprivate.so.4
#13 0xb73e29c4 in KMReaderWin::qt_metacall () from /usr/lib/libkmailprivate.so.4
#14 0xb70489ac in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb70495e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb7082a87 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#17 0xb704e05e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#18 0xb7042b5f in QObject::event () from /usr/lib/libQtCore.so.4
#19 0xb6684994 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#20 0xb668c07c in QApplication::notify () from /usr/lib/libQtGui.so.4
#21 0xb7df4faa in KApplication::notify () from /usr/lib/libkdeui.so.5
#22 0xb7032fcb in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#23 0xb706079e in ?? () from /usr/lib/libQtCore.so.4
#24 0xb705d780 in ?? () from /usr/lib/libQtCore.so.4
#25 0xb483bd98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb483f3e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#27 0xb483f513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb705d6cc in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb67226c5 in ?? () from /usr/lib/libQtGui.so.4
#30 0xb7031579 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#31 0xb70319ca in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#32 0xb7033e3f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#33 0xb6684817 in QApplication::exec () from /usr/lib/libQtGui.so.4
#34 0x0804a6b2 in _start ()

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

Reported using DrKonqi

Comment 1 Christophe Marin 2009-09-02 18:18:08 UTC

Unfortunately, the backtrace is not useful. 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 Szczepan Hołyszewski 2009-09-03 13:00:47 UTC

Then we're having a KCrash defect here: it misidentified the stack trace as useful. I realize it uses heuristics, but perhaps those can be improved?

Anyway,

- Arch Linux doesn't provide debug packages
- the howto doesn't provide exact instructions for Arch Linux
- Arch Linux has just recently switched to split packages:

kdepim-akregator
kdepim-console
kdepim-kaddressbook
kdepim-kalarm
kdepim-kjots
kdepim-kleopatra
kdepim-kmail
kdepim-knode
kdepim-knotes
kdepim-kontact
kdepim-korganizer
kdepim-kpilot
kdepim-kresources
kdepim-ktimetracker
kdepim-libkdepim
kdepim-runtime
kdepim-wizards
kdepimlibs

Which of these should I rebuild?

This crash has never happened again, which probably means I cannot reproduce it. Is the original KCrash report saved somewhere, so that I can reload it, load symbols into it, and resend?

Comment 3 Myriam Schweingruber 2012-08-19 11:02:41 UTC

Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding