Bug 234527 - Akregator crash in every login after a suddenly system power off
Summary: Akregator crash in every login after a suddenly system power off
Status: RESOLVED DUPLICATE of bug 201492
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.6.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-16 13:30 UTC by vista killer
Modified: 2010-06-05 16:45 UTC (History)
1 user (show)

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 vista killer 2010-04-16 13:30:01 UTC
Application: akregator (1.6.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-21-generic x86_64
Distribution: Ubuntu lucid (development branch)

-- Information about the crash:
I have always open akregator in my system to see the news from different rss. If i have a suddenly power off to the pc then in every login akregator crash. I have to delete the /home/spiros/.kde/share/apps/akregator/ folder to stop crashing. I have the latest KDE version and i have this problem to Kubuntu 9.10 and to 10.04 with every version of KDE

The crash can be reproduced every time.

 -- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
[KCrash Handler]
#5  QString::fromLatin1_helper (str=0xfee <Address 0xfee out of bounds>, size=-1) at tools/qstring.cpp:3597
#6  0x00007fd8669cbf1d in QString::fromAscii_helper (str=0xfee <Address 0xfee out of bounds>, size=-1) at tools/qstring.cpp:3638
#7  0x00007fd85524c3c7 in QString (this=0x4b8d400, tag=<value optimized out>) at /usr/include/qt4/QtCore/qstring.h:413
#8  Akregator::Backend::FeedStorageMK4Impl::articles (this=0x4b8d400, tag=<value optimized out>) at ../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:234
#9  0x00007fd856df3c72 in Akregator::Feed::loadArticles (this=0x4b8db10) at ../../../akregator/src/feed.cpp:236
#10 0x00007fd856df7804 in Akregator::Feed::fromOPML (e=<value optimized out>, storage=<value optimized out>) at ../../../akregator/src/feed.cpp:174
#11 0x00007fd856e02af5 in Akregator::FeedList::parseChildNodes (this=0x18bcd50, node=<value optimized out>, parent=0x4b8d720) at ../../../akregator/src/feedlist.cpp:237
#12 0x00007fd856e02d46 in Akregator::FeedList::parseChildNodes (this=0x18bcd50, node=<value optimized out>, parent=0x22373c0) at ../../../akregator/src/feedlist.cpp:255
#13 0x00007fd856e02d46 in Akregator::FeedList::parseChildNodes (this=0x18bcd50, node=<value optimized out>, parent=0x20aaad0) at ../../../akregator/src/feedlist.cpp:255
#14 0x00007fd856e02d46 in Akregator::FeedList::parseChildNodes (this=0x18bcd50, node=<value optimized out>, parent=0x1dcde80) at ../../../akregator/src/feedlist.cpp:255
#15 0x00007fd856e03566 in Akregator::FeedList::readFromOpml (this=0x18bcd50, doc=<value optimized out>) at ../../../akregator/src/feedlist.cpp:295
#16 0x00007fd856e3e83b in Akregator::LoadFeedListCommand::Private::handleDocument (this=0x1876840, doc=...) at ../../../akregator/src/loadfeedlistcommand.cpp:68
#17 0x00007fd856e3f2c3 in Akregator::LoadFeedListCommand::Private::doLoad (this=0x1876840) at ../../../akregator/src/loadfeedlistcommand.cpp:173
#18 0x00007fd856e3f692 in Akregator::LoadFeedListCommand::qt_metacall (this=0x1da41c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff0d104250) at ./loadfeedlistcommand.moc:78
#19 0x00007fd866a85e3f in QMetaObject::activate (sender=0x1d8d2e0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3293
#20 0x00007fd866a8d65f in QSingleShotTimer::timerEvent (this=0x1d8d2e0) at kernel/qtimer.cpp:308
#21 0x00007fd866a82a63 in QObject::event (this=0x1d8d2e0, e=0x7fff0d1049b0) at kernel/qobject.cpp:1212
#22 0x00007fd8673e722c in QApplicationPrivate::notify_helper (this=0x17f68e0, receiver=0x1d8d2e0, e=0x7fff0d1049b0) at kernel/qapplication.cpp:4300
#23 0x00007fd8673ed6fb in QApplication::notify (this=0x7fff0d104cb0, receiver=0x1d8d2e0, e=0x7fff0d1049b0) at kernel/qapplication.cpp:4183
#24 0x00007fd8680f2526 in KApplication::notify (this=0x7fff0d104cb0, receiver=0x1d8d2e0, event=0x7fff0d1049b0) at ../../kdeui/kernel/kapplication.cpp:302
#25 0x00007fd866a7306c in QCoreApplication::notifyInternal (this=0x7fff0d104cb0, receiver=0x1d8d2e0, event=0x7fff0d1049b0) at kernel/qcoreapplication.cpp:704
#26 0x00007fd866a9fd42 in QCoreApplication::sendEvent (this=0x17fc100) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#27 QTimerInfoList::activateTimers (this=0x17fc100) at kernel/qeventdispatcher_unix.cpp:603
#28 0x00007fd866a9c824 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#29 0x00007fd860ac58c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0x00007fd860ac9748 in ?? () from /lib/libglib-2.0.so.0
#31 0x00007fd860ac98fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0x00007fd866a9c513 in QEventDispatcherGlib::processEvents (this=0x17c97a0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#33 0x00007fd86749746e in QGuiEventDispatcherGlib::processEvents (this=0xfee, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#34 0x00007fd866a71992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#35 0x00007fd866a71d6c in QEventLoop::exec (this=0x7fff0d104c50, flags=) at kernel/qeventloop.cpp:201
#36 0x00007fd866a75aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#37 0x000000000040971d in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../akregator/src/main.cpp:103

Possible duplicates by query: bug 215161, bug 209845, bug 201492, bug 195176.

Reported using DrKonqi
Comment 1 Maciej Kacper Jagiełło 2010-04-18 14:40:12 UTC
Happened to me a few times when my laptop was tourning itself off from overheating.
For me it was sufficient to delete/rename only the ~/.kde/share/apps/akregator/Archive/archiveindex.mk4 file if I recall correctly (without losing feed archives etc.).
Comment 2 Christophe Marin 2010-06-05 16:45:45 UTC

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