Closed Bug 460053 Opened 17 years ago Closed 17 years ago

Errors in recurring alarms

Categories

(Calendar :: Alarms, defect)

Product:
Calendar
Component:
Alarms
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: davida, Unassigned)

Details

I get these for an event which is "recurring forever": ... [calAlarmService] now is 2008/10/15 16:25:03 UTC isDate=0 [calAlarmService] alarm is in the future. [calAlarmService] alarm is too late. [calAlarmService] considering alarm for item: Mark Banner alarm time: 2008/11/03 19:45:00 UTC isDate=0 snooze time: null [calAlarmService] now is 2008/10/15 16:25:03 UTC isDate=0 [calAlarmService] alarm is in the future. [calAlarmService] alarm is too late. [calAlarmService] considering alarm for item: Mark Banner alarm time: 2008/11/10 19:45:00 UTC isDate=0 snooze time: null ...
Flags: tb-integration+
Where is the error? This looks like the normal debug output if "calendar.debug.log" is set to true.
Marking as INVALID. David, please reopen, in case calendar.debug.log is not set in about:config and this is still occurring.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.