After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 253637 - In any calandar view pre-1970 birthdays and aniversaries end up on December 31
In any calandar view pre-1970 birthdays and aniversaries end up on December 31
Status: RESOLVED DUPLICATE of bug 231662
Product: evolution
Classification: Applications
Component: Calendar
1.5.x (obsolete)
Other All
: Normal major
: ---
Assigned To: Chris Toshok
Evolution QA team
: 252803 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-01-30 19:22 UTC by Trever Adams
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Trever Adams 2004-01-30 19:22:36 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:

Create a contact, add a birthday and aniversary (your parents would do fine
I think) where it is pre-1970.  Look on December 31, here you see it.  This
probably comes down to a sign error in the calandar part of the program.


Steps to reproduce the problem:
1. Create a contact with pre-1970 birthday/aniversary
2. Tell calandar to show such
3. Look at december 31

Actual Results:

The aniversary and birthday that are pre-1970 will show up on December 31,
not where they belong.

Expected Results:

Seeing it on the right day.

How often does this happen? 

Every time

Additional Information:

As a related note, NONE (or empty) in aniversary or birthday should not
become 00/00/0 or some such.  This is a related, significant bug.
Comment 1 Björn Torkelsson 2004-02-17 21:26:57 UTC 
*** bug 252803 has been marked as a duplicate of this bug. ***
Comment 2 Björn Torkelsson 2004-02-17 22:28:49 UTC 
It is not only birthdays that are broken. Try to add an event before
Jan 1, 1970 and it ends up on wrong day. "Goto Date" does nothing when
trying to go to a date before 1970.
Comment 3 Björn Torkelsson 2004-02-17 23:01:32 UTC 
This is actually a duplicate of 31662.

*** This bug has been marked as a duplicate of 231662 ***