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 319241 - No alarm notification of exchange meetings and appointments
No alarm notification of exchange meetings and appointments
Status: RESOLVED DUPLICATE of bug 316710
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
unspecified
Other other
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-10-19 15:02 UTC by John Russell
Modified: 2005-10-20 04:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John Russell 2005-10-19 15:02:36 UTC 
From: John Russell <jjrussell@gmail.com>
To: submit@bugzilla.ximian.com
X-Mailer: bug-buddy 2.12.1
Subject: No alarm notification of exchange meetings and appointments

Distribution: Gentoo Base System version 1.12.0_pre9
Package: Evolution
Priority: Normal
Version: GNOME2.12.1 unspecified
Gnome-Distributor: Gentoo
Synopsis: No alarm notification of exchange meetings and appointments
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
Description:
Description of Problem:
There is no alarm notification of meetings and appointments that are in
any exchange calendar.  Alarms work fine for personl local calendars.

Steps to reproduce the problem:
1. Schedule an exchange meeting with an alarm
2.
3.

Actual Results:
The alarm does not appear

Expected Results:
An alarm would pop up when scheduled before the meeting

How often does this happen?
Every time.

Additional Information:




------- Bug moved to this database by unknown@gnome.bugs 2005-10-19 15:02 UTC -------
Comment 1 Chenthill P 2005-10-19 16:07:44 UTC 
Moving it to connector as it might be a exchange specific issue.
Comment 2 Poornima 2005-10-20 04:05:49 UTC 

*** This bug has been marked as a duplicate of 316710 ***