Ubuntu
evolution package

Customized alarms NOT saved in Evolution appointment

Bug #33416 reported by laksdjfaasdf
10
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Medium
evolution (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Flight4, latest Evolution 2.5.92 update:

Customized Alarm settings are not saved and have wrong values:

Make a new appointment:

Then do the following in the dialog:

> Options > Alarms

You get alarm customize dialog:

> Alarm > Customize

And edit "Pop up an alert ... before the start of the appointment"

You get a new Alarm dialog:

But there the pop up an alert input box has the value:

"4294967295"

Looks like an uninitialized 32 bit Integer or sth?

If you close the dialogs and edit the appointment again the alarm settings are gone.

Have included screenshots.

Revision history for this message
laksdjfaasdf (laksdjfaasdf) wrote : Create Appointment

Create Appointment

Revision history for this message
laksdjfaasdf (laksdjfaasdf) wrote : Customize alarm

Customize alarm

Revision history for this message
laksdjfaasdf (laksdjfaasdf) wrote : Edit alarm

Edit alarm

Revision history for this message
laksdjfaasdf (laksdjfaasdf) wrote : My edited alarm

My edited alarm

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

Thanks for your bug report, this issue is known upstream: http://bugzilla.gnome.org/show_bug.cgi?id=333689

Changed in evolution:
assignee: nobody → desktop-bugs
status: Unconfirmed → Confirmed
Revision history for this message
Geoff Jacobsen (geoffj) wrote :

This fix doesn't look like it will happen upstream anytime-soon but I feel that since evolution is the calendaring tool of choice for ubuntu that it is a major bug to go live with especially when the bug is not in breazy. Therefore is it not worth applying a patch to?

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

"Applying a patch" is easy, writting a patch is not as easy. If you have a patch for it we would be happy to apply it

Revision history for this message
Geoff Jacobsen (geoffj) wrote :

I thought someone would say that :)

I'll give it a go - I might get lucky.

One thing I have discovered is a user work around:

If one edits the Calendar preferences and changes "Show a reminder" to something other than 15 minutes (no need to tick the check box) the problem goes away but setting it back to 15 re-introduces the problem. This should indicate that the fix should be small at least.

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

Upstream pointed that a patch has been sent for it: http://mail.gnome.org/archives/evolution-patches/2006-March/msg00081.html

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

This upload fixes the issue:

 evolution (2.6.1-0ubuntu5) dapper; urgency=low
 .
   * debian/patches/17_fix_alarm_delay_for_calendar.patch:
     - fix alarm being set to "-1" (Ubuntu: #33416)
   * debian/patches/18_fix_label_typo.patch:
     - fix type to the "To Do" label (Ubuntu: #36744)
   * debian/patches/19_fix_account_conditional.patch:
     - fix account conditional (Ubuntu: #26854)

Changed in evolution:
status: Confirmed → Fix Released
Revision history for this message
Geoff Jacobsen (geoffj) wrote : fix alarm for calandar and duplicate menu entry

This patch replaces the ubuntu5 patch:

  17_fix_alarm_delay_for_calendar.patch

This old patch fixed the -1 custom alarm problem but introduced a duplicate menu entry to the alarm_types menu.

Revision history for this message
Geoff Jacobsen (geoffj) wrote :

re-opening because 17_fix_alarm_delay_for_calendar.patch introduces a duplicate menu entry bug. See attached patch for full fix.

Changed in evolution:
status: Fix Released → Unconfirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

that issue is fixed, please open a new bug for the new one

Changed in evolution:
status: Unconfirmed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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