Bug 259660

Summary:	Closing Kontact
Product:	[Applications] korganizer	Reporter:	Chris <crglasoe>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	anmeldungen
Priority:	NOR
Version:	4.4.5
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Chris 2010-12-12 23:00:21 UTC

Application: kontact (4.4.5)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 3"
Qt Version: 4.7.1
Operating System: Linux 2.6.34.7-0.5-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
Closed Kontact.  Nothing else was running.  I really cannot add any additional information because that is what happened.  I closed Kontact and got the bug report.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fac91909760 (LWP 3131))]

Thread 2 (Thread 0x7fac6c192710 (LWP 8908)):
#0  0x00007fac89d5b709 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fac8fd67072 in wait (this=<value optimized out>, mutex=0x1c47fb0, time=30000) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x1c47fb0, time=30000) at thread/qwaitcondition_unix.cpp:160
#3  0x00007fac8fd5ce98 in QThreadPoolThread::run (this=0x7fac640b0a80) at concurrent/qthreadpool.cpp:140
#4  0x00007fac8fd66a1e in QThreadPrivate::start (arg=0x7fac640b0a80) at thread/qthread_unix.cpp:285
#5  0x00007fac89d56a4f in start_thread () from /lib64/libpthread.so.0
#6  0x00007fac8eaac82d in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fac91909760 (LWP 3131)):
[KCrash Handler]
#5  0x00007fac6edb3efe in FreeBusyManager::publishFreeBusy (this=0x1c2a6e0) at /usr/src/debug/kdepim-4.4.4/korganizer/freebusymanager.cpp:330
#6  0x00007fac8fe65999 in QObject::event (this=0x1c2a6e0, e=<value optimized out>) at kernel/qobject.cpp:1175
#7  0x00007fac8f20fcd4 in QApplicationPrivate::notify_helper (this=0x63d740, receiver=0x1c2a6e0, e=0x7fff8572b750) at kernel/qapplication.cpp:4445
#8  0x00007fac8f2181ca in QApplication::notify (this=<value optimized out>, receiver=0x1c2a6e0, e=0x7fff8572b750) at kernel/qapplication.cpp:4324
#9  0x00007fac90751c06 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#10 0x00007fac8fe51e2c in QCoreApplication::notifyInternal (this=0x7fff8572bb10, receiver=0x1c2a6e0, event=0x7fff8572b750) at kernel/qcoreapplication.cpp:732
#11 0x00007fac8fe7f658 in sendEvent (this=0x64d800) at kernel/qcoreapplication.h:215
#12 QTimerInfoList::activateTimers (this=0x64d800) at kernel/qeventdispatcher_unix.cpp:618
#13 0x00007fac8fe7c3b4 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#14 0x00007fac87a19a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#15 0x00007fac87a1a270 in ?? () from /usr/lib64/libglib-2.0.so.0
#16 0x00007fac87a1a510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#17 0x00007fac8fe7ca8f in QEventDispatcherGlib::processEvents (this=0x6132b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#18 0x00007fac8f2b4eae in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#19 0x00007fac8fe51262 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#20 0x00007fac8fe51475 in QEventLoop::exec (this=0x7fff8572ba60, flags=...) at kernel/qeventloop.cpp:201
#21 0x00007fac8fe558db in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#22 0x000000000040417e in main (argc=3, argv=0x7fff8572c0f8) at /usr/src/debug/kdepim-4.4.4/kontact/src/main.cpp:224

Reported using DrKonqi

Comment 1 Christophe Marin 2010-12-31 00:35:41 UTC

*** Bug 261672 has been marked as a duplicate of this bug. ***

Comment 2 Christophe Marin 2011-02-18 00:03:31 UTC

*** Bug 266571 has been marked as a duplicate of this bug. ***

Comment 3 Christophe Marin 2011-05-21 18:26:42 UTC

*** Bug 273805 has been marked as a duplicate of this bug. ***

Comment 4 Jan 2011-09-22 22:05:31 UTC

Created attachment 63868 [details]
New crash information added by DrKonqi

korganizer (4.4.10) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2

Using a remote calendar

-- Backtrace (Reduced):
#6  0x00007fd34c3e0b83 in FreeBusyManager::publishFreeBusy (this=0x2d6fd80) at ../../korganizer/freebusymanager.cpp:330
#7  0x00007fd34a7871c9 in QObject::event (this=0x2d6fd80, e=<value optimized out>) at kernel/qobject.cpp:1190
#8  0x00007fd34b12e9f4 in QApplicationPrivate::notify_helper (this=0x2568000, receiver=0x2d6fd80, e=0x7fffc809ec10) at kernel/qapplication.cpp:4462
#9  0x00007fd34b1333ba in QApplication::notify (this=<value optimized out>, receiver=0x2d6fd80, e=0x7fffc809ec10) at kernel/qapplication.cpp:4341
#10 0x00007fd34d392796 in KApplication::notify (this=0x7fffc809eec0, receiver=0x2d6fd80, event=0x7fffc809ec10) at ../../kdeui/kernel/kapplication.cpp:311

Comment 5 Denis Kurz 2016-09-24 18:51:48 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 6 Denis Kurz 2017-01-07 22:49:26 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.