No alarms or appointment list for Exchange calendar

Bug #40005 reported by Michael F. Rimbert
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Medium
evolution-data-server
Invalid
Undecided
Unassigned
evolution (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs
Nominated for Hardy by Jesse Gilles

Bug Description

I have an MS exchange account configured in evolution on a daily-updated dapper install. I do not get any alarm notifications for my calendar appointments, despite alarms being set for them. Clicking on the clock applet should list my appointments. However, only appointments on my "On This Computer" Personal calendar are shown.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. I forwarded the issue to the upstream developers: http://bugzilla.gnome.org/show_bug.cgi?id=338909

Changed in evolution-data-server:
assignee: nobody → desktop-bugs
Revision history for this message
Michael F. Rimbert (mrimbert) wrote :

I've discovered recently that appointements and alarm notifications work if and only if I have evolution save my password, which happens to be a security violation at my institution. The desired behavior would be to have them work after supplying the password, even if it is not saved.

Revision history for this message
Daniel Holbach (dholbach) wrote :

I followed up with your comment.

Revision history for this message
driedlinger (darinr) wrote :

I am experiencing the same issue with exchange and lack of alarms (Ubuntu edgy - updated). It worked once or twice but it would often crash evol. and now it does not notify at all for exchange alarms. I have all the settings correct....(select calendars for notification -- exchange account is selected). I have the save password box checked and I still do not get alarms.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Upstream comment:

"Yes. As of not alarms work only if the passwords are remembered for
accounts which requires authentication.

General Evolution bug, not specific to Exchange backend.

Changing the summary and moving it to Evolution - Calendar."

Changed in evolution-data-server:
status: Unconfirmed → Confirmed
Revision history for this message
Michael F. Rimbert (mrimbert) wrote :

Changed the summary back to original wording, as saving the password is no longer sufficient to get alarm notifications. This was tested on a fresh edgy install and feisty herd 4.

Revision history for this message
Richard Wilbur (richard-wilbur) wrote :

I confirm on a fresh install of feisty that Evolution 2.10 gave me no alarms for my Exchange calendar but did include the appointment list therefrom.

Another discussion of this issue (where I describe how I got alarms again):
https://bugs.launchpad.net/ubuntu/+source/evolution-exchange/+bug/98625

Revision history for this message
Ari (ari-reads) wrote :

Same problem under 7.10 / gutsy.

I use gutsy in an office / enterprise corporate environment. In this environment, this is a very major issue.

Revision history for this message
driedlinger (darinr) wrote :

After some time of getting frustrated and messing around with this issue, i stumbled upon a workaround. If you bring up evolution, log in (save password option checked) and wait for it update all your mail and when all is quite within evolution do a "evolution --force-shutdown" from a shell prompt, then restart evolution you will get your calendar alarms....kinda clunky and a royal pain but it seems to work....hope this helps someone track this issue down.

Revision history for this message
Jesse Gilles (jesse-gilles) wrote :

I also have this issue with 7.10 (and with 7.04). I used the --force-shutdown workaround and it does seem to work consistently. Every time I restart evolution, I run 'evolution --force-shutdown' first to stop any running evolution components. If I do this every time I restart evolution, I get alarms as configured. Also, I have had missing alarms for local calendar items as well, not just Exchange calendars.

Revision history for this message
Francesco Locunto (franceloc) wrote :

Please see my post on this thread:

https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/147163

and test if it works also for exchange alarms. I use normal calendar events only, and disabling session management for evolution-alarm-notify daemon has fixed the problem perfectly.

Revision history for this message
Stephen (sawjew) wrote :

I am using Hardy Beta and have the same issue. The calendar applet only shows the local calendar not the exchange calendar. I have tried the workarounds mentioned here and they do not work.

I had the same issue in Gutsy and fixed it by replacing the applet with Novell's International Clock Applet but I gather that has now been merged into the new Gnome Clock Applet.

This is a major problem as I use this system in a business environment and rely heavily on my calendar

Revision history for this message
Jesse Gilles (jesse-gilles) wrote :

I can confirm Stephen's comments. I tested an up-to-date hardy install last week and was only able to see my local appointments in the calendar applet. If evolution was not running, I only got alarms for appointments in my local calendar and not for my exchange calendar.

I did get alarms for exchange calendar appointments if evolution was running at the time of the alarm. so this seems to be an improvement over gutsy.

Revision history for this message
riker09 (riker-09) wrote :

I haven't read this bug report earlier, so I commented on bug #224188. All I can say right now is that I can confirm the problem with exchange calendars. Like my predecessors I rely on my calendar and having exchange appointments not only appear bolded but with a nice description just like lokal calendar appointments would be a great improvement. It shouldn't be too hard to fix, since the days already get bolded, so the applet must know that "something is there". After all, I remember this was working in Feisty.

Changed in evolution:
status: Confirmed → Triaged
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Reassigning to match the product of the upstream bug.

Changed in evolution-data-server:
importance: Unknown → Undecided
status: New → Invalid
Changed in evolution:
importance: Unknown → Medium
status: Unknown → New
Changed in evolution:
status: New → Fix Released
Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

change status to Fix released (see gnome-bugs)

Changed in evolution (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.