GNOME Bugzilla – Bug 692059
No calendar reminder notifications after suspend
Last modified: 2013-03-11 17:52:29 UTC
I noticed that after my laptop went to suspend overnight no more calendar reminder notifications are shown, neither via pop-up window (if set so) nor in gnome 3 notification area at the bottom of the screen. This is true at least for local calendar and gmail calendars. I did the following test to reproduce the behaviour: I set a series of test-calendar entries all with notification set. All of them appeared in time (fine). Then I set my laptop in suspend state. Next morning when waking it up the calendar entries which where in the past and not processed and are not popped up. Same is true for all coming calendar entries. Expected bahaviour of course should be that the missing calendar entries are popped up immediately and the reminder notification for all coming calendar entries shall be shown. The behaviour does not show when sending the laptop to suspend for only a few minutes. I'm running Gnome 3.4.2, Evolution 3.4.4 on Fedora 17. Laptop is Lenovo T400. The expected behaviour (so this is some kind of a workaround) can be estalished when going to Edit->Preferences->Calendar, Tab "Reminders" and clearing and restting the checkboxes for "Select calendars for reminder notifications". If clearing and setting a calendar the missing popups appera immediately.
I think this is fixed already in 3.6. The problem is we were scheduling reminders using a monotonic timer instead of based on wall-clock time. So for example if a reminder is scheduled for an hour from now, the reminder would pop up after an hour's worth of CPU time, regardless of how long you suspend.
Understood. Thanks for your reply. when will it be released? I guess 3.6 is part of the next Gnome 3-Version, right? CU - robert.
Evolution 3.6 was released last September. It's included in Feodra 18, which was (finally) released last week.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 680611 ***