All articles are marked unread and all lables are lost after akregator crash

[Pavel Malyshev]

Binary package hint: kdepim

All the time akregator crashes all articles that I have read marks unread again. All marks that I have set on articles are lost. All articels that were fetched but could not be fetched after crash are lost.
The only one storage engine in akregator is metakit for now and it seems like storage is being saved only at exit. It seems like storage is not being synced while program is running and that is really strange.

So if you have some reproducable crash you can fetch new articles, mark some of them as important, mark all of them as read and then force akregator to crash. After restart you will see that all your changes are lost.
This bug is really annoying when akregator runs for days.

This bug was there for a long time.
Now I'm using lucid and tried 4:4.4.2-0ubuntu5 and 4:4.4.3-0ubuntu1~ppa1 from kubuntu-ppa. All of them have this bug.

[Pavel Malyshev (afunix)]

7 months passed without any comment!

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Matt Dittloff (mattdittloff)]

I figured out a bad workaround for this.

Use KAlarm or some other scheduling program to run the following command once a day:

killall akregator
akregator --hide-mainwindow

It causes akregator to close and then restart, saving the current state. It doesn't fix the problem, but it at least limits the damage caused by it.

[Matt Dittloff (mattdittloff)]

This bug is fixed. Akregator now has a Restore Session feature for after it has crashed.

[Rohan Garg (rohangarg)]

Comment #4 mentions that it's fixed, changing status to fix released.