Expired/dismissed alarms repeat on every startup

Bug #804289 reported by Keith Refson
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Exchange Data Provider for Lightning
New
Undecided
Unassigned

Bug Description

Every time I start up Thunderbird, I receive a long list of alarm notifications for calendar events
which are dated in the past. The "Dismiss" button has no effect - the alarms still occur on subsequent
startups. It appears that TB or exchange provider is not actually expiring old appointments at all.

Due to the habit of my organization of posting calendar appointments for site-wide events, the
event log is very large, and in any case contains information I don't want to see posted on the net.
But I'll happily arrange to send a private copy.

At the end there are many events listed similar to

[calAlarmService] considering alarm for item: Office accommodation discussion alarm time: 2011/06/20 12:45:00 UTC isDate=0 snooze time: null
[calAlarmService] now is 2011/07/01 11:22:54 UTC isDate=0
[calAlarmService] last ack was: 2011/07/01 11:22:54 UTC isDate=0
[calAlarmService] Office accommodation discussion - alarm previously ackd.
d97d7c84-9aa8-4874-bb76-efcb5519ff54/STFC Exchange: modifyItem

d97d7c84-9aa8-4874-bb76-efcb5519ff54/STFC Exchange: PS: NEEDS-ACTION

Dismissing alarms using the webmail interface does appear to get rid of alarms permanently;
but TB/lightning + echange provider does not.

I am using exch provider 0.14 with TB 3.1 under Mandriva Linux 2010.1

Revision history for this message
Simon Schubert (corecode) wrote :

Could you paste a sample of the debug output for one item when loading the calendar. Please also post the output of the modify (when you press dismiss).

Feel free to obscure all text data fields.

Revision history for this message
Keith Refson (krefson) wrote :
Download full text (4.1 KiB)

Here is the relevant extract from the log for a single calendar item, which sets an alarm every time. Is that sufficient?

[calAlarmService] considering alarm for item: Office accommodation discussion alarm time: 2011/06/20 12:45:00 UTC isDate=0 snooze time: 2011/06/20 12:45:00 UTC isDate=0
[calAlarmService] now is 2011/07/02 12:49:32 UTC isDate=0
[calAlarmService] last ack was: 2011/06/20 12:44:59 UTC isDate=0
[calAlarmService] alarm is in the past and unack'd, firing now!

            <t:MeetingRequest>
              <t:ItemId Id="AAMkAGRlOTAzODBiLWI1NDUtNGQxYS04ZmE4LTkxZDA0NTNlOWRmMwBGAAAAAADIPD9BebNNR7ra47/Efb7OBwA3ysUaxcHSEZZhAKDJ7QAKAAAB61OHAADbViLTI6vzSpVKHEtQCrwaAAAADC74AAA=" ChangeKey="CwAAABYAAADbViLTI6vzSpVKHEtQCrwaAAAADPrc"/>
              <t:Subject>Office accommodation discussion</t:Subject>
              <t:Body BodyType="Text">When: 20 June 2011 14:00-14:30 (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London.
Where: R3, 2.30

Note: The GMT offset above does not reflect daylight saving time adjustments.

*~*~*~*~*~*~*~*~*~*</t:Body>
              <t:DateTimeReceived>2011-06-17T07:44:19Z</t:DateTimeReceived>
              <t:ReminderDueBy>2011-06-20T13:00:00Z</t:ReminderDueBy>
              <t:ReminderIsSet>true</t:ReminderIsSet>
              <t:ReminderMinutesBeforeStart>1525252321</t:ReminderMinutesBeforeStart>
              <t:ExtendedProperty>
                <t:ExtendedFieldURI DistinguishedPropertySetId="Common" PropertyId="34144" PropertyType="SystemTime"/>
                <t:Value>2011-06-20T13:00:00Z</t:Value>
              </t:ExtendedProperty>
              <t:ExtendedProperty>
                <t:ExtendedFieldURI DistinguishedPropertySetId="Meeting" PropertyId="3" PropertyType="Binary"/>
                <t:Value>BAAAAIIA4AB0xbcQGoLgCAAAAADgXNa9yizMAQAAAAAAAAAAEAAAAJVnvBLmO2tAvnnO05rhRy8=</t:Value>
              </t:ExtendedProperty>
              <t:UID>040000008200E00074C5B7101A82E00800000000E05CD6BDCA2CCC010000000000000000100000009567BC12E63B6B40BE79CED39AE1472F</t:UID>
              <t:Start>2011-06-20T13:00:00Z</t:Start>
              <t:End>2011-06-20T13:30:00Z</t:End>
              <t:IsAllDayEvent>false</t:IsAllDayEvent>
              <t:Location>R3, 2.30</t:Location>
              <t:IsCancelled>false</t:IsCancelled>
              <t:CalendarItemType>Single</t:CalendarItemType>
              <t:MyResponseType>NoResponseReceived</t:MyResponseType>
              <t:Organizer>
                <t:Mailbox>
                  <t:Name>ZZZZ </t:Name>
                  <t:EmailAddress>xxx@yyyy</t:EmailAddress>
                  <t:RoutingType>SMTP</t:RoutingType>
                </t:Mailbox>
              </t:Organizer>
              <t:RequiredAttendees>
                <t:Attendee>
                  <t:Mailbox>
                    <t:Name>ZZZZ</t:Name>
                    <t:EmailAddress>xxxx@yyyy</t:EmailAddress>
                    <t:RoutingType>SMTP</t:RoutingType>
                  </t:Mailbox>
                  <t:ResponseType>Unknown</t:ResponseType>
                </t:Attendee>
                <t:Attendee>
                  <t:Mailbox>
                    <t:Name>ZYZYZY</t:Name>
                  ...

Read more...

Revision history for this message
Keith Refson (krefson) wrote :

Hi, I hope that information was sufficient.

But with an update to 0.16, the behaviour is now changed. I now receive reminders for the events, not just once on start up but now every time the exchange calendar is refreshed. Again the "dismiss" button has no long-term effect
on the event alarm status, which just won't go away.

Revision history for this message
Keith Refson (krefson) wrote :

Actually with this change, it now looks more and more like another instance of #633352

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.