Bug 191645

Summary:	Akregator should store feed data in SQLite database
Product:	[Applications] akregator	Reporter:	Artem S. Tashkinov <aros>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	osterfeld
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	One of broken feeds

Description Artem S. Tashkinov 2009-05-05 06:00:39 UTC

Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Fedora RPMs

Recently my Akregator hang for no obvious reasons I could only kill it via -KILL signal.

Right now one my feeds files is broken to the point Akregator 100% hangs when I try to run it. There are no tools for feed data files recovery, as such I strongly suggest switching to SQLite backend.

I can provide you a feed file in question (it's actually three files).

This bug status is not CRASH but the application is totally unusable.

Comment 1 Artem S. Tashkinov 2009-05-05 06:22:49 UTC

Created attachment 33358 [details]
One of broken feeds

For two feeds I've lost 99.99% of past articles - they are either garbage or empty having 1970-01-01 05:00 date.

Comment 2 Artem S. Tashkinov 2009-05-05 06:29:04 UTC

Actually I've got as many as six feeds lost. Their respective data files are all broken - almost all articles are lost. :(

Comment 3 Frank Osterfeld 2009-05-05 10:10:22 UTC

The issues with metakit storage will be history when we switch to using Akonadi, which will hopefully happen for 4.4.

Comment 4 Artem S. Tashkinov 2009-05-06 06:25:16 UTC

Is there currently a way to recover broken articles files? It seems like when I delete those broken articles Akregator does nothing and at each new start it shows them again (not to mention it takes over 5 minutes to start with 100% CPU usage).

Comment 5 Frank Osterfeld 2009-05-14 12:16:56 UTC

no, one has to delete/move the broken files (or just all of them) from ~/.kde/share/apps/akregator/Archive 

See also bug 116482

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