Bug 293649

Summary:	The openXchange resource interprets the birthday wrong
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Johann-Nikolaus Andreae <johann-nikolaus>
Component:	OpenXchange Resource	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	marco, winter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:	4.8.2
Sentry Crash Report:

Description Johann-Nikolaus Andreae 2012-02-08 15:56:38 UTC

Version:           unspecified (using KDE 4.8.0) 
OS:                Linux

Copy my adressbook to openxchange some birthday are set to the 7.2.2106.

I tray to corect this date using kadressbook. I is always set beck to 7.2.2106.
Corecting the date with ox webinterface the 24.3.1954 is displayd in kadressbook as 29.4.2090. This date is is corect synct with Android.

Reproducible: Always

Steps to Reproduce:
Add a new kontact to a ox adressbook with birthday 08.01.1945.
Sync the adressbook.



Actual Results:  
The birthday is now change to 7.2.2106.

Expected Results:  
The birthday is 8.1.1945 on all systems

If i set 7.2.1984 the birthday is corect sync.
It fails at 10% of my adressbook entrys

Comment 1 Marco Nelles 2012-03-01 09:24:10 UTC

I can reproduce the bug and will have a closer look on it.

Comment 2 Marco Nelles 2012-03-01 11:56:50 UTC

Okay, Problem: 

QDateTime is unable to handle dates/times earlier than 1970-01-01 00:00:00.

I've fixed this with a workaround in this Akonadi resource.

COMMIT: cf86c0a8f0e6a6363c6fcd86e84225f83317dab0

Comment 3 Allen Winter 2012-03-02 13:39:46 UTC

can we resolve this one now?

Comment 4 Allen Winter 2012-03-02 13:40:42 UTC

hmmm, I don't see the backport of this fix into the 4.8 branch

Comment 5 Denis Kurz 2016-09-24 20:34:11 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 6 Denis Kurz 2017-01-07 21:41:09 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.