Bug 260838

Summary: Date column shows incorrect dates
Product: [Applications] akregator Reporter: Joseph Crawford <info>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal    
Priority: NOR    
Version: 1.6.5   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: screenshots

Description Joseph Crawford 2010-12-20 23:14:50 UTC 
Version:           1.6.5 (using KDE 4.5.4) 
OS:                Linux

If you look at the screenshots attached you will see that in Akregator the date of the articles appear to be in the year 2106 rather than 2010 like the websites say.  If you check the RSS source the date is correct as well:

http://microformatique.com/optimus/?uri=dmitry.baranovskiy.com&format=rss

Thanks,
Joseph Crawford

Reproducible: Sometimes

Steps to Reproduce:
tends to happen with different feeds


Expected Results:  
proper dates show

OS: Linux (i686) release 2.6.35-23-generic-pae
Compiler: cc
Comment 1 Joseph Crawford 2010-12-20 23:15:56 UTC 
Created attachment 55116 [details]
screenshots
Comment 2 Christophe Marin 2010-12-21 01:51:10 UTC 
I can't reproduce with this feed.

Note that this feed has errors:

http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fmicroformatique.com%2Foptimus%2F%3Furi%3Ddmitry.baranovskiy.com%26format%3Drss
Comment 3 Joseph Crawford 2010-12-21 15:55:31 UTC 
I will see if i can get it to reproduce today.  I have the same feeds in Thunderbird which do not have these date issues.

Thanks,
Joseph Crawford
Comment 4 Denis Kurz 2016-09-24 19:40:46 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 5 Denis Kurz 2017-01-07 21:46:42 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.