Bug 63024 - No reminders until korganizar is run.
Summary: No reminders until korganizar is run.
Status: CLOSED DUPLICATE of bug 64120
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdepim   
(Show other bugs)
Version: 8.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-04-09 13:23 UTC by Tim Waugh
Modified: 2007-04-18 16:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 18:48:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Tim Waugh 2002-04-09 13:23:41 UTC
Description of Problem: 
This morning I set an event for 3:20pm today, with a 1 hour reminder.  There 
was no reminder; it's now 2:23pm. 
Version-Release number of selected component (if applicable): 
Steps to Reproduce: 
1. Set event with reminder.

Comment 1 Ben Levenson 2002-04-09 17:48:39 UTC
I can't reproduce this w/ kdepim-3.0.0-1. Is 'kalarmd' running? Was the 
calendar 'active'?

Comment 2 Tim Waugh 2002-06-14 14:17:39 UTC
Yes, but I hadn't started the calendar in that session.  This still happens.

Comment 3 Aleksey Nogin 2002-10-08 22:59:06 UTC
I see that same problem in Psyche (kdepim-3.0.3-3). If I restart my KDE session,
I do not see any alarms (although I kalarmd is running - the icon is there and I
see the process in ps). But if I run korganizer (without doing anything to
kalarmd), then after that (even after I quit korganizer), I get alarms.

I've set Severity to "high" since not getting alarms (while the kalarmd icon is
siting there "promising" you an alarm) could mean being late for an important
meeting, etc.

P.S. See also bug 64120 - it might be related.

Comment 4 Ngo Than 2003-02-01 09:49:01 UTC

*** This bug has been marked as a duplicate of 64120 ***

Comment 5 Red Hat Bugzilla 2006-02-21 18:48:41 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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