Bug 349354 - Imported Contacts from google have a random year in birthday field
Summary: Imported Contacts from google have a random year in birthday field
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-18 22:19 UTC by j0k3ing+spam
Modified: 2018-02-01 09:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description j0k3ing+spam 2015-06-18 22:19:18 UTC
I imported my contacts from google (fresh import).
Most of my contacts have a birthday including a year. For some I only have Month and day.
The ones that don't have a year specified were assigned a random year.
It wasn't completely random. the years that were assigned were either 1604 or 1900

Reproducible: Didn't try

Steps to Reproduce:
1. make sure you have a contact with only month and day as birthday in gmail (Junge 19 for example)
2. Use google contact import
3. the contact has some weird year as birthday

Actual Results:  
year of contacts was set to wrong value

Expected Results:  
no year set

latest archlinux package
KAddressBook
Version 4.14.9
Using KDE Development Platform 4.14.9
Comment 1 Denis Kurz 2017-06-23 19:58:23 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-02-01 09:47:16 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.