Bug 240154 - Kontact crashed while shutting down and crashed again while starting it up after system start
Summary: Kontact crashed while shutting down and crashed again while starting it up af...
Status: RESOLVED DUPLICATE of bug 116482
Alias: None
Product: kontact
Classification: Applications
Component: akregator (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: aKregator haxx0rz
: 240196 (view as bug list)
Depends on:
Reported: 2010-05-30 22:48 UTC by Frans Leerink
Modified: 2010-06-06 16:31 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Kontact crash due to reenabeling Feeds and start using feeds application (3.81 KB, application/octet-stream)
2010-06-01 16:19 UTC, Frans Leerink

Note You need to log in before you can comment on or make changes to this bug.
Description Frans Leerink 2010-05-30 22:48:55 UTC
Application that crashed: kontact
Version of the application: 4.3.5
KDE Version: 4.3.5 (KDE 4.3.5) "release 0"
Qt Version: 4.5.3
Operating System: Linux i686
Distribution: "openSUSE 11.2 (i586)"

What I was doing when the application crashed:

Kontact crashed while shutting down and Kontact crashed again while starting up after system start. This started to happen after a system freeze while I was downloading a PDF document with Okular. I had to push the power button to bring the system down. I started my System and than Kontact what triggered a Kontact crash. Due to the bug 2023..  -high CPU consumption Xorg and plasma-desktop-  I had to start Kontact again and than shutdown and restart the the system and as a result Kontact, but this time Kontact crashed  during shutdown ans crashed again during the next start after the system was started again

Regards,   Frans

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

Thread 2 (Thread 0xaf549b70 (LWP 2796)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb4cad0c2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb62a92d4 in pthread_cond_timedwait () from /lib/libc.so.6
#3  0xb6e006dc in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:85
#4  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#5  0xb6df5bc2 in QThreadPoolThread::run (this=0x89d0fe0) at concurrent/qthreadpool.cpp:140
#6  0xb6dff623 in QThreadPrivate::start (arg=0x89d0fe0) at thread/qthread_unix.cpp:188
#7  0xb4ca86e5 in start_thread () from /lib/libpthread.so.0
#8  0xb4ca8600 in ?? () from /lib/libpthread.so.0

Thread 1 (Thread 0xb3e30920 (LWP 2768)):
[KCrash Handler]
#6  0xb6240a81 in memcpy () from /lib/libc.so.6
#7  0xb00553dc in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#8  0xb0048c51 in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#9  0xb0048e84 in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#10 0xb0059ddb in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#11 0xb00568df in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#12 0xb005c057 in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#13 0xb0172620 in Akregator::Article::setStatus(int) () from /usr/lib/kde4/akregatorpart.so
#14 0xb01726c8 in Akregator::Article::setDeleted() () from /usr/lib/kde4/akregatorpart.so
#15 0xb01791dc in ?? () from /usr/lib/kde4/akregatorpart.so
#16 0xb0179406 in ?? () from /usr/lib/kde4/akregatorpart.so
#17 0xb6f0c864 in QMetaObject::activate (sender=0x8a21688, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#18 0xb6f0d585 in QMetaObject::activate (sender=0x8a21688, m=0xb6fe8908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#19 0xb6f11b25 in QSingleShotTimer::timeout (this=0x8a21688) at .moc/release-shared/qtimer.moc:76
#20 0xb6f11c5c in QSingleShotTimer::timerEvent (this=0x8a21688) at kernel/qtimer.cpp:298
#21 0xb6f0651b in QObject::event (this=0x8a21688, e=0xbfaebb44) at kernel/qobject.cpp:1075
#22 0xb653c8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#23 0xb654434e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#24 0xb7439521 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#25 0xb6ef632e in QCoreApplication::notifyInternal (this=0xbfaebe94, receiver=0x8a21688, event=0xbfaebb44) at kernel/qcoreapplication.cpp:610
#26 0xb6f25356 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#27 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:594
#28 0xb6f22325 in timerSourceDispatch (source=0x8075170) at kernel/qeventdispatcher_glib.cpp:184
#29 idleTimerSourceDispatch (source=0x8075170) at kernel/qeventdispatcher_glib.cpp:231
#30 0xb48444c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#31 0xb4847d98 in ?? () from /usr/lib/libglib-2.0.so.0
#32 0xb4847ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#33 0xb6f22011 in QEventDispatcherGlib::processEvents (this=0x80541c0, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#34 0xb65de29a in ?? () from /usr/lib/libQtGui.so.4
#35 0xb6ef498d in QEventLoop::processEvents (this=0xbfaebdf4, flags=) at kernel/qeventloop.cpp:149
#36 0xb6ef4dd9 in QEventLoop::exec (this=0xbfaebdf4, flags=...) at kernel/qeventloop.cpp:201
#37 0xb6ef7270 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#38 0xb653c774 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#39 0x0804b546 in _start ()

Reported using DrKonqi
Comment 1 Frans Leerink 2010-05-30 23:02:15 UTC

The bug I am referring to was 232047 -- Sometimes very high CPU-Consumption by XOrg and plasma-desktop 49-53% resp. 41-43%

My system is now basically not useable due to high CPU-load or missing Kontact

Any idea how to solve this problem.

Regards,  Frans
Comment 2 Frans Leerink 2010-06-01 16:19:21 UTC
Created attachment 47561 [details]
Kontact crash due to reenabeling Feeds and start using feeds application
Comment 3 Frans Leerink 2010-06-01 16:22:20 UTC

Further investigation learned me the following. This crash of Kontact happened allways during shutdown of the system while Kontact was running and allways during the 1st start of Kontact after the system was started up. The subsequent start of Kontact was possible without crash but resulted in the bug 232047 -- Sometimes very high CPU-Consumption by XOrg and plasma-desktop 49-53% resp. 41-43%

I have now found out that I can suppress the crashing by disabeling Feeds in Kontact/Summary/Settings/Configure Kontact/Feeds. As soon as I enable it again and go to the Feeds application Kontact crash again. I have saved the crash report abd will add it as an attachment.  

Regards,  Frans
Comment 4 Christophe Marin 2010-06-06 16:30:54 UTC

*** This bug has been marked as a duplicate of bug 116482 ***
Comment 5 Christophe Marin 2010-06-06 16:31:37 UTC
*** Bug 240196 has been marked as a duplicate of this bug. ***