Version: (using KDE 4.2.4) Installed from: Fedora RPMs If Akregator (or Kontact) crashes, Akregator loses all feeds and read/unread state since the last successful quit. It should at least dump to the database on every update of feeds, otherwise weeks of feeds can be lost if something goes wrong.
I can confirm this with KDE 4.3.2 on Ubuntu: https://bugs.launchpad.net/bugs/460756
This is very similar to Bug 187687 "When there is a crash read links are not stored. ", also Bug 210408 "problems with session saving / restoration" sounds related.
Also Bug 196633 and Bug 185507 are related, maybe we can duplicate most of these to this one. I'm using the following command to ask Akregator to save the current state (all in one line): dbus-send --session --dest=org.kde.akregator --type=method_call /Akregator org.kde.akregator.part.saveSettings this will use d-bus to instruct Akregator to persist its database, at least it seems to work for me. Unfortunately you cannot run this workaround in a cron-job periodically as it requires access to the d-bus session, which you don't have inside cron. But you can probably add it to some X-shutdown script and make it work this way.
What is Storage::autoCommit() used for? It looks like it's only checked on close() but isn't this only called on the shutdown path where you'd want to always commit to the database?
(In reply to comment #3) > Unfortunately you cannot run this workaround in a cron-job periodically as it > requires access to the d-bus session, which you don't have inside cron. As a workaround I use a simple wrapper that harvests DBUS_SESSION_BUS_ADDRESS from environment of existsing kde processes (via /proc) - with that you can call dbus from cronjob. See http://www.mail-archive.com/debian-kde@lists.debian.org/msg30421.html
Akregator v1.6.5 Besides loosing the read/unread information (which is very annoying) it also looses the settings which columns to display (title/feed/author/date). Also the severity of this bug should not be "wishlist" but "normal" to its degrade of function during specified conditions.
This issue is still present in Akregator 5.5.3.
Regarding my previous comment, I lost a lot of articles after an uptime of about 10 days and a crash of Akregator during startup (after a reboot). I've been monitoring the archived feeds since then, but they seem to be saved correctly after each fetch.
It seems Akregator (5.7.1) stops saving the feed data after a new feed is added.