Bug 221790

Summary: kmail dies when entering body of new mail
Product: [Applications] kontact Reporter: Odd Arild Olsen <oao>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: kdenis, oao
Priority: NOR Keywords: triaged
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Odd Arild Olsen 2010-01-08 13:45:03 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.31-14-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Open new kmail session, select new message and click on the body field. Same problem if To and Subject fields filled out before enering body by mouse click or new line.

 -- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0x7f0d84406750 (LWP 5476))]

Thread 2 (Thread 0x7f0d63887910 (LWP 5486)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:220
#1  0x00007f0d8206a462 in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x30cbb70, time=30000) at thread/qwaitcondition_unix.cpp:85
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x30cbb70, time=30000) at thread/qwaitcondition_unix.cpp:159
#3  0x00007f0d820604f2 in QThreadPoolThread::run (this=<value optimized out>) at concurrent/qthreadpool.cpp:140
#4  0x00007f0d82069445 in QThreadPrivate::start (arg=0x30cde30) at thread/qthread_unix.cpp:188
#5  0x00007f0d7b778a04 in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007f0d81a6b7bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f0d84406750 (LWP 5476)):
[KCrash Handler]
#5  0x00007f0d819bf4b5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x00007f0d819c2f50 in *__GI_abort () at abort.c:92
#7  0x00007f0d81dc3cc5 in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:93
#8  0x00007f0d81dc20f6 in __cxxabiv1::__terminate (handler=0x1564) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:38
#9  0x00007f0d81dc2123 in std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:48
#10 0x00007f0d81dc21a6 in __cxa_rethrow () at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:116
#11 0x00007f0d8214ea55 in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:214
#12 0x00007f0d82150ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#13 0x0000000000403f47 in _start ()
The current source language is "auto; currently asm".
The current source language is "auto; currently c".

Reported using DrKonqi
Comment 1 Odd Arild Olsen 2010-01-15 15:55:36 UTC 
Also instantly crashes when I try to edit an old mail and enter the body field
Comment 2 Christophe Marin 2010-03-28 03:10:41 UTC 
Sounds like an installation problem. Please reopen this report and paste a new backtrace if you're able to reproduce this crash with KDE > 4.4.1
Comment 3 Odd Arild Olsen 2010-04-06 13:34:03 UTC 
Created attachment 42526 [details]
New crash information added by DrKonqi

Made a dist-upgrade to packported I guess. KDE version is now 4.4.2. Same thing happens.
Comment 4 Denis Kurz 2017-06-24 00:08:39 UTC 
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 5 Andrew Crouthamel 2018-09-28 02:36:06 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 6 Andrew Crouthamel 2018-10-28 03:30:26 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!