GNOME Bugzilla – Bug 247585
Evolution meeting created with time as free, in outlook are busy
Last modified: 2012-02-02 14:39:09 UTC
Description of Problem: I create a meeting in Evolution and show the meeting time as Free. If an attendee accepts the meeting invitation in Outlook then the meeting created in Outlook's calendar shows the time as busy. The reverse does not work either. For a meeting created in Outlook with the time shown as free, accepting the invitiation in Evolution creates a meeting with the time is busy. However when the organizer and attendee both use Oulook the meeting is correctly created with the time as free in the attendee's calendar. Steps to reproduce the problem: 1. Create meeting in Evolution and Show time as Free 2. Invite one Outlook account 3. Accept meeting invitation in Outlook Expected Results: Meeting in attendee's calendar show's time as free Additional Information: Machine Configuration ------------------------------------------------------------------ Linux tlee 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux evolution-1.4.3.99.0.200307281501-0.snap.ximian.5.1 ximian-connector-1.4.4-0.ximian.5.1 libsoup-1.99.24.0.200307281501-0.snap.ximian.5.1 libgal19-0.19.2-4 libgal2.0_3-1.99.8.99.0.200307281501-0.snap.ximian.5.1 gtkhtml-1.0.4-3 gtkhtml3.0-3.0.7.0.200307281501-0.snap.ximian.5.1 evolution-pilot-1.4.3.99.0.200307281501-0.snap.ximian.5.1 pilot-link-0.11.3-3 gnome-pilot-2.0.10.0.200307281501-0.snap.ximian.5.1 gnome-pilot-applet-2.0.10.0.200307281501-0.snap.ximian.5.1 gnome-pilot-conduits-2.0.9-0.ximian.5.1 gnome-mime-data-2.0.0-9 gtk-1.2.10-22 gtk2-2.0.6-8.ximian.80.1 bonobo-1.0.21-1.ximian.1 libbonoboui-2.0.1-2 libgnomecanvas-2.2.0.2-0.ximian.5.2
Retargetting all 2.0 reports for 1.5.x Please set new milestone if needed.
Retargeting 1.5.3->1.5.4 bug reports. Sorry for the spam.
Not a regression, and we should be sending transparency to outlook, i suspect they aren't using the icalendar field for this.
This bug is happening in my set up too .
Sorry that this report has not received attention earlier. Note that the package "evolution-exchange" is deprecated nowadays. Similar functionality is now provided by "evolution-mapi" and "evolution-ews" packages. This bug was reported against a version that is now not supported anymore. Could you please check if the problem that you reported here still happens with a recent version of Evolution (like 3.2 or 3.0) AND with either evolution-mapi or evolution-ews? Thanks in advance!
Closing this bug report as no updated information has been provided. Please reopen this bug if the problem still occurs with a newer version of Evolution (currently this means: preferably version 3.2.x) and provide the information that was asked for in the previous comment. Again thank you for reporting this bug and we are sorry it could not be fixed for the version that you originally used when reporting this problem.