Evolution alarm notification does not persist after snooze and reboot

This is not a bug in Launchpad. Moving it to the evolution project.

Sorry but inadvertently i clicked on the nice popup message "add to
launchpad bugs" again, now i dunno how to remove it from lauchpad bugs. Can
you help me? Any hint?

bye,
Alessandro

2009/2/19 Tom Berger <email address hidden>

> This is not a bug in Launchpad. Moving it to the evolution project.
>
> ** Changed in: evolution
> Product: Launchpad Bugs => Evolution
>
> --
> Evolution alarm notification does not persist after snooze and reboot
> https://bugs.launchpad.net/bugs/331347
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Evolution Mail & Calendaring Tool: New
>
> Bug description:
> Snooze function works properly while the system is on, but it stops working
> if the system is rebooted. For instance, i receive a notification for "Event
> #1" and I decide to snooze "6 hours later". If i keep the system on for the
> whole 6 hours it will work as expected, but if I reboot it or shutdown the
> system, after that the notification will be forgot. This behaviour is very
> tricky and the notification reliability is somehow low...
>
> Linux gidan-notebook 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009
> x86_64 GNU/Linux
>
> ProblemType: Bug
> Architecture: amd64
> ExecutablePath: /usr/bin/evolution
> NonfreeKernelModules: nvidia
> Package: evolution 2.24.3-0ubuntu1
> SourcePackage: evolution
>

[Sorry Allesandro, that's a couple of not-yet-fixed problems with Launchpad: see bug 1342 and bug 246041.]

Ok, i marked that as invalid in "Launchpad bugs". But will evolution consider it as a valid bug?

The Evolution developers do not use Launchpad for bug tracking. If you're using an Evolution package in a distribution that does use Launchpad for bug tracking (e.g. Ubuntu), you should mark this bug report as affecting that distribution as well.

Thank you for your bug report, that's a known upstream issue you can read about it on http://bugzilla.gnome.org/show_bug.cgi?id=409805

Yes, I got it... but at the same time it doesn't seem to me a secondary issue. I mean, 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...

that's an issue right but not a blocker, there is thousand of evolution bugs and other issues that need to be worked

yes, it is an issue and not a blocker, but at the same time for people who use Evolution for productivity and at work (like me) it is a remarkable bug. Calendars and appointment management are not a secondary feature in Evolution.
I mean, as far as I'm concerned, I had to migrate to Outlook and abandon Evolution after I lost some appointments... and even if it's a great software. As you all can understand this is quite disappointing.

what do you expect the "display again in nn minutes" to do if you stop the computer? display it nn minutes after next log-in? or at the time corresponding if the computer has restarted?

I am expecting the most intuitive reminder behavior in presence of alarms and alarm snooze function.

IDEAL BEHAVIOR: If a user chooses the option "Display again in N minutes" and the PC is switched off, *ideally* PC should switch on once N minutes are elapsed and should show again the notification (it is the common behavior of any smart device, cellphones, smart-phones, but also of simple alarm clocks).

CONSTRAINT: Since we are talking of a PC there is a remarkable constraint: PC can't (and maybe shouldn't) switch on automatically when the notification occurs.

If you keep the most intuitive alarm behaviour described above and add the previous constraint, the resulting behavior should sounds as the following:

CONCRETE BEHAVIOR: If a user chooses the option "Display again in N minutes" and the PC is switched off, *concretely* notification will be shown as soon as possible, when the PC is switched on again (a.k.a. immediately after reboot).

After all this is the behaviour adopted by the main reminder/notification software.

As an example I can report "sunbird", which replaced (along with Thunderbird) Evolution in my system. This calendar system works well and implements for notifications the same behaviour I theorized in the previous comment.

bug from 2009. Version not more supported.
change status to invalid.