Bug 237837 - Unable to accept meetings, because the meeting already exists in other person's calendar
Summary: Unable to accept meetings, because the meeting already exists in other person...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-connector
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-04-25 15:51 UTC by Egon Kastelijn
Modified: 2010-06-28 10:24 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-28 10:24:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Egon Kastelijn 2007-04-25 15:51:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.10) Gecko/20070313 Fedora/1.5.0.10-5.fc6 Firefox/1.5.0.10

Description of problem:
My evolution is connected to Exchange with evolution-connector.
I connected to my collegue's calendar with "Subscribe to other user's calendar".
This works fine, and I can read his calendar.
(I do not have write access)

The problem:
* When I receive a meeting for a group, and my collegue accepts the meeting in his calendar before I do, then Evolution sais that it found the meeting in my collegue's calendar. This way I cannot accept the meeting in my own agenda.

Version-Release number of selected component (if applicable):
evolution-connector-2.8.3-1.fc6

How reproducible:
Always


Steps to Reproduce:
1. Configure the evolution-connector on 3 computers
2. Use the first computer to subscribe to the second user's calendar
3. Create a group meeting on the third computer and invite the first and the second user
4. Accept the meeting on the second computer
5. Try to accept the meeting on the first computer
   (this will not work, because evolution finds the meeting in the calendar of the second user.

Actual Results:
The meeting can not be accepted, and no alternative calendar can be selected.

Expected Results:
One of these:
* Evolution should not try to find the meeting in other user's calendars
* Evolution should allow the user to accept the meeting in another calendar than the calendar it has found it in.

Additional info:
-

Comment 1 Matthew Barnes 2007-10-02 18:21:25 UTC
Is this problem still present in Fedora 8 Test 2 or later?

Comment 2 Egon Kastelijn 2007-10-04 12:53:52 UTC
I am running FC7 at the moment.
I will install a FC8-test2 system next week and report about my findings.

Comment 3 Matthew Barnes 2007-10-04 14:16:21 UTC
Thanks for responding.  I'll leave this in NEEDINFO state until then.

Comment 4 Egon Kastelijn 2007-10-08 10:01:42 UTC
I enabled the yum development repos and did a "yum update" of my system from
Fedora 7 to Fedora 7.92 (Fedora8_test3).
Now I am running the following RPMs:
evolution.x86_64  2.12.0-6.fc8  
evolution-data-server.x86_64  1.12.0-1.fc8
evolution-exchange.x86_64  2.12.0-1.fc8
evolution-sharp.x86_64  0.14.0.1-1.fc8
evolution-webcal.x86_64  2.12.0-1.fc8

The problem still exists.

Comment 5 Matthew Barnes 2007-10-08 12:09:38 UTC
Okay, thanks for re-testing.  Moving version to f8test3.

Comment 6 Egon Kastelijn 2007-10-11 18:50:06 UTC
See also:
http://bugzilla.gnome.org/show_bug.cgi?id=436052

Comment 7 Bug Zapper 2008-11-26 07:14:20 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Matthew Barnes 2008-11-29 06:33:30 UTC
Assuming this issue is still unresolved since the upstream bug is still open.  Changing version to Rawhide.

Comment 9 Bug Zapper 2009-06-09 09:14:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Bug Zapper 2010-04-27 11:42:49 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Bug Zapper 2010-06-28 10:24:50 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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