GNOME Bugzilla – Bug 409805
snoozed alarms don't pop-up after evolution has been restarted
Last modified: 2018-05-11 11:39:01 UTC
Please describe the problem: If I snooze an alarm and then close evolution and restart my computer, I will not get re-minded of the appointment again. I listed this as priority = normal, but in reality, this causes me to miss events so I think its high priority. This is especially common for events that are one day out. Let's say I have an 11:30 appointment that is very important. I might schedule an alarm 1 day in advance, then hit the snooze button telling it to remind me again in 12 hours. Then, at the end of the day I shut down my computer expecting to be reminded again when I boot up in the morning. However, I will not be reminded the next morning. Having come to Evolution from Outlook, this is very disturbing because I rely on my alarms. Steps to reproduce: 1. Create an event a ways out 2. set an alarm to pop-up 3. snooze the alarm 4. reboot Actual results: Your snoozed alarm does not popup again Expected results: I would expect to continue to be reminded about events until I *dismiss* the alarm. This is actually a bit confusing, because there is no "dismiss" button for alarms, so if I have multiple alarms open, I have to snooze all of them that I don't want to dismiss, then dismiss the remaining ones and wait for the reminders to pop-up again. Its very unfortunate if I have to reboot and my reminders are lost for good. Does this happen every time? Yes Other information:
When the Evo guys were redesigning this dialog a year or two back, ISTR I pointed them at OSX's iCal reminder dialog as an example of a compact design that let you do everything you're asking for here. Might be worth them looking at it again...
https://bugs.edge.launchpad.net/bugs/331347 suggests that's still an issue using GNOME 2.24
Yes, and at the same time it doesn't seem to me a secondary issue. As I wrote in the other bug-track someone (like me) could really lose meetings because of this issue and decide to migrate even if the software itself is well done and mature... I think this bug shouldn't be under-evaluated.
This is similar to the current Evolution Alarm behaviour where Alarms that would have occured when a PC was powered off do not display when the system is eventually started. I recall a few years ago Evolution did display all Alarms missed because of the PC not running, but that disappeared a few versions ago. It would be nice if the Evolution/Gnome Calendar had a user selectable option to display "Missed" Alarms because of the PC being powered off - this sort of PC use spawned the Anacron package in acknowledgement that desktop PCs are not left running 24/7.
This problem still exists in Evolution 2.28.1 running on Ubuntu 9.10 and is definitely extremely annoying - any news on a possible upcoming patch or at least some kind of workaround?
This problem still exists in Evolution 2.28.3 running on Ubuntu 10.04 and, having just converted from Windows and Thunderbird/Lightening and previously MS Outlook, is a real problem for me. I accept there is the issue of a host of alarms going off when you come back from holiday but surely an option could be built in to deal with that. The only workaround I have is to remember to reschedule any appointments/tasks I have snoozed into the next day. Not good especially as my brain has long become conditioned to not having to remember things.
(In reply to comment #7) > This problem still exists in Evolution 2.28.3 running on Ubuntu 10.04 and, > having just converted from Windows and Thunderbird/Lightening and previously MS > Outlook, is a real problem for me. I accept there is the issue of a host of > alarms going off when you come back from holiday but surely an option could be > built in to deal with that. > > The only workaround I have is to remember to reschedule any appointments/tasks > I have snoozed into the next day. Not good especially as my brain has long > become conditioned to not having to remember things. The problem still exists in Evolution 2.30.3 with Ubuntu 10.10 64bit.
[Removing ancient GNOME Target.]
Hello André, Could you please explain "removing ancient GNOME Target"? Also I do not understand the status "unconfirmed" of this bug. It is very easy reproducable as reported by Matthew Nuzum [reporter] at 2007-02-19 23:30:52 UTC. Just follow the steps described by Matthew and the problem will show up. The bug is present for almost 4 years now, making the calender-function of Evolution essentially useless. The bug is still present in version 2.30.3 of Evolution with GNOME version 2.32 (Ubuntu 10.10). If any more info is needed regarding the issue, please let me know.
(In reply to comment #10) > Hello André, > > Could you please explain "removing ancient GNOME Target"? Target was 2.28, but nobody is working on 2.28 anymore, plus not a blocker by any means.
AFAIK this is still true in the latest releases, but then I haven't paid a lot of attention because... I forget about events that I snoozed that don't actually show up, obviously.
*** Bug 558363 has been marked as a duplicate of this bug. ***
This is finally addressed with a move of evolution-alarm-notify to evolution-data-server, which happened for 3.29.2+: https://git.gnome.org/browse/evolution-data-server/commit/?id=8ba0b06b7 https://git.gnome.org/browse/evolution/commit/?id=499518d53c