Discussion:
[Bug 256034] Feed content is displayed with date 07.02.2106 07:28
dmatt
2012-01-21 11:56:30 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034


dmatt <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com




--- Comment #4 from dmatt <xdarkmatter gmail com> 2012-01-21 11:56:30 ---
I have seen this issue repeated with Kubuntu 11.04 and 11.10. I noticed it only
happens during initial feed fetching (and not consistently for all feeds) after
fresh install. I always press "Fetch all feeds" button. This might be similar
situation to adding few new feeds at once and consistent with bug reported.

I did fresh install of Kubuntu 11.10 64bit with subsequent update 2 days ago
(so Akregator from KDE 4.7.3 is concerned). Examples of feeds behaviour:
http://www.kde.org/dotkdeorg.rdf - 9 items fetched, all with wrong date
2106-02-07 07:28
http://planetkde.org/rss20.xml - 21 items fetched with same wrong date
http://pim.planetkde.org/rss20.xml - all fetched correctly

I usually delete wrong items afterwards as they are always first and hide new
items.

I try to investigate it in more detail with next install I have planned.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
dmatt
2012-06-27 08:29:09 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #5 from dmatt <***@gmail.com> ---
Happened to me again in Akregator 4.8.3 in Kubuntu 12.04 with few feeds
including Planet KDE after I imported links in opml file from previous
Akregator install before first "Fetch all feeds".
--
You are receiving this mail because:
You are the assignee for the bug.
dmatt
2013-11-02 23:28:42 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #6 from dmatt <***@gmail.com> ---
The bug is still present in 4.11.2 and is easily reproducible. I always trigger
this bug in a new Kubuntu installation by simply importing *.opml with my usual
set of feeds, some of which are duplicates to Akregator (or Kubuntu) default
set.

Steps to reproduce:
1. Add feed, which is duplicate of the feed already included in Akregator or
add new feed twice to different folders.
2. Fetch all feeds. New Items in one copy of the feed have all information
correct. New Items in second copy of feed might have 00:59 or 01:00 information
instead of correct date. After Akregator is restarted date information for
affected items changes to 07.02.2106 07:28.

When the duplicate feed is removed, new items are fetched with correct dates,
but the older ones with wrong date stay wrong.
--
You are receiving this mail because:
You are the assignee for the bug.
dmatt
2013-11-02 23:44:31 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #7 from dmatt <***@gmail.com> ---
Actually, after akregator is restarted, both copies of feed show the date
07.02.2106 07:28 in affected items.
--
You are receiving this mail because:
You are the assignee for the bug.
Janet
2013-11-03 19:40:37 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Janet <***@kerridis.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Version|1.6.5 |4.11.2

--- Comment #8 from Janet <***@kerridis.de> ---
I am not aware of having duplicate feeds... It happend to me with unique feeds.
But - maybe - it happens when feeds come from the same source, like last.fm
recently played tracks and loved tracks: two different feeds, but same
origin...
--
You are receiving this mail because:
You are the assignee for the bug.
Christoph Feck
2013-12-28 14:13:18 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Christoph Feck <***@maxiom.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #9 from Christoph Feck <***@maxiom.de> ---
*** Bug 317344 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
Arthur Țițeică
2015-03-10 05:37:19 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Arthur Țițeică <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com
--
You are receiving this mail because:
You are the assignee for the bug.
Andrey via KDE Bugzilla
2015-10-21 00:15:11 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Andrey <***@openaliasbox.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@openaliasbox.org
--
You are receiving this mail because:
You are the assignee for the bug.
Marc González Majoral via KDE Bugzilla
2016-02-25 20:45:09 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Marc González Majoral <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #10 from Marc González Majoral <***@gmail.com> ---
More than 5 years, not bad.

Still happening in KDE 5, Akregator 5.0.3.

07-02-2016 has passed.
--
You are receiving this mail because:
You are the assignee for the bug.
Yuriy Vidineev via KDE Bugzilla
2016-04-25 10:12:33 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Yuriy Vidineev <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #11 from Yuriy Vidineev <***@gmail.com> ---
I also have such bug from time to time (Kubuntu 16.04) but can't reproduce
--
You are receiving this mail because:
You are the assignee for the bug.
Mark Fraser
2017-01-07 20:11:24 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Mark Fraser <mfraz74+***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |mfraz74+***@gmail.com

--- Comment #12 from Mark Fraser <mfraz74+***@gmail.com> ---
Yes, I am still seeing this bug with Kontact 5.2.3 in Kubuntu 16.04.
--
You are receiving this mail because:
You are the assignee for the bug.
Buoidin
2017-01-14 12:33:31 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Buoidin <607h67+***@pokemail.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |607h67+***@pokema
| |il.net

--- Comment #13 from Buoidin <607h67+***@pokemail.net> ---
This bug is still present in Akregator 16.04.3-2 and is really annoying. I'm
using Akregator in Debian Stretch with Kontact 16.04.3-2 and Plasma 5.

The bug seems to appear randomly but I also see it when the following happens.
First Akregator fetches new articles from feeds and it saves some of them
without date and time. So usually I don't see these articles because they are
put at the bottom of the list. Then, when Kontact is restarted, Akregator shows
these articles whit the date 07/02/06 07:28 at the top of the list.

This bug really undermines the usability of the program because it messes the
chronological order of the articles.
--
You are receiving this mail because:
You are the assignee for the bug.
Christoph Feck
2017-01-25 01:58:24 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Christoph Feck <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@free.fr

--- Comment #14 from Christoph Feck <***@kde.org> ---
*** Bug 375448 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
Mark Fraser
2017-06-24 16:03:06 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #15 from Mark Fraser <mfraz74+***@gmail.com> ---
I'm running Akregator 16.12.3 and this is still happening.
--
You are receiving this mail because:
You are the assignee for the bug.
Dennis Brünig
2017-08-12 23:41:14 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Dennis Brünig <***@dennis-bruenig.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@dennis-bruenig.de
--
You are receiving this mail because:
You are the assignee for the bug.
Dennis Brünig
2017-08-12 23:48:22 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #16 from Dennis Brünig <***@dennis-bruenig.de> ---
Version 17.04.3

It happened after a crash. For some items the feeds had the 2106 date.
--
You are receiving this mail because:
You are the assignee for the bug.
Pal Körössy
2017-08-20 05:59:05 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Pal Körössy <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #17 from Pal Körössy <***@gmail.com> ---
Same here with Akregator 17.04.3 with OpenSUSE Tumbleweeed.
--
You are receiving this mail because:
You are the assignee for the bug.
Philippe ROUBACH
2017-08-20 06:27:06 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #18 from Philippe ROUBACH <***@free.fr> ---
kde app 17.08

also some time some contents has no date.
--
You are receiving this mail because:
You are the assignee for the bug.
Laurent Montel
2017-08-20 11:44:44 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Laurent Montel <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Post by Philippe ROUBACH
also some time some contents has no date.
We need a test case for this one.
Perhaps it's a parsing error.
--
You are receiving this mail because:
You are the assignee for the bug.
Pal Körössy
2017-09-11 17:41:52 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #20 from Pal Körössy <***@gmail.com> ---
After deleting ~/.local/share/akregator folder, Akregator was working fine for
one day. Now I got items with wrong date again, so I moved back to the backup
folder.
What is necessary for you from my side to reproduce the issue?
--
You are receiving this mail because:
You are the assignee for the bug.
Holger
2017-09-16 16:08:01 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Holger <***@hotmail.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@hotmail.de

--- Comment #21 from Holger <***@hotmail.de> ---
Created attachment 107877
--> https://bugs.kde.org/attachment.cgi?id=107877&action=edit
example from packman list

I can confirm this issue as well, feeds appear suddenly with date 09.02.06
07:28.
Yesterday is configured akregator completely new (deleting
~/.local/share/akregator/ and ~/.config/akregatorrc). It worked without any
issues for some hours. Then akregator crashed (don't remember exactly the error
message, but something with a xml file) After the crash, my feeds were gone, I
had to import them again from a opml file. Again it worked for a couple of
hours. And now this strange feed date apears again.
--
You are receiving this mail because:
You are the assignee for the bug.
Cruz Enrique
2017-10-15 08:55:00 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Cruz Enrique <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com
--
You are receiving this mail because:
You are the assignee for the bug.
Marc González Majoral
2017-10-25 13:47:39 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #22 from Marc González Majoral <***@gmail.com> ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
Marc González Majoral
2017-10-25 13:48:39 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Marc González Majoral <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0 |1

--- Comment #23 from Marc González Majoral <***@gmail.com> ---
*** This bug has been confirmed by popular vote. ***
--
You are receiving this mail because:
You are the assignee for the bug.
Pal Körössy
2017-10-25 16:53:40 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #24 from Pal Körössy <***@gmail.com> ---
For me the problem was present on OpenSUSE Tumbleweed. It gone after reverting
back to stable version Leap 42.3 (Akregator 17.04-2-2.1). I deleted the items
with wrong date and I haven't experienced any problem for a month.
It was probably caused by some incorrect package versions.
--
You are receiving this mail because:
You are the assignee for the bug.
Daniel
2018-02-10 03:26:23 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Daniel <***@daniel.priv.no> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@daniel.priv.no

--- Comment #25 from Daniel <***@daniel.priv.no> ---
I also noticed this after a crash (#390192).
--
You are receiving this mail because:
You are the assignee for the bug.
Daniel
2018-02-10 23:41:54 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #26 from Daniel <***@daniel.priv.no> ---
The problem here may be that QDateTime can return -1 for invalid dates. Cast to
a 32-bit unsigned int, -1 is 4294967295, and interpreted as a timestamp that's
exactly 2106-02-07 07:28. The code doesn’t handle this case, as far as I can
tell.

Notably, I’ve had this happen with completely valid feeds with correct time
zone and ISO time strings. I’m not sure what the root cause is. The same feeds
will work if I delete all Akregator settings and import it anew.
--
You are receiving this mail because:
You are the assignee for the bug.
Philippe ROUBACH
2018-02-11 13:05:25 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #27 from Philippe ROUBACH <***@free.fr> ---
(In reply to Laurent Montel from comment #19)
Post by Laurent Montel
Post by Philippe ROUBACH
also some time some contents has no date.
We need a test case for this one.
Perhaps it's a parsing error.
what do you need ?
how to get what you need ?
--
You are receiving this mail because:
You are the assignee for the bug.
Mike Eichler
2018-03-27 08:30:51 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Mike Eichler <***@mykolab.ch> changed:

What |Removed |Added
----------------------------------------------------------------------------
Version|4.11.2 |5.7.2
Platform|Debian unstable |Neon Packages
CC| |***@mykolab.ch

--- Comment #28 from Mike Eichler <***@mykolab.ch> ---
There are a few articles with that date stuck at the top of article list in
akregator.
--
You are receiving this mail because:
You are the assignee for the bug.
aeris
2018-08-28 16:44:23 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

aeris <***@imirhil.fr> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@imirhil.fr

--- Comment #29 from aeris <***@imirhil.fr> ---
Created attachment 114662
--> https://bugs.kde.org/attachment.cgi?id=114662&action=edit
bugged feed

Dump of http://blog.xebia.fr/feed
--
You are receiving this mail because:
You are the assignee for the bug.
aeris
2018-08-28 16:45:12 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #30 from aeris <***@imirhil.fr> ---
Created attachment 114663
--> https://bugs.kde.org/attachment.cgi?id=114663&action=edit
Bad date on some entries
--
You are receiving this mail because:
You are the assignee for the bug.
aeris
2018-08-28 16:45:42 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #31 from aeris <***@imirhil.fr> ---
Created attachment 114664
--> https://bugs.kde.org/attachment.cgi?id=114664&action=edit
Broken entries after refresh from bugged feed
--
You are receiving this mail because:
You are the assignee for the bug.
aeris
2018-08-28 16:47:34 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

--- Comment #32 from aeris <***@imirhil.fr> ---
Same trouble here
Enclosed to this ticker a feed which generate bugged entries after a "refresh
feed" action.
Seem broken entries matches the one with the bugged date, only the 5 last
entries are correctly displayed.
--
You are receiving this mail because:
You are the assignee for the bug.
Martin Koller
2018-09-13 06:44:50 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Martin Koller <***@aon.at> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@aon.at

--- Comment #33 from Martin Koller <***@aon.at> ---
I see lots of them from http://planet.qt-project.org/rss20.xml
and I have the feeling it is the same problem coming from kio-http
which stores the same date/time when doing
kioclient5 copy 'https://www.kde.org/aether/media/patrons/google.svg'
file:///tmp/google.svg

stat google.svg shows
Modify: 2106-02-07 07:28:15.000000000 +0100

Also described here https://bugs.kde.org/show_bug.cgi?id=374420
but there it says it's not related to Akregator

Also possible dup: https://bugs.kde.org/show_bug.cgi?id=262271#c10
--
You are receiving this mail because:
You are the assignee for the bug.
Manuel Mommertz
2018-10-17 17:30:58 UTC
Permalink
https://bugs.kde.org/show_bug.cgi?id=256034

Manuel Mommertz <***@gmx.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmx.de
--
You are receiving this mail because:
You are the assignee for the bug.
Loading...