Bug 198756 - akregator crashed after I added a rss feed
Summary: akregator crashed after I added a rss feed
Status: RESOLVED DUPLICATE of bug 193963
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-03 11:25 UTC by Jan
Modified: 2009-07-04 13:17 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 2009-07-03 11:25:51 UTC
Application that crashed: akregator
Version of the application: 1.4.50
KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1)) "release 139"
Qt Version: 4.5.2
Operating System: Linux 2.6.27.23-0.1-pae i686
Distribution: "openSUSE 11.1 (i586)"

What I was doing when the application crashed:
After i klicked on the rss button in the right corner of the konqueror, akregator started and crashed moments later.

 -- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
[Current thread is 1 (Thread 0xb45ff700 (LWP 11407))]

Thread 2 (Thread 0xb139eb90 (LWP 11410)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6960f62 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb69c055c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0xb69b5b96 in ?? () from /usr/lib/libQtCore.so.4
#4  0xb69bf572 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb695d1b5 in start_thread () from /lib/libpthread.so.0
#6  0xb5cb13be in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb45ff700 (LWP 11407)):
[KCrash Handler]
#6  Akregator::Folder::insertChild (this=0x0, node=0x830afc0, after=0x0) at /usr/include/QtCore/qlist.h:87
#7  0xb2b53df4 in Akregator::CreateFeedCommand::Private::doCreate (this=0x838de78) at /usr/src/debug/kdepim-4.2.95/akregator/src/createfeedcommand.cpp:123
#8  0xb2b540b8 in Akregator::CreateFeedCommand::qt_metacall (this=0x838e0f0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbff7ae48)
    at /usr/src/debug/kdepim-4.2.95/build/akregator/src/createfeedcommand.moc:66
#9  0xb6ac9788 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#10 0xb6aca412 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#11 0xb6acf5b7 in ?? () from /usr/lib/libQtCore.so.4
#12 0xb6acf6dc in ?? () from /usr/lib/libQtCore.so.4
#13 0xb6ac472f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#14 0xb5f897fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#15 0xb5f91aee in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb709a10d in KApplication::notify (this=0xbff7b590, receiver=0x838e7e0, event=0xbff7b2f0) at /usr/src/debug/kdelibs-4.2.95/kdeui/kernel/kapplication.cpp:302
#17 0xb6ab416b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#18 0xb6ae35f6 in ?? () from /usr/lib/libQtCore.so.4
#19 0xb6adf980 in ?? () from /usr/lib/libQtCore.so.4
#20 0xb4c0b9c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb4c0f083 in ?? () from /usr/lib/libglib-2.0.so.0
#22 0xb4c0f241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb6adf8d8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#24 0xb6029cc5 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb6ab278a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0xb6ab2bd2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb6ab5079 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#28 0xb5f89677 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#29 0x0804f091 in main (argc=137945328, argv=0x0) at /usr/src/debug/kdepim-4.2.95/akregator/src/main.cpp:115

Reported using DrKonqi
Comment 1 Christophe Marin 2009-07-04 13:17:53 UTC

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