Bug 217607

Summary:	akregator forgets read feeds after system crash
Product:	[Applications] akregator	Reporter:	andres.rogers
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	grave	CC:	guysoft, karaluh, marcus, naranek, wrar
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description andres.rogers 2009-12-06 17:55:37 UTC

Version:           4.3.4 (using KDE 4.3.4)
OS:                Linux
Installed from:    Archlinux Packages

I use Akregator always active in the system tray, the problem is when my system crashes or suddenly reboots after startup the news red in the last session are marked as not read (and downloads them again). this really makes difficult to follow the reading because old and new articles as marked as new alike.

the above does not happen when closing akregator before rebooting.

a fix for this behavior should be to instantly writting to the respective file or database that the program uses the news that are read and downloaded not being subject to closing the program session.

Comment 1 Frank Osterfeld 2010-02-06 21:06:10 UTC

*** Bug 219063 has been marked as a duplicate of this bug. ***

Comment 2 Christophe Marin 2010-03-25 23:53:51 UTC

*** Bug 187687 has been marked as a duplicate of this bug. ***

Comment 3 Marcus Meissner 2010-08-12 09:51:18 UTC

also on SUSE, so I guess everwhere.

i really see this as a grave problem

Comment 4 karaluh 2010-09-27 09:57:38 UTC

*** This bug has been confirmed by popular vote. ***

Comment 5 Guy Sheffer 2010-11-22 11:51:57 UTC

Hello,
I thought I might also note that this worked fine in KDE 3. It seems like the bug started only after KDE4. 
Was there any change to the database system during that time?

Comment 6 Andrey Rakhmatullin 2010-12-17 16:10:20 UTC

Note that this bug is applicable to caes when akregator itself crashes (and it does that quite often, at least when compared to other frequently used software).

Comment 7 Denis Kurz 2016-09-24 19:41:21 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 8 Denis Kurz 2017-01-07 22:50:39 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.