Bug 225913 - Kontact crash after quitting it
Summary: Kontact crash after quitting it
Status: RESOLVED DUPLICATE of bug 185544
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-08 14:36 UTC by Jan Gerrit Marker
Modified: 2010-03-27 22:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Gerrit Marker 2010-02-08 14:36:31 UTC
Application: kontact (4.4 rc2)
KDE Platform Version: 4.3.98 (KDE 4.3.98 (KDE 4.4 RC3)) "release 218"
Qt Version: 4.6.1
Operating System: Linux 2.6.31.8-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

-- Information about the crash:
Kontact is started through the Autostart Systemsettings module (by the way: everything appears there twice, maybe that's important). If I login I get the message that Kontact is already started. There's no tray icon (neither KMail's nor Akregator's one) so it start Kontact, tough. Then suddenly there are two tray icons for KMail and two for Akregator. I close Kontact through Ctrl+Q and the four tray icons disappear. Then the crash dialog with the backtrace appears. This happend at two logins, if I start Kontact through KRunner later everything is normal.

The crash can be reproduced some of the time.

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

Thread 3 (Thread 0x7f763123c910 (LWP 2341)):
#0  0x00007f764965f2cd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f764ebe8662 in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:85
#2  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#3  0x00007f764ebddac9 in QThreadPoolThread::run (this=0x1db9ed0) at concurrent/qthreadpool.cpp:140
#4  0x00007f764ebe7745 in QThreadPrivate::start (arg=0x1db9ed0) at thread/qthread_unix.cpp:248
#5  0x00007f764965a65d in start_thread () from /lib64/libpthread.so.0
#6  0x00007f764d94414d in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f76309e0910 (LWP 2351)):
#0  0x00007f764965f2cd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f764ebe8662 in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:85
#2  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#3  0x00007f764ebddac9 in QThreadPoolThread::run (this=0x16c5230) at concurrent/qthreadpool.cpp:140
#4  0x00007f764ebe7745 in QThreadPrivate::start (arg=0x16c5230) at thread/qthread_unix.cpp:248
#5  0x00007f764965a65d in start_thread () from /lib64/libpthread.so.0
#6  0x00007f764d94414d in clone () from /lib64/libc.so.6
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f76507e37f0 (LWP 2026)):
[KCrash Handler]
#5  0x00007f764ebe2996 in fetchAndAddOrdered (valueToAdd=1, this=<value optimized out>) at ../../src/corelib/arch/qatomic_x86_64.h:164
#6  fetchAndAddAcquire (valueToAdd=1, this=<value optimized out>) at ../../src/corelib/arch/qatomic_x86_64.h:297
#7  QMutex::lock (valueToAdd=1, this=<value optimized out>) at thread/qmutex.cpp:158
#8  0x00007f764ecdaa62 in QCoreApplication::postEvent (receiver=0x16d7350, event=0x7f14b0, priority=0) at kernel/qcoreapplication.cpp:1113
#9  0x00007f764eceb967 in queued_activate (sender=0x16a79a0, signal=<value optimized out>, c=0x1239dc0, argv=0x7fffe9341640, semaphore=0x0) at kernel/qobject.cpp:3155
#10 0x00007f764ecedac2 in QMetaObject::activate (sender=0x16a79a0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x4) at kernel/qobject.cpp:3248
#11 0x00007f764ecf535f in QSingleShotTimer::timerEvent (this=0x16a79a0) at kernel/qtimer.cpp:308
#12 0x00007f764ecea853 in QObject::event (this=0x16a79a0, e=0x7fffe9341de0) at kernel/qobject.cpp:1212
#13 0x00007f764e099c9c in QApplicationPrivate::notify_helper (this=0x643e90, receiver=0x16a79a0, e=0x7fffe9341de0) at kernel/qapplication.cpp:4298
#14 0x00007f764e0a027b in QApplication::notify (this=0x7fffe93421f0, receiver=0x16a79a0, e=0x7fffe9341de0) at kernel/qapplication.cpp:4181
#15 0x00007f764f637ba6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#16 0x00007f764ecdadfc in QCoreApplication::notifyInternal (this=0x7fffe93421f0, receiver=0x16a79a0, event=0x7fffe9341de0) at kernel/qcoreapplication.cpp:704
#17 0x00007f764ed07ac5 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215
#18 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:617
#19 0x00007f764ed04658 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#20 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#21 0x00007f76464f6dee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f76464fa7b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f76464fa8e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f764ed04323 in QEventDispatcherGlib::processEvents (this=0x613810, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00007f764e147dce in QGuiEventDispatcherGlib::processEvents (this=0x1, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f764ecd9712 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#27 0x00007f764ecd9aec in QEventLoop::exec (this=0x7fffe9342130, flags=) at kernel/qeventloop.cpp:201
#28 0x00007f764ecdd83b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#29 0x0000000000403ed7 in _start ()

Reported using DrKonqi
Comment 1 Christophe Marin 2010-03-27 22:11:18 UTC

*** This bug has been marked as a duplicate of bug 185544 ***