Bug 133927 - appointment alarms don't work in the calendar
Summary: appointment alarms don't work in the calendar
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 3
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dave Malcolm
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-09-28 15:13 UTC by Tom "spot" Callaway
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-10-30 15:02:59 UTC

Attachments (Terms of Use)

Description Tom "spot" Callaway 2004-09-28 15:13:32 UTC
Description of problem:

When alarms are enabled for appointments, they never go off.

Version-Release number of selected component (if applicable):


How reproducible:

I can't make alarms work, and I've got several set.

Steps to Reproduce:
1. Add an appointment.
2. Enable an alarm for 15 minutes before the start time.
3. Watch it do nothing.
Actual results:


Expected results:

Alarm popup, 15 minutes before start time.

Additional info:

I do not have global alerts enabled.

Comment 1 Matthew Miller 2006-07-10 20:17:06 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

Comment 2 John Thacker 2006-10-30 15:02:59 UTC
Closing per lack of response to previous request for information.  This bug was
originally filed against FC3 and has remained in NEEDINFO state for quite some
time.  Many packages and bugfixes have been made since the last substantive bug

Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only.  Please install a still supported version and retest.  If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version.  Otherwise, if this a security issue, please change the
product to Fedora Legacy.  Thanks, and we are sorry that we did not
get to this bug earlier.

Note You need to log in before you can comment on or make changes to this bug.