197845 2009-06-25 16:12:58 +0000 Akregator crashes on closing 2009-10-23 17:02:51 +0000 1 1 2 Applications akregator general unspecified Unlisted Binaries Linux RESOLVED DUPLICATE 193780 NOR crash --- 0 xosecalvo pim-bugs-null andresbajotierra 0 oldest_to_newest 781730 0 xosecalvo 2009-06-25 16:12:58 +0000 Application that crashed: akregator Version of the application: 1.4.50 KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) Qt Version: 4.5.0 Operating System: Linux 2.6.28-13-generic i686 Distribution: Ubuntu 9.04 What I was doing when the application crashed: Akregator opens on starttup. I clicked on the window to close it and it crashed. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [KCrash Handler] #6 0xb2fa87ea in Akregator::Feed::unread () from /usr/lib/kde4/akregatorpart.so #7 0xb2fb263b in Akregator::Folder::updateUnreadCount () from /usr/lib/kde4/akregatorpart.so #8 0xb2fb26e2 in Akregator::Folder::slotChildChanged () from /usr/lib/kde4/akregatorpart.so #9 0xb2fb2844 in Akregator::Folder::qt_metacall () from /usr/lib/kde4/akregatorpart.so #10 0xb6105ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb6106932 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0xb2fb06f3 in Akregator::TreeNode::signalChanged () from /usr/lib/kde4/akregatorpart.so #13 0xb2fb0734 in Akregator::TreeNode::nodeModified () from /usr/lib/kde4/akregatorpart.so #14 0xb2fb3119 in Akregator::Folder::removeChild () from /usr/lib/kde4/akregatorpart.so #15 0xb2fb0f40 in Akregator::TreeNode::emitSignalDestroyed () from /usr/lib/kde4/akregatorpart.so #16 0xb2fa98aa in Akregator::Feed::~Feed () from /usr/lib/kde4/akregatorpart.so #17 0xb2fb1c46 in Akregator::Folder::FolderPrivate::~FolderPrivate () from /usr/lib/kde4/akregatorpart.so #18 0xb2fb1d07 in Akregator::Folder::~Folder () from /usr/lib/kde4/akregatorpart.so #19 0xb2fb1c46 in Akregator::Folder::FolderPrivate::~FolderPrivate () from /usr/lib/kde4/akregatorpart.so #20 0xb2fb1d07 in Akregator::Folder::~Folder () from /usr/lib/kde4/akregatorpart.so #21 0xb2fb6ac4 in Akregator::FeedList::setRootNode () from /usr/lib/kde4/akregatorpart.so #22 0xb2fb916e in Akregator::FeedList::~FeedList () from /usr/lib/kde4/akregatorpart.so #23 0xb2fff9d8 in ?? () from /usr/lib/kde4/akregatorpart.so #24 0xb2fa1c28 in ?? () from /usr/lib/kde4/akregatorpart.so #25 0xb60feb25 in qDeleteInEventHandler () from /usr/lib/libQtCore.so.4 #26 0xb61003cb in QObject::event () from /usr/lib/libQtCore.so.4 #27 0xb65cee9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #28 0xb65d719e in QApplication::notify () from /usr/lib/libQtGui.so.4 #29 0xb71f4e8d in KApplication::notify () from /usr/lib/libkdeui.so.5 #30 0xb60efa3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #31 0xb60f0695 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4 #32 0xb60f088d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4 #33 0xb611b7ef in ?? () from /usr/lib/libQtCore.so.4 #34 0xb4e08b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #35 0xb4e0c0eb in ?? () from /usr/lib/libglib-2.0.so.0 #36 0xb4e0c268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #37 0xb611b438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #38 0xb6670365 in ?? () from /usr/lib/libQtGui.so.4 #39 0xb60ee06a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #40 0xb60ee4aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #41 0xb60f0959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #42 0xb65ced17 in QApplication::exec () from /usr/lib/libQtGui.so.4 #43 0x0804f041 in _start () Reported using DrKonqi 781950 1 andresbajotierra 2009-06-26 00:03:49 +0000 Does this happens everytime? If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdepim-dbg" package. Thanks 786297 2 christophe 2009-07-04 13:10:33 +0000 Changing the bug status until we get a useful backtrace (see comment #1). 849452 3 christophe 2009-10-23 17:02:51 +0000 *** This bug has been marked as a duplicate of bug 193780 ***