Bug 262823

Summary:	Replying to All in Kmail 2.0.89 for a lengthy thread brings a crash
Product:	[Applications] kmail2	Reporter:	Roger Pixley <skreech2>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	tokoe
Priority:	NOR	Keywords:	investigated, triaged
Version:	2.0.89
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Roger Pixley 2011-01-11 05:19:19 UTC

Application: kmail (2.0.89)
KDE Platform Version: 4.5.95 (4.6 RC2)
Qt Version: 4.7.1
Operating System: Linux 2.6.35.10-74.fc14.i686 i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I have one thread with a little over 30 replies that is not a true mailing list instead we just hit reply all. I've been back and forthing in the thread and reading updates all day. A new mail came in and I hit reply all and Kmail crashed. I reopened it and tried again resulting in a crash. I rebooted and opened Kmail replied all again and it crashed. Opened and replied all to a different thread tried reply all to a single e-mail then replied all to the original thread and then submitted this report. I installed debug packages for Akonadi KDEPIM and KDELibs. Please let me know if any other packages would help. (Gstreamer was suggested but I didn't think it applicable though the duplicates suggested were very heavy on Amarok and Knotify)

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
[Current thread is 1 (Thread 0xb76ee780 (LWP 9261))]

Thread 2 (Thread 0xb5469b70 (LWP 9268)):
#0  0x00640416 in __kernel_vsyscall ()
#1  0x0099c98b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0x42383057 in ?? () from /usr/lib/libQtWebKit.so.4
#3  0x00997f19 in start_thread () from /lib/libpthread.so.0
#4  0x008d1c4e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb76ee780 (LWP 9261)):
[KCrash Handler]
#7  0x00640416 in __kernel_vsyscall ()
#8  0x00821531 in raise () from /lib/libc.so.6
#9  0x00822f9e in abort () from /lib/libc.so.6
#10 0x00c69c45 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#11 0x00c67b16 in ?? () from /usr/lib/libstdc++.so.6
#12 0x00c67b53 in std::terminate() () from /usr/lib/libstdc++.so.6
#13 0x00c67d3c in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#14 0x074f8855 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#15 0x074fd327 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#16 0x0241e078 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#17 0x0804a793 in main (argc=) at /usr/src/debug/kdepim-4.6beta3/kmail/main.cpp:145

Possible duplicates by query: bug 262617, bug 262425, bug 262413, bug 262340, bug 262308.

Reported using DrKonqi

Comment 1 Tobias Koenig 2011-06-04 12:15:58 UTC

Hej Roger,

can you try a more recent version, please?

Ciao,
Tobias

Comment 2 Roger Pixley 2011-06-05 04:14:26 UTC

Ok I'm on 2.0.96 now but Akonadi Console tells me there is no Mysql to contact and Akonadi Configuration is telling me everything is ok. So Kmail is krashing as soon as it opens. Once I have that sorted I'll test and let you know unless you want me to test on a newer version than that.

Comment 3 Andrew Crouthamel 2018-09-22 01:50:36 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Andrew Crouthamel 2018-10-27 03:34:22 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!