Open Bug 1547992 Opened 6 years ago Updated 3 years ago

Alarms are not triggered if timezone is not set

Categories

(Calendar :: Alarms, defect)

x86
Windows 10
defect

Tracking

(Not tracked)

People

(Reporter: selim, Unassigned)

References

Details

Steps to reproduce:

  1. Create a new profile.
  2. Check that Options > Calendar > General > Timezone setting is empty.
  3. Create a new event and set reminder to 5 minutes before.

Reminder is not triggered when Thunderbird is running at the time of set reminder. Restarting Thunderbird triggers the missed reminder.

Reminders work properly if timezone is manually set in options (Europe/Istanbul in my case).

What version of Thunderbird and Lightning do you use? How did you specify an empty entry in Options > Calendar > General > Timezone? Do you get any error messages in Error Console?

I tried Thunderbird 68.0a1 (2019-04-29) with Lightning 7.0a1 and I cannot select an empty entry in Options > Calendar > General > Timezone.

Flags: needinfo?(selim)

I'm using Thunderbird 67.0b2 with Lightning 6.9.

Creating a new profile gives me an empty entry in Options > Calendar > General > Timezone. Once you select any timezone from the list, you can't revert to the empty entry.

Flags: needinfo?(selim)

So you get no error messages in Error Console?

But the behavior sounds strange. As far as I know Lightning should detect/guess timezone during installation. If I create a new profile using English Thunderbird Daily 68.0a1 (2019-05-08) on German Windows 10 system Lightning automatically sets the timezone to Europe/Berlin. Maybe this doesn't work for you? What localization, operating system, timezone do you use?

Could you create and set the preferences "calendar.debug.log" and "calendar.debug.log.verbose" to true in Thunderbird before installing Lightning? During Lightning installation I get a warning message like this in Error Console:

Lightning: Warning: Using guessed timezone
Europe/Berlin (UTC+0100/+0200).
This ZoneInfo timezone seems to match the operating system timezone this year.
This ZoneInfo timezone was chosen based on the operating system timezone
identifier "W. Europe Standard Time". calTimezoneService.js:802

Maybe you see some messages that might explain what happens when detecting/guessing timezone during installation.

Flags: needinfo?(selim)

I'm using Turkish Windows 10, timezone set to UTC+3 Istanbul and region set to Turkey.

I've just installed Thunderbird Daily (tr) and here's what I see in the error console:

İşletim sistemi saat dilimi (Turkey Standard Time) görmezden geliniyor. [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: jar:file:///C:/Program%20Files/Thunderbird%20Daily/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D.xpi!/components/calTimezoneService.js :: guessSystemTimezone :: line 635" data: no] calTimezoneService.js:696
guessSystemTimezone jar:file:///C:/Program Files/Thunderbird Daily/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi!/components/calTimezoneService.js:696
get defaultTimezone jar:file:///C:/Program Files/Thunderbird Daily/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi!/components/calTimezoneService.js:251
get defaultTimezone resource://calendar/modules/utils/calDateTimeUtils.jsm:24
now resource://calendar/modules/utils/calDateTimeUtils.jsm:65
setUpTodayDate chrome://calendar/content/widgets/calendar-widgets.xml:49
toolbarbutton_XBL_Constructor chrome://calendar/content/widgets/calendar-widgets.xml:44

Lightning: Uyarı: "Sabit" saat dilimi kullanılıyor.
Bölge bilgisi saat dilimi verisi, işletim sisteminin saat dilimi verisiyle eşleşti. calTimezoneService.js:762

English translations FYI:

Skipping Operating System timezone 'Turkey Standard Time'.

Warning: Using "floating" timezone.
No ZoneInfo timezone data matched the operating system timezone data.

Flags: needinfo?(selim)

I filed Bug 1550044 to make Lightning aware of new time zone names used by Windows.

See Also: → 1550044
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.