Bug 188500

Summary:	Kontact crashes upon close
Product:	[Applications] kontact	Reporter:	Geert Poels <geert.poels>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	andresbajotierra, jtsheldon, kdenis, mstu
Priority:	NOR	Keywords:	triaged
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Geert Poels 2009-03-30 19:49:05 UTC

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

Application: Kontact (kontact), signal SIGABRT
[Current thread is 0 (LWP 7387)]

Thread 2 (Thread 0xb0bdab90 (LWP 7393)):
#0  0xb800f430 in __kernel_vsyscall ()
#1  0xb5a98df1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5d67150 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb5c976ae in ?? () from /usr/lib/libQtCore.so.4
#4  0xb53ce50f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb5aa0a0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4b546c0 (LWP 7387)):
[KCrash Handler]
#6  0xb800f430 in __kernel_vsyscall ()
#7  0xb59ea8a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb59ec268 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb59e372e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb157234c in KMKernel::self () from /usr/lib/libkmailprivate.so.4
#11 0xb164986c in kmcrashHandler () from /usr/lib/libkmailprivate.so.4
#12 0xb6dc363a in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#13 <signal handler called>
#14 0xb800f430 in __kernel_vsyscall ()
#15 0xb59ea8a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#16 0xb59ec268 in abort () from /lib/tls/i686/cmov/libc.so.6
#17 0xb5a2816d in ?? () from /lib/tls/i686/cmov/libc.so.6
#18 0xb5a2e454 in ?? () from /lib/tls/i686/cmov/libc.so.6
#19 0xb5a304b6 in free () from /lib/tls/i686/cmov/libc.so.6
#20 0xb5c91f2d in qFree () from /usr/lib/libQtCore.so.4
#21 0xb5cdbb40 in QString::free () from /usr/lib/libQtCore.so.4
#22 0xb733b5bb in ?? () from /usr/lib/libkcal.so.4
#23 0xb733ec13 in KCal::CalendarLocal::incidenceUpdated () from /usr/lib/libkcal.so.4
#24 0xb730a131 in KCal::IncidenceBase::updated () from /usr/lib/libkcal.so.4
#25 0xb730d4c0 in KCal::Incidence::setRelatedToUid () from /usr/lib/libkcal.so.4
#26 0xb730f066 in KCal::Incidence::setRelatedTo () from /usr/lib/libkcal.so.4
#27 0xb73110d8 in KCal::Incidence::~Incidence () from /usr/lib/libkcal.so.4
#28 0xb731588d in KCal::Event::~Event () from /usr/lib/libkcal.so.4
#29 0xb733b3de in KCal::CalendarLocal::close () from /usr/lib/libkcal.so.4
#30 0xb738fd93 in KCal::ResourceCached::doClose () from /usr/lib/libkcal.so.4
#31 0xb7234f57 in KRES::Resource::close () from /usr/lib/libkresources.so.4
#32 0xb7395dad in KCal::CalendarResources::close () from /usr/lib/libkcal.so.4
#33 0xb7396135 in KCal::CalendarResources::~CalendarResources () from /usr/lib/libkcal.so.4
#34 0xb1d020a4 in KOrg::StdCalendar::~StdCalendar () from /usr/lib/libkorganizer_calendar.so.4
#35 0xb1d03abf in ?? () from /usr/lib/libkorganizer_calendar.so.4
#36 0xb79226ca in ?? () from /usr/lib/libkde3support.so.4
#37 0xb5d883fb in qt_call_post_routines () from /usr/lib/libQtCore.so.4
#38 0xb62433b8 in QApplication::~QApplication () from /usr/lib/libQtGui.so.4
#39 0xb6d5374e in KApplication::~KApplication () from /usr/lib/libkdeui.so.5
#40 0xb6d5aad8 in KUniqueApplication::~KUniqueApplication () from /usr/lib/libkdeui.so.5
#41 0x0804c0f2 in _start ()

Comment 1 Dario Andres 2009-05-08 00:10:12 UTC

If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here?
You need to install the "kdepim-dbg" package
Thanks
This may be related to bug 183318 (bug 177862) / bug 171271

Comment 2 Dario Andres 2009-06-26 16:33:47 UTC

Marking as NEEDSINFO

Comment 3 jtsheldon 2009-07-14 17:25:35 UTC

Here is my output, one item "might" be that I'm "watching" Kontact with gKrellm.

Well, I'm sorry but the copy and paste disappeared, however I do remember that it said there was not output, and then there was some text and again no output.

Comment 4 Vsevolod Krishchenko 2009-07-21 18:34:03 UTC

I have reproduced some Kontact crash in 4.3 RC2. My steps are:
1) Create new user profile.
2) Start Kontact, d nothing and wait until it fully started.
3) Quit it (by pressing X in window title).
4) Kontact crashes with 100% chance.

It works every time.

Comment 5 Denis Kurz 2017-06-24 00:07:36 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 6 Andrew Crouthamel 2018-09-28 02:32: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 7 Andrew Crouthamel 2018-10-28 03:18:28 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!