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 269685 - Changing a calendar item does not change the alarm text
Changing a calendar item does not change the alarm text
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Calendar
2.2.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Srinivasa Ragavan
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-11-18 22:37 UTC by Luke Hutchison
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch that fixes this problem (2.48 KB, patch)
2005-09-02 04:39 UTC, Chakravarthi
rejected Details | Review
updates all local alarm structures when calendar component changes (5.69 KB, patch)
2005-09-30 05:34 UTC, Chakravarthi
none Details | Review

Description Luke Hutchison 2004-11-18 22:37:39 UTC
In Evolution-2.0.1, if you create a calendar item with an alarm and then
let the alarm go off, then hit Snooze and change the appointment text, the
next time the alarm appears it displays the original item text, not the new
(changed) text.  I have also observed this with recurring events, without
hitting Snooze, and even between reboot cycles.
Comment 1 André Klapper 2005-06-01 14:28:46 UTC
right, confirming this on 2.2.2. i've seen this before.
Comment 2 Chakravarthi 2005-09-02 04:39:10 UTC
Created attachment 51686 [details] [review]
Patch that fixes this problem


Attaching a patch that fixes this problem. The CompQueuedAlarms
structure needs to be updated with most recent component as soon
as there is a change.
Comment 3 Chakravarthi 2005-09-21 08:49:24 UTC
the above patch is not the right fix and there are some problems relating to 
modification of calendar component after snoozing. they all can be put under same 
category. Suspect http://bugzilla.gnome.org/show_bug.cgi?id=269689 and this 
bug are related.
Comment 4 Chakravarthi 2005-09-30 05:34:54 UTC
Created attachment 52844 [details] [review]
updates all local alarm structures when calendar component changes

This patch works for all except for a gw recurring event for which the problem
is 
much deeper than just updating local structures ... opened a separate bug for
that 
http://bugzilla.gnome.org/show_bug.cgi?id=317575
Comment 5 Chenthill P 2005-10-01 06:22:56 UTC
committed the fix to gnome-2-12 and head branches.
Comment 6 Poornima 2005-10-06 03:46:42 UTC
Verified in evolution 2.4.1
Comment 7 Luke Hutchison 2006-05-10 03:50:58 UTC
This bug is actually still present in:

# rpm -q evolution evolution-data-server
evolution-2.6.1-1.fc5.2
evolution-data-server-1.6.1-1.fc5.2

Reopening.

See also bug 269689.
Comment 8 Chenthill P 2006-05-10 09:50:27 UTC
Lot of code has been changed in alarm now. Assigning to srini.
Comment 9 Srinivasa Ragavan 2006-05-10 09:59:27 UTC
I have rewritten alarm in 2.7.x. Im sure this will be fixed there. Lots of issues were resolved in the HEAD.  I tried it too. This is fixed in 2.7.x
Comment 10 André Klapper 2006-05-10 18:20:14 UTC
i can confirm that this is fixed in the development version (2.7.1). the fix will be available in the next major release (2.8).