765530 - Invite Attendees is not working after update for TB 13.0.1 update

Status: RESOLVED FIXED

(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)

Description

[Ron McKenzie]

Attachment: InviteAttendeesDialogError-2012-06-16.png

User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; BRI/2)

Steps to reproduce:

I clicked on an existing Calendar event, opening the Edit Event dialog, I clicked the Invite Attendees button popping the Invite Attendees dialog.


Actual results:

1. The header for the grid has the proper date range (event date and day after), however, it shows today's date and the current time in the From & To fields for date and time, NOT the event's dates and times from the Edit Event dialog. 
2. Even after adding an Attendee's email and correcting the From & To fields for date and time, when I click "OK" nothing happens. The Invite Attendees dialog fails to close and return focus to the Edit Event dialog.


Expected results:

1. The dates/times for the event should have been populated in the From/To fields of the Invite Attendees dialog; and
2. After adding an Attendee, clicking "OK" should update that information to the Event record, close the Invite Attendee dialog, and return focus to the Edit Event dialog.

Comment 1

[Stefan Sitter [:ssitter]]

Hi, do you see any error messages in Tools > Error Console during the workflow? What type of calendar provider (e.g. local, remote, ics, caldav, ...) do you use?

Comment 2

[Ron McKenzie]

Looking in Tools > Error Console:
1. Just opening a Calendar Event produces this error:

Timestamp: 6/17/2012 3:33:25 PM
Error: uncaught exception: [Exception... "Node cannot be inserted at the specified point in the hierarchy"  code: "3" nsresult: "0x80530003 (HierarchyRequestError)"  location: "chrome://calendar/content/calendar-event-dialog-attendees.js Line: 85"]
Timestamp: 6/17/2012 3:33:25 PM
Warning: Error in parsing value for 'min-height'.  Declaration dropped.
Source File: chrome://calendar/skin/calendar-event-dialog.css
Line: 0
Timestamp: 6/17/2012 3:34:10 PM
Warning: Dangling combinator.  Ruleset ignored due to bad selector.
Source File: about:blank
Line: 4

2. Clicking Invite Attendee, correcting the date/times and adding attendee, produces the following errors:

Timestamp: 6/17/2012 3:37:35 PM
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [calIDateTime.addDuration]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://calendar/content/calendar-event-dialog-attendees.js :: updateStartTime :: line 379"  data: no]
Timestamp: 6/17/2012 3:37:35 PM
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [calIDateTime.addDuration]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://calendar/content/calendar-event-dialog-attendees.js :: updateStartTime :: line 379"  data: no]
Timestamp: 6/17/2012 3:37:49 PM
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [calIDateTime.addDuration]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://calendar/content/calendar-event-dialog-attendees.js :: updateStartTime :: line 379"  data: no]
Timestamp: 6/17/2012 3:37:49 PM
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [calIDateTime.addDuration]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://calendar/content/calendar-event-dialog-attendees.js :: updateStartTime :: line 379"  data: no]
Timestamp: 6/17/2012 3:37:52 PM
Error: timezone is null
Source File: chrome://calendar/content/calendar-event-dialog-attendees.js
Line: 414
Timestamp: 6/17/2012 3:37:52 PM
Error: timezone is null
Source File: chrome://calendar/content/calendar-event-dialog-attendees.js
Line: 414
Timestamp: 6/17/2012 3:38:00 PM
Error: timezone is null
Source File: chrome://calendar/content/calendar-event-dialog-attendees.js
Line: 414
Timestamp: 6/17/2012 3:38:00 PM
Error: timezone is null
Source File: chrome://calendar/content/calendar-event-dialog-attendees.js
Line: 414
Timestamp: 6/17/2012 3:38:09 PM
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [calIDateTime.addDuration]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://calendar/content/calendar-event-dialog-attendees.js :: updateStartTime :: line 379"  data: no]
Timestamp: 6/17/2012 3:38:09 PM
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004003 (NS_ERROR_INVALID_POINTER) [calIDateTime.addDuration]"  nsresult: "0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://calendar/content/calendar-event-dialog-attendees.js :: updateStartTime :: line 379"  data: no]
Timestamp: 6/17/2012 3:38:31 PM
Error: timezone is null
Source File: chrome://calendar/content/calendar-event-dialog-attendees.js
Line: 414
Timestamp: 6/17/2012 3:38:31 PM
Error: timezone is null
Source File: chrome://calendar/content/calendar-event-dialog-attendees.js
Line: 414
Timestamp: 6/17/2012 3:44:11 PM
Warning: Expected declaration but found '*'.  Skipped to next declaration.
Source File: about:blank
Line: 392
Timestamp: 6/17/2012 3:44:11 PM
Warning: Expected declaration but found '*'.  Skipped to next declaration.
Source File: about:blank
Line: 393
Timestamp: 6/17/2012 3:44:11 PM
Warning: Error in parsing value for 'font'.  Declaration dropped.
Source File: about:blank
Line: 399
Timestamp: 6/17/2012 3:44:11 PM
Warning: Expected declaration but found '*'.  Skipped to next declaration.
Source File: about:blank
Line: 407

Calendar provider? Must be local, I'm using TB & Lightning on my laptop, occasionally send events to and receive them from my desktop at work which runs MS Outlook on Exchange Server. Does this answer your question?

Comment 3

[Carlo Di Dato]

@Ron McKenzie
I had your same problem, actually to solve I removed Lightning 1.5.1 and install the version 1.5. Everything works fine.

Comment 6

[Mark Dixon]

Ron  That worked for me as well. Thanks

Comment 8

[Roland Tanglao needinfo please :rolandtanglao, :mohnkuchen, :adobo, :sinigang, :roland]

Philipp sounds like we need a a Lightning 1.5.2 to fix this problem. 

For what it's worth, I don't see this problem with Mac TB 13.0.1 + Lightning 1.5.1. I only see it with Windows 13.0.1 + Lightning 1.5.1

Comment 9

[Stefan Sitter [:ssitter]]

Possible workaround for Lightning 1.5.1:
1. Open your profile folder, e.g. via Help > Troubleshooting Information > Profile Folder
2. Open the following file in a text editor: "extensions\{e2fda1a4-762b-4020-b5ad-a41df1933103}\chrome\calendar\skin\calendar\calendar-event-dialog.css"
3. Delete the line "@import url(chrome://calendar-windows/skin/calendar-event-dialog.css);"
4. Save and restart Thunderbird

Comment 10

[Roland Tanglao needinfo please :rolandtanglao, :mohnkuchen, :adobo, :sinigang, :roland]

(In reply to Stefan Sitter from comment #9)
> Possible workaround for Lightning 1.5.1:
> 1. Open your profile folder, e.g. via Help > Troubleshooting Information >
> Profile Folder
> 2. Open the following file in a text editor:
> "extensions\{e2fda1a4-762b-4020-b5ad-
> a41df1933103}\chrome\calendar\skin\calendar\calendar-event-dialog.css"
> 3. Delete the line "@import
> url(chrome://calendar-windows/skin/calendar-event-dialog.css);"
> 4. Save and restart Thunderbird

this is a great workaround for power users but won't work for "normal" :-) people, therefore I'd like a 1.5.2 to be considered for release soon

Comment 11

[Mike Pail]

I can confirm the same bug, with Win 13.0.1 + Lightning 1.5.1.
I can confirm that changing the file, as listed by Stefan Sitter, fixes the problem.

Comment 16

[foodsage]

Please fix this soon for us "normal" users. If I tried do that work around I would probably screw up something else. 

When can we get the fix?

Comment 17

[foodsage]

I tried the workaround and it did work. I consider myself a "slightly more savvy than normal" user but not a power user and luckily knew what was meant by using a text editor. If you explained that line by giving Mac and PC names of editors then more people could probably make it work.

Have to agree that a normal or novice user will need a fix.

Comment 18

[Stefan Sitter [:ssitter]]

A fix was checked in for all branches with Bug 765600.

Lightning 1.5.2 that contains the fix was released on June 21, 2012:
https://addons.mozilla.org/thunderbird/addon/lightning/versions/1.5.2

Thunderbird should automatically download and install the update once it has been officially reviewed and approved by the addons.mozilla.org team.