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 316710 - Alarms don't popup on items on Exchange
Alarms don't popup on items on Exchange
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
: 319241 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-09-19 15:41 UTC by Ryan P Skadberg
Modified: 2005-11-10 18:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
generate correct key for fetching password (2.36 KB, patch)
2005-11-08 09:49 UTC, Chakravarthi
committed Details | Review

Description Ryan P Skadberg 2005-09-19 15:41:33 UTC
Distribution/Version: Fedora Rawhide

I have been putting my work events on my Exchange calendar now that I have
exchange and connector, but none of them have been sending me alarms.  I did
notice when I recently went in to OWA on a Windows machine using IE and got
popups for old events that had never popped up in Evolution.
Comment 1 Sarfraaz Ahmed 2005-10-11 07:01:07 UTC
Try remembering your password in evolution and see if it works. Though, I am not
sure if the same should also help for the clock applet.

If, i am right, the alarm notify and the clock-applets should prompt the user
for authentication if the backend supports authentication and then load the
backend calendars. This is currently not supported by either of them :-(. So as
a workaround, we need to remember the password in Evolution
Comment 2 John Affleck 2005-10-11 13:10:12 UTC
I have the same problem. I exited evolution, did an evolution-2.4
--force-shutdown, and restarted it. When prompted for my exchange password, I
checked 'Remember this password'. I exited evolution again and restarted to make
sure that the password was being stored, and was not prompted for my password again.

I then created two identical appointments, one on my local calendar and one on
my exchange. The reminder for the local version of the appointment appeared, but
the exchange version did not. I also created a new, exchange only appointment,
but did not receive a reminder for that either.
Comment 3 Poornima 2005-10-20 04:05:50 UTC
*** Bug 319241 has been marked as a duplicate of this bug. ***
Comment 4 Poornima 2005-10-20 05:50:29 UTC
Even with save password alarm notification doesnt popup for appointments in
exchange calendar.
Comment 5 John Affleck 2005-10-27 15:39:38 UTC
I just tried this on an Ubuntu Breezy Badger machine, and the clock-applet
intergration worked fine. Same exchange server, same setup. Still no alarms, though.

I rebuild with -g, but can't make head or tail of what I'm seeing. I appear to
see a corrupted 'property' string in the following e_source_get_property call:
    at alarm-notify.c:347
347             if ((e_source_get_property (source, "auth") &&
If I force it to a good value in the e_source_get_property call, I get a
'client' assigned correctly, but the alarms still don't seem to work, and I'm
not sure how sane things are at that point.

Any hints on tracking this down ?
Comment 6 John Affleck 2005-10-27 22:46:07 UTC
Well, I think I have a work-around. It looks like alarm-notify looks for
exchange://jrafflec%40amr;auth=Basic@<foo>/;personal/Calendar, but the disk
version is just exchange://jrafflec%40amr;auth=Basic@<foo>/. Saving the exchange
password and adding the ;personal/Calendar seems to make the alarm component
happy at least. Does anyone want to verify that ?
Comment 7 John Affleck 2005-10-27 22:46:39 UTC
Well, I think I have a work-around. It looks like alarm-notify looks for
exchange://jrafflec%40amr;auth=Basic@<foo>/;personal/Calendar, but the disk
version is just exchange://jrafflec%40amr;auth=Basic@<foo>/. Saving the exchange
password and adding the ;personal/Calendar seems to make the alarm component
happy at least. Does anyone want to verify that ?
Comment 8 John Russell 2005-11-07 17:37:13 UTC
When you say alarm-notify "looks for" that string.  Where is it looking? What
should I change in order to test your workaround.  Thanks.
Comment 9 Chakravarthi 2005-11-08 09:49:26 UTC
Created attachment 54456 [details] [review]
generate correct key for fetching password
Comment 10 Chakravarthi 2005-11-08 10:01:13 UTC
Changing the component to evolution calendar as its not a connector bug.
 
Comment 11 Chakravarthi 2005-11-08 10:02:23 UTC
Changing the status to resolved fixed as the patch is approved on the lists and
is  committed to both head and gnome-2-12. 
Comment 12 John Russell 2005-11-10 18:09:33 UTC
Applied the patch and alarms work perfectly.  Thanks a lot.