Bug 831907 - Unable to send item to calendar 'Calendar'. Timeout was reached
Summary: Unable to send item to calendar 'Calendar'. Timeout was reached
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-ews
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-14 03:38 UTC by Louis van Dyk
Modified: 2012-06-14 07:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-14 07:25:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 670458 0 None None None 2012-06-14 07:25:28 UTC

Description Louis van Dyk 2012-06-14 03:38:40 UTC
Description of problem:
I am able to read our corporate Exchange 2010 calendar.  I am able to add, delete and change entries using the Evolution interface.  But when I receive a meeting request, I am unable to ACCEPT it.
As an example, today I received a mail request. I opened it and it checked my calendar and stated:
An appointment in the calendar 'Calendar' conflicts with this meeting
I chose to accept the request anyway.  Each time I clicked accept, Evolution would wait a while, and then I would get the message:
Unable to send item to calendar 'Calendar'.  Timeout was reached
If I then tried to close the message with the invitation, it would hang.
If I killed Evolution with Force Quit, then evolution-calendar-factory would still be running.  I cannot kill it unless I use signal 9.
If I start evolution from the Terminal window, then I get the following over and over being recorded:
(evolution:10699): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed



Version-Release number of selected component (if applicable):
evolution-ews-3.4.2-2.fc17.x86_64
 -- along with --
evolution-data-server-3.4.2-1.fc17.x86_64
evolution-NetworkManager-3.4.2-1.fc17.x86_64
evolution-3.4.2-1.fc17.x86_64
evolution-help-3.4.2-1.fc17.noarch

I often get crashes where the submission points to
https://bugzilla.redhat.com/show_bug.cgi?id=814300
but this bug is old and nothing appears to be being done to it.

How reproducible:
Every time.


Steps to Reproduce:
As in Description.

  
Actual results:
As in Description.


Expected results:
I should be able to accept a meeting request, have the acknowledgement mail sent out, and the calendar updated with my meeting.

Additional info:

Comment 1 Milan Crha 2012-06-14 07:25:28 UTC
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

With respect of the crash you see often, I didn't get it yet. Are there any specific steps which would help with reproducibility of it, please?

[1] https://bugzilla.gnome.org/show_bug.cgi?id=670458


Note You need to log in before you can comment on or make changes to this bug.