Summary: | Crashes upon startup with akregator: ERROR: Communication problem with akregator, it probably crashed. | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Thorben <tj.trevelyan> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 1.2.4 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Thorben
2006-10-17 17:22:31 UTC
Some apt-get upgrades later and this bug has gone away. It now runs (on its own and in kontact). Qt: 3.3.7 KDE: 3.5.5 Akregator: 1.2.5 I am seeing the same error on my box System: openSUSE 10.2 (i586) KDE: 3.5.7 "release 64.1" akregator 1.2.7 System configuration startup check disabled. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1235933488 (LWP 6325)] [KCrash handler] #9 0xb58405fc in c4_FormatB::Define () from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so #10 0xb5843089 in c4_HandlerSeq::Prepare () from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so #11 0xb5846aa5 in c4_Persist::LoadAll () from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so #12 0xb584b70d in c4_Storage::c4_Storage () from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so #13 0xb582fb06 in Akregator::Backend::FeedStorageMK4Impl::FeedStorageMK4Impl () from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so #14 0xb5831f21 in Akregator::Backend::StorageMK4Impl::archiveFor () from /opt/kde3/lib/kde3/libakregator_mk4storage_plugin.so #15 0xb7f122c8 in Akregator::Feed::loadArticles () from /opt/kde3/lib/libakregatorprivate.so #16 0xb7f13030 in Akregator::Feed::fromOPML () from /opt/kde3/lib/libakregatorprivate.so #17 0xb7f1d805 in Akregator::FeedList::parseChildNodes () from /opt/kde3/lib/libakregatorprivate.so #18 0xb7f1d90c in Akregator::FeedList::parseChildNodes () from /opt/kde3/lib/libakregatorprivate.so #19 0xb7f1dd7e in Akregator::FeedList::readFromXML () from /opt/kde3/lib/libakregatorprivate.so #20 0xb60e0cdc in Akregator::View::loadFeeds () from /opt/kde3/lib/kde3/libakregatorpart.so #21 0xb60dc3ab in Akregator::Part::openFile () from /opt/kde3/lib/kde3/libakregatorpart.so #22 0xb60d9f4c in Akregator::Part::openURL () from /opt/kde3/lib/kde3/libakregatorpart.so #23 0xb60d691b in Akregator::Part::openStandardFeedList () from /opt/kde3/lib/kde3/libakregatorpart.so #24 0xb60d5770 in Akregator::AkregatorPartIface::process () from /opt/kde3/lib/kde3/libakregatorpart.so #25 0xb77dfe77 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4 #26 0xb77e0602 in DCOPClient::send () from /opt/kde3/lib/libDCOP.so.4 #27 0xb77e0c3f in DCOPRef::sendInternal () from /opt/kde3/lib/libDCOP.so.4 #28 0x08050796 in Akregator::Application::newInstance () #29 0xb794fdbd in KUniqueApplication::processDelayed () from /opt/kde3/lib/libkdecore.so.4 #30 0xb7980078 in KUniqueApplication::qt_invoke () from /opt/kde3/lib/libkdecore.so.4 #31 0xb7358f1d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #32 0xb76940ae in QSignal::signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #33 0xb7374ff7 in QSignal::activate () from /usr/lib/qt3/lib/libqt-mt.so.3 #34 0xb737c383 in QSingleShotTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #35 0xb72f99c7 in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #36 0xb72fa791 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #37 0xb79b08d2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #38 0xb72eebd3 in QEventLoop::activateTimers () from /usr/lib/qt3/lib/libqt-mt.so.3 #39 0xb72a8c40 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #40 0xb73107f0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #41 0xb7310686 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #42 0xb72f957f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #43 0x0805025e in main () See also bug 109174, it contains a similar backtrace, but it has been marked as FIXED for two years now. Seems it re-appeared? Hi, I reported this a long time ago, subsequent (debian) dist-upgrade seemed to have fixed it. Sorry that I forget about this report. Thorben On 9 Aug 2007 06:39:07 -0000, Bram Schoenmakers <bramschoenmakers@kde.nl> wrote: [bugs.kde.org quoted mail] |