Bug 206653

Summary:	crash when sending acknowledge
Product:	[Unmaintained] kmail	Reporter:	EM <R125600>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED NOT A BUG
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description EM 2009-09-07 19:13:49 UTC

Version:            (using KDE 4.2.4)
Installed from:    Debian testing/unstable Packages

For a few weeks kmail has difficulites to start: no specific error message, even started from console. At second or third test it is OK
Today, it started well and I got on a received message an acknowledge request: I answered "Yes" and all crashed!
Backtrace info is not filled in in a full manner but I add it if usefull:
===
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)Since a a 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xacb9ab90 (LWP 9264)]
(no debugging symbols found)Since a a 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb8064424 in __kernel_vsyscall ()
[Current thread is 1 (Thread 0xb3f74700 (LWP 7037))]

Thread 2 (Thread 0xacb9ab90 (LWP 9264)):
#0  0xb8064424 in __kernel_vsyscall ()
#1  0xb644cfe1 in select () from /lib/i686/cmov/libc.so.6
#2  0xb70cec80 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb6fff582 in ?? () from /usr/lib/libQtCore.so.4
#4  0xb560b4b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#5  0xb6454a5e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb3f74700 (LWP 7037)):
#0  0xb8064424 in __kernel_vsyscall ()
#1  0xb6411676 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb641148e in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7efc0f8 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7efcac4 in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb55edb30 in DwHeaders::FindField(char const*) const () from /usr/lib/libmimelib.so.4
#7  0xb73a14bd in ?? () from /usr/lib/libkmailprivate.so.4
#8  0xb73a90d7 in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xb73b9c85 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0xb74a1ac9 in ?? () from /usr/lib/libkmailprivate.so.4
#11 0xb74b3f83 in ?? () from /usr/lib/libkmailprivate.so.4
#12 0xb7105b33 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#13 0xb7106782 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#14 0xb7141177 in QTimer::timeout() () from /usr/lib/libQtCore.so.4
#15 0xb710be9e in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQtCore.so.4
#16 0xb7100bcf in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#17 0xb6730814 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0xb673897e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0xb7e8c5ed in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#20 0xb70f09cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#21 0xb711f361 in ?? () from /usr/lib/libQtCore.so.4
#22 0xb711b900 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb4894368 in g_main_dispatch (context=0x8335e90) at /build/buildd-glib2.0_2.20.4-1-i386-6KfM1O/glib2.0-2.20.4/glib/gmain.c:1824
#24 IA__g_main_context_dispatch (context=0x8335e90) at /build/buildd-glib2.0_2.20.4-1-i386-6KfM1O/glib2.0-2.20.4/glib/gmain.c:2377
#25 0xb48978c3 in g_main_context_iterate (context=0x8335e90, block=1, dispatch=1, self=0x8334028) at /build/buildd-glib2.0_2.20.4-1-i386-6KfM1O/glib2.0-2.20.4/glib/gmain.c:2455
#26 0xb4897a48 in IA__g_main_context_iteration (context=0x8335e90, may_block=1) at /build/buildd-glib2.0_2.20.4-1-i386-6KfM1O/glib2.0-2.20.4/glib/gmain.c:2518
#27 0xb711b858 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0xb67cffd5 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb70ef01a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0xb70ef462 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0xb70f18b9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#32 0xb6730697 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#33 0x0804a6a0 in _start ()
===

Comment 1 Christophe Marin 2009-09-07 20:42:27 UTC

Unfortunately, the backtrace is not useful and your KMail version is very old. If you can reproduce this bug with KMail from KDE 4.3.1, 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 EM 2009-09-07 22:16:29 UTC

The version of mail I use is "Version 1.11.4 / KDE 4.2.4". it is the one Debian Squeez packages give: how can you consider it is too old for support?

kdepim is present on my configuration: what should I do to match your resquirements?

Next time I face a bug, I think I'll not report it, according to the way this one is received (even if; I understand, not well documented)

Comment 3 Torgny Nyblom 2009-09-08 08:09:09 UTC

(In reply to comment #2)
> The version of mail I use is "Version 1.11.4 / KDE 4.2.4". it is the one Debian
> Squeez packages give: how can you consider it is too old for support?

The entire 4.2 branch is out of date, hence no bugs will be fixed there. But if the bug is still present in the 4.3 branch we will try and fix it here.
The KDE community does not have the manpower to maintain old releases.

Comment 4 Christophe Marin 2009-10-23 15:35:11 UTC

Closing the old crash reports which don't have a useful backtrace. Thanks.