Bug 240196

Summary: Kontact crashed after start
Product: [Applications] kontact Reporter: Frans Leerink <f.leerink>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Frans Leerink 2010-05-31 10:51:49 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 2.6.31.12-0.2-desktop i686
Distribution: "openSUSE 11.2 (i586)"

What I was doing when the application crashed:
Hello,

I have recreated the crash and tried to improve debug info  by adding debuginfo packages. But still I see debug lines with ?? for:
    -  libglib-2.0.so.0
    -  libQtGui.so.4
    -  akregatorpart.so
Which debuginfo packages should I add.

The details are the same as from bug report 240154

Regards,  Frans

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0xb6203a81 in memcpy () from /lib/libc.so.6
#7  0xb00183dc in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#8  0xb000bc51 in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#9  0xb000be84 in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#10 0xb001cddb in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#11 0xb00198df in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#12 0xb001f057 in ftell () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#13 0xb0135620 in Akregator::Article::setStatus(int) () from /usr/lib/kde4/akregatorpart.so
#14 0xb01356c8 in Akregator::Article::setDeleted() () from /usr/lib/kde4/akregatorpart.so
#15 0xb013c1dc in ?? () from /usr/lib/kde4/akregatorpart.so
#16 0xb013c406 in ?? () from /usr/lib/kde4/akregatorpart.so
#17 0xb6ecf864 in QMetaObject::activate (sender=0x8a362a8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#18 0xb6ed0585 in QMetaObject::activate (sender=0x8a362a8, m=0xb6fab908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#19 0xb6ed4b25 in QSingleShotTimer::timeout (this=0x8a362a8) at .moc/release-shared/qtimer.moc:76
#20 0xb6ed4c5c in QSingleShotTimer::timerEvent (this=0x8a362a8) at kernel/qtimer.cpp:298
#21 0xb6ec951b in QObject::event (this=0x8a362a8, e=0xbfab0be4) at kernel/qobject.cpp:1075
#22 0xb64ff8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#23 0xb650734e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#24 0xb73fc521 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#25 0xb6eb932e in QCoreApplication::notifyInternal (this=0xbfab0f34, receiver=0x8a362a8, event=0xbfab0be4) at kernel/qcoreapplication.cpp:610
#26 0xb6ee8356 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 0xb6ee5325 in timerSourceDispatch (source=0x8075170) at kernel/qeventdispatcher_glib.cpp:184
#29 idleTimerSourceDispatch (source=0x8075170) at kernel/qeventdispatcher_glib.cpp:231
#30 0xb48074c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#31 0xb480ad98 in ?? () from /usr/lib/libglib-2.0.so.0
#32 0xb480aebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#33 0xb6ee5011 in QEventDispatcherGlib::processEvents (this=0x80541c0, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#34 0xb65a129a in ?? () from /usr/lib/libQtGui.so.4
#35 0xb6eb798d in QEventLoop::processEvents (this=0xbfab0e94, flags=) at kernel/qeventloop.cpp:149
#36 0xb6eb7dd9 in QEventLoop::exec (this=0xbfab0e94, flags=...) at kernel/qeventloop.cpp:201
#37 0xb6eba270 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#38 0xb64ff774 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#39 0x0804b546 in _start ()

This bug may be a duplicate of or related to bug 240154

Reported using DrKonqi
Comment 1 Christophe Marin 2010-06-06 16:31:37 UTC

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