Bug 211836

Summary:	kontact died unexpectedly, no interaction
Product:	[Applications] akregator	Reporter:	Joseph Rawson <umeboshi3>
Component:	metakit plugin	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Joseph Rawson 2009-10-25 22:13:09 UTC

Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
I never selected the akgregator icon in kontact.  In previous versions of kontact, akgregator didn't run until it was selected.  I ran kontact all day yesterday without touching akgregator, and this didn't happen.


 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f028e7b8c07 in ?? () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#6  0x00007f028e7ac95c in ?? () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#7  0x00007f028e7bb0cd in ?? () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#8  0x00007f028e7bc1c9 in ?? () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#9  0x00007f028e7b4271 in ?? () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#10 0x00007f028e7bb885 in ?? () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#11 0x00007f028e7bd20b in ?? () from /usr/lib/kde4/akregator_mk4storage_plugin.so
#12 0x00007f028f10961e in Akregator::Article::setStatus(int) () from /usr/lib/kde4/akregatorpart.so
#13 0x00007f028f1174c0 in Akregator::Feed::fetch(bool) () from /usr/lib/kde4/akregatorpart.so
#14 0x00007f028f12ad1c in Akregator::FetchQueue::fetchNextFeed() () from /usr/lib/kde4/akregatorpart.so
#15 0x00007f028f12aef0 in Akregator::FetchQueue::addFeed(Akregator::Feed*) () from /usr/lib/kde4/akregatorpart.so
#16 0x00007f028f1176b2 in Akregator::Feed::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () from /usr/lib/kde4/akregatorpart.so
#17 0x00007f028f1207d0 in Akregator::Folder::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () from /usr/lib/kde4/akregatorpart.so
#18 0x00007f028f180a0a in Akregator::MainWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/kde4/akregatorpart.so
#19 0x00007f02aec5cdf2 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#20 0x00007f02aec57353 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#21 0x00007f02ae0c101d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#22 0x00007f02ae0c907a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#23 0x00007f02af5e70db in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#24 0x00007f02aec47c9c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#25 0x00007f02aec742c6 in ?? () from /usr/lib/libQtCore.so.4
#26 0x00007f02aec70658 in ?? () from /usr/lib/libQtCore.so.4
#27 0x00007f02a7d7712a in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#28 0x00007f02a7d7a988 in ?? () from /lib/libglib-2.0.so.0
#29 0x00007f02a7d7ab3c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#30 0x00007f02aec7039c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0x00007f02ae157f1f in ?? () from /usr/lib/libQtGui.so.4
#32 0x00007f02aec46562 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#33 0x00007f02aec46934 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#34 0x00007f02aec48ba4 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#35 0x0000000000404751 in _start ()

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

Reported using DrKonqi

Comment 1 Dario Andres 2009-10-25 22:48:18 UTC

- If you can reproduce the crash at will (or you experience this regularly), can you install the "kdepim-dbg" package and post a complete backtrace here? Thanks

Comment 2 Joseph Rawson 2009-10-25 23:44:20 UTC

On Sunday 25 October 2009 16:48:19 Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=211836
> 
> 
> Dario Andres <andresbajotierra@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
> - CC|                            |andresbajotierra@gmail.com
>  Component|general                     |akregator
>          AssignedTo|kdepim-bugs@kde.org        
>  |akregator-devel@lists.sourc
> 
>                    |                            |eforge.net
> 
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  2009-10-25
>  22:48:18 --- - If you can reproduce the crash at will (or you experience
>  this regularly), can you install the "kdepim-dbg" package and post a
>  complete backtrace here? Thanks
> 
I selected a bunch of kde*-dbg packages.  Downloading now. :)
I don't know about reproducing the crash, as I wasn't even using kontact when 
it crashed.  I have yet to even touch anything other than kmail through 
kontact.  Once the -dbg packages are installed, I'll restart X and do the same 
thing again. :)

Comment 3 Dario Andres 2009-11-27 17:39:28 UTC


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