Dates before 1943 are reset to 20xx

UNCONFIRMED
Unassigned

Status

Calendar
Internal Components
UNCONFIRMED
6 years ago
4 years ago

People

(Reporter: Udvarias Ur, Unassigned)

Tracking

Lightning 1.1
x86
Linux

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Ubuntu; X11; Linux i686; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Build ID: 20111228084953

Steps to reproduce:

Ctrl-i: to open a new event
enter Title: Stephen Hawking 1942
select Category: Birthday
select Calendar: celebrity births & deaths
check: All day Event
set date: 1942 Jan 8
select Repeat: Yearly
click: Save and Close


Actual results:

Event Stephen Hawking 1942 is saved with a start date of Wed 8 Jan 2042.


Expected results:

Event Stephen Hawking 1942 should have been saved with a start date of Wed 8 Jan 1942.
(Reporter)

Updated

6 years ago
OS: All → Linux
Priority: -- → P3
Hardware: All → x86

Comment 1

6 years ago
I cannot reproduce this.

Which storage do you use?

What is your Linux distribution?
(Reporter)

Comment 2

6 years ago
I don't understand what you mean by 'which storage.' Everything, both software and data, is on a new IDE hard disk that was installed this past November.

The system it is running on is:
        Ubuntu 11.10,
        Thunderbird 8.0, and
        Lightning 1.0.

Comment 3

6 years ago
With storage I meant which backend you use. Lightning supports WebDAV, CalDAV and Local Storage. When you create a calendar in the wizard you choose where it will be stored.

From the above I assume you are using the "Local Storage" provider/backend.

I am on Ubuntu 11.10, Firefox 9.0.1 and Lightning 1.1.1 for me this works on CalDAV and Local Storage.

Can anybody else reproduce? 

Udvarias, could you try with a clean Thunderbird profile? i.e. a new user account?
(Reporter)

Comment 4

6 years ago
Deleted an empty account I created for test purposes and recreated it.

Then repeated the steps delineated in the bug report with the same result.
Priority: P3 → --
You need to log in before you can comment on or make changes to this bug.