After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 361760 - Evolution Calendar reminders not working
Evolution Calendar reminders not working
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.6.0
Other All
: Normal normal
: ---
Assigned To: Chenthill P
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2006-10-12 17:46 UTC by m0nk
Modified: 2008-09-08 11:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description m0nk 2006-10-12 17:46:53 UTC
Please describe the problem:
Calendar appointments on an Exchange calendar are not producing a reminder/alarm for version 2.6.3 (2.6.3-1.fc5.5) on Fedora Core 5.  The issue started with version 2.6.1 and wasn't corrected after upgrading.  Exchange connecter version: 2.6.3-2.fc5.  

Steps to reproduce:
I have the issue yet my coworker does not.  Steps I have taken to try and correct are basically just changing my settings:

1. Edit>Preferences>Calendars and Tasks - Show a Reminder is checked, set from 15 minutes to 20 minutes (no change)
2. Alarms tab has all my calendars selected for alarms, I changed to only show the one on the exchange server (no change)
3. Each appointment on the calendar has the alarm set, initially 15 minutes prior then changed to 20 minutes prior (no change)


Actual results:
No change, no reminders/alarms are provided.

Expected results:
A reminder/alarm 20 minutes prior to appointment.

Does this happen every time?
Yes

Other information:
Comment 1 Chenthill P 2006-10-13 05:25:41 UTC
Monk, you need to remember the password for reminders to work on exchange component. Please run evolution, mark "Remember password" while entering the password. From terminal run
$ evolution --force-shutdown.

Then restart evolution. Please try out this.
Comment 2 Akhil Laddha 2008-08-06 06:58:39 UTC
There has been so many changes and bug fixes in alarm code there after. Can you please check in current stable 2.22.3, thanks in advance.
Comment 3 Akhil Laddha 2008-09-08 11:11:01 UTC
Closing this bug report as no further information has been provided. Please
feel free to reopen this bug if you can provide the information asked for with
current version 2.22.3.1 Thanks!