Bug 670917

Summary:	Evolution reports cancelled meeting is in disabled calendar
Product:	Red Hat Enterprise Linux 6	Reporter:	Marc Milgram <mmilgram>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	lnovich, mcrha, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	evolution-2.32.3-3.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-21 04:59:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Marc Milgram 2011-01-19 16:47:31 UTC

Description of problem:
I have two versions of each of my calendars - a Webcal version, and a Caldav version.  The Webcal versions are all disabled.  I received email with an appointment cancellation.  Evolution reported, "Found appointment in the calendar", and listed a Webcal calendar that I currently have disabled.

Version-Release number of selected component (if applicable):
evolution-2.28.3-10.el6.x86_64


How reproducible:
Seems to be

Steps to Reproduce:
1. Configure Caldav access to a calendar
2. Configure Webdav access to the same calendar
3. Disable Webdav access to the calendar
4. Make sure that a completely separate (Caldav?) calendar is the default calendar.
5. Receive and accept an appointment invitation
6. Receive an appointment cancelation for the appointment

Actual results:
Evolution shows that it found the appointment in the Webdav Calendar

Expected results:
Evolution shows that it found the calendar in the Caldav calendar

Additional info:

Comment 2 Milan Crha 2011-01-20 07:21:04 UTC

Sort of NotABug, it searches in all configured calendars, or in those setup in Edit->Preferences->Mail Preferences->tab Calendar and Tasks, section "Conflict search". I  believe it's correct to not take into account sources checked in the Calendar view, because it's just your current view on your calendars, which might not reflect your needs on meeting invitation lookup.

What about skipping read-only calendars? Though you can have there a meeting scheduled and as not an organizer you may not update the meeting anyway.

Other option would be to always use only calendars checked for conflict searching and never all configured calendars?

Comment 3 RHEL Program Management 2011-04-04 01:52:18 UTC

Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 Milan Crha 2013-05-09 17:53:55 UTC

Upstream fix to not check read-only calendars:
https://bugzilla.gnome.org/show_bug.cgi?id=616561

It cannot be backported as such (it landed in time for 3.4.0), it's just for a reference what the current upstream code uses.

Comment 13 errata-xmlrpc 2013-11-21 04:59:19 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1540.html