Bug 146775

Summary:	Items marked as read when fetching new feeds
Product:	[Applications] akregator	Reporter:	Alejandro Exojo <suy>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	dev+kde, graham.anderson
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alejandro Exojo 2007-06-14 11:15:34 UTC

Version:           1.2.7 (using KDE 3.5.7, Debian Package 4:3.5.7.dfsg.1-1 (lenny/sid))
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.21-1-amd64

Hi.

Since I upgraded to akregator 3.5.7, some feeds are randomly marked as read, when its status would be unread or new. I haven't discovered yet when this happens, but it is possible that it does both closing and starting again akregator, and when new feeds are fetched.

I realized that this way: I read some feeds only weekly, or monthly, but I download them everyday. When I was about to read Planet KDE, I noticed that some entries are marked as read, but I didn't remember clicking on them. I then checked some feeds that I'm 100% sure that I haven't read in weeks, maybe months, and I see that from the present day to 21st of May, the entries are randomly unread, and randomly read, but the ones older than this date, are all unread (as I expected).

According to my log, day 23 I upgraded to akregator 3.5.7, so I'm guessing this might be the problem.

Thanks in advance, and any suggestions are welcome!

Comment 1 Alejandro Exojo 2007-06-23 13:39:31 UTC

FWIW, I want to add that I downgraded only akregator to 3.5.6, and since then, I don't lose feeds. :)

Regards.

Comment 2 Oliver Henshaw 2007-11-30 21:26:36 UTC

I too have a problem where items are wrongly marked as read. It seems to happen to random entries. One of the triggers seems to be restarting akgregator, either from a complete close or from kde's sessesion restore - but it happens at other times too.

I have a large archive and over a hundred unread articles (which makes it particularly annoying when the articles that disappear are part of the backlog).

I'd like to get to the bottom of this, if possible.

Comment 3 Imri Goldberg 2007-12-11 13:28:37 UTC

I'm having the same problem with KDE 3.5.8, akregator 1.2.7, on my ubuntu machine.

This is especially annoying, as I depend on the unread items for future reference.

Comment 4 Hernan Giovagnoli 2008-03-11 01:15:27 UTC

Same as Imri, I do have the problem on Kubuntu 7.10, using Akregator 1.2.7 on KDE 3.5.8

It's a simple thing, but it's quite annoying. Even if I change the read items as unread (as they are supposed to be) they keep changing.

Comment 5 Graham Anderson 2009-09-02 21:22:17 UTC

This bug is still plagues Akgregator and we are now on 1.5.1 in KDE 4.3.1

Comment 6 Alejandro Exojo 2010-05-10 19:08:37 UTC

Hi.

I've tried to reproduce this bug in a recent akregator version (4.4 branch) and I could not reproduce it. I don't know if it's gone for sure, so it will be nice if somebody can comment on it too.

Thanks.

Comment 7 Alejandro Exojo 2010-05-10 19:10:36 UTC

Hi.

I've tried to reproduce this bug in a recent akregator version (4.4 branch) and I could not reproduce it. I don't know if it's gone for sure, so it will be nice if somebody can comment on it too.

Thanks.

Comment 8 Graham Anderson 2010-05-10 19:47:37 UTC

This bug still remains in the 4.4.3 release. I can reproduce it at will.

1. Select a feed with new entries
2. Select "fetch all feeds"
3. Watch existing unread entries get marked as read.

It happens also on every automatic fetch of feed updates.

Comment 9 Frank Steinmetzger 2012-08-13 09:59:45 UTC

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

Comment 10 Frank Steinmetzger 2012-08-13 10:01:33 UTC

I too reported this problem in 2008, but haven't had it for a long time now. How about you others? Would you consider it fixed?

Comment 11 Christophe Marin 2012-09-09 20:34:36 UTC

Let's close this report then. Thanks for the feedback.