Bug 165227 - Kontact crash after first attempt to load new RSS feed.
Summary: Kontact crash after first attempt to load new RSS feed.
Status: RESOLVED DUPLICATE of bug 158835
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-28 19:51 UTC by Fry
Modified: 2008-06-29 02:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Fry 2008-06-28 19:51:15 UTC 
Version:           Kontact from KDE4 (using KDE 4.0.83)
Installed from:    Ubuntu Packages
OS:                Linux

After adding my first new RSS feed (slashdot) to akregator in kontact, kontact crashed when I attempted to read the first newly loaded post from slashdot.

Backtrace: 
Application: Kontact (kontact), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb4e71940 (LWP 10517)]
[New Thread 0xb0fbcb90 (LWP 10560)]
[KCrash handler]
#6  0xb7fc1410 in __kernel_vsyscall ()
#7  0xb6c05085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6c06a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb6bfe10e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb04fccf2 in Akregator::ArticleModel::Private::articlesUpdated ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#11 0xb04fd035 in Akregator::ArticleModel::qt_metacall ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#12 0xb789b4f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb789bbc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb0507169 in Akregator::TreeNode::signalArticlesUpdated ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#15 0xb0507442 in Akregator::TreeNode::qt_metacall ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#16 0xb0508cca in Akregator::Folder::qt_metacall ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#17 0xb789b4f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb789bbc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb0507169 in Akregator::TreeNode::signalArticlesUpdated ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#20 0xb050003b in Akregator::Feed::doArticleNotification ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#21 0xb05072cc in Akregator::TreeNode::setNotificationMode ()
   from /usr/lib/kde4/lib/kde4/akregatorpart.so
#22 0xb04f709d in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#23 0xb04f71e3 in ?? () from /usr/lib/kde4/lib/kde4/akregatorpart.so
#24 0xb789b4f9 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#25 0xb789bbc2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#26 0xb78a2037 in ?? () from /usr/lib/libQtCore.so.4
#27 0xb78a215c in ?? () from /usr/lib/libQtCore.so.4
#28 0xb7896c9a in QObject::event () from /usr/lib/libQtCore.so.4
#29 0xb6f56c0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#30 0xb6f5b799 in QApplication::notify () from /usr/lib/libQtGui.so.4
#31 0xb7d17d93 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#32 0xb78866a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#33 0xb78b41a1 in ?? () from /usr/lib/libQtCore.so.4
#34 0xb78b1a40 in ?? () from /usr/lib/libQtCore.so.4
#35 0xb5745bf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#36 0xb5748e5e in ?? () from /usr/lib/libglib-2.0.so.0
#37 0xb57493ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#38 0xb78b1f98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#39 0xb6fea195 in ?? () from /usr/lib/libQtGui.so.4
#40 0xb788592d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#41 0xb7885abd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#42 0xb7887d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#43 0xb6f56567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#44 0x0804b2ca in _start ()
#0  0xb7fc1410 in __kernel_vsyscall ()
Comment 1 FiNeX 2008-06-28 20:16:15 UTC 
"no debugging symbols found" means that the backtrace is not useful. If you can reproduce the crash, you should install the debug enabled packages before providing again the backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks a lot!!!
Comment 2 Fry 2008-06-28 20:51:19 UTC 
Hi, not to be brusque, but there is a debug trace at the end.
I included the (no debugging symbols found) bit on the off chance that the number of them might be helpful.

Thanks for your speedy reply.
-Fry-
Comment 3 Christophe Marin 2008-06-29 02:19:39 UTC 

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