So, after updating to 5.5.3, akregator has been a mess, and I noticed something that maybe could help with this issue.
A weird bug happened to me causing that, after updating all feeds, all new articles appeared with no date on them (empty column). After a reboot, all the articles I tried to read with an empty date now appear as 07.02.2106 07:28.
The conclusion is that apparently, if there's a problem with setting the date when getting/reading a new article (which seems it should never happen, why not just set the current date then?), for some reason it gets the 07.02.2106 one (that seems like a maximum possible integer value for a timestamp or something, don't you think?).
Hope it helps, this has to be one of the longest running bugs in kdepim, and still unconfirmed for some reason.
So, after updating to 5.5.3, akregator has been a mess, and I noticed something that maybe could help with this issue.
A weird bug happened to me causing that, after updating all feeds, all new articles appeared with no date on them (empty column). After a reboot, all the articles I tried to read with an empty date now appear as 07.02.2106 07:28.
The conclusion is that apparently, if there's a problem with setting the date when getting/reading a new article (which seems it should never happen, why not just set the current date then?), for some reason it gets the 07.02.2106 one (that seems like a maximum possible integer value for a timestamp or something, don't you think?).
Hope it helps, this has to be one of the longest running bugs in kdepim, and still unconfirmed for some reason.