Bug 317344 - feeds with date in 2106
Summary: feeds with date in 2106
Status: RESOLVED DUPLICATE of bug 256034
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.10.2
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-25 18:03 UTC by ed.shornock
Modified: 2013-12-28 14:13 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
The year 2106 (86.16 KB, image/png)
2013-04-03 00:17 UTC, ed.shornock
Details
another 2106 example (177.86 KB, image/png)
2013-04-03 00:22 UTC, ed.shornock
Details
Another 2106 (185.65 KB, image/png)
2013-06-07 03:12 UTC, Andrey
Details
Test/demo RSS document (910 bytes, application/xml)
2013-08-27 16:44 UTC, mel
Details
image of the date problem. (153.22 KB, image/png)
2013-12-11 20:52 UTC, Isaque Galdino
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ed.shornock 2013-03-25 18:03:29 UTC
Akregator 1.6.6
Debian unstable

A couple of my feeds have entries with timestamps of "07.02.2016 08:28". 

Googling I've found this problem reported at https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/982210 and bug 166721 which is marked as resolved.

I have not tried removing my akregator configs to start over but can do so if needed. I can also provide the feeds that I experience this issue with, if it'd be of use.


Reproducible: Didn't try
Comment 1 Allen Winter 2013-04-02 23:49:14 UTC
so a couple of your feeds have correctly formatted ISO dates, but those dates are in the future.
interesting.  wonder how that happens

the fix in bug 166724 was for handling improperly formatted ISO dates, which is not the case here.

I suppose we could say.. if the date is valid and a future date, then use today's date.

even so.. this is a strange situation.
Comment 2 ed.shornock 2013-04-03 00:17:03 UTC
Created attachment 78585 [details]
The year 2106

A screenshot of the problem.
Comment 4 ed.shornock 2013-04-03 00:22:30 UTC
Created attachment 78586 [details]
another 2106 example
Comment 5 ed.shornock 2013-04-11 15:44:52 UTC
BTW, I've since updated to 4.10.2 and I still see the problem with these same feeds.
Comment 6 ed.shornock 2013-04-23 13:19:14 UTC
I deleted ~/.kde/share/apps/akregator/Archive/* after making a backup (in case the backup would be of use).

The dates are all normal at present.
Comment 7 Andrey 2013-06-07 03:09:23 UTC
Confirm this bug on KDE 4.10.3, Gentoo GNU/Linux amd64.

I tried to delete feeds with date 2106, but they spring up again and again :(
Comment 8 Andrey 2013-06-07 03:12:17 UTC
Created attachment 80370 [details]
Another 2106
Comment 9 mel 2013-08-27 16:44:56 UTC
Created attachment 81972 [details]
Test/demo RSS document

After some testing, I've discovered that this has *nothing* to do with dates in the feed! The cause (or at least *a* cause) of the issue appears to be somehow unexpected characters in the GUID field of an RSS feed item.
I've personally experienced this when a URL is used as the GUID, and that URL includes a non-ASCII hyphen or such. I see EN DASH (U+2013) quite often.

Add the attached RSS document as a feed:
1. Fetch feed -> The bugged item appears as normal in Akregator.
2. Quit Akregator
3. Re-open Akregator -> The feed and items appear normal
4. Fetch feed -> A *duplicate* of the bugged item shows up, with the date " 01:00" (may vary by timezone?) - including the leading space.
5. Quit Akregator
6. Re-open Akregator -> The bugged item appears just once in the feed, but at the top of the list with a date of: "2106-02-07 07:28" (always the same, but may vary by timezone?)
7. Goto #4

Deleting the item/s from the feed will just restart the process the next time Akregator is restarted, and the feed is fetched.

FYI:
Akregator Version 1.6.6
Using KDE Development Platform 4.8.4 (4.8.4)
Comment 10 Isaque Galdino 2013-12-11 18:35:03 UTC
I have this issue in KDE 4.11.3 (openSuse 13.1) as well.
I'll add a screenshot.
Comment 11 Isaque Galdino 2013-12-11 20:52:09 UTC
Created attachment 84051 [details]
image of the date problem.
Comment 12 Christoph Feck 2013-12-28 14:13:18 UTC

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