Bug 277107 - Alarms can't be set to fire at event start, must be at least a minute in advance
Summary: Alarms can't be set to fire at event start, must be at least a minute in advance
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: incidence editors (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-05 05:10 UTC by Paul Thomas
Modified: 2017-01-07 21:24 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Thomas 2011-07-05 05:10:03 UTC
Version:           unspecified (using KDE 4.5.5) 
OS:                Linux

It doesn't seem possible to set an alarm for the time of an incidence: for example, to set a reminder for 12:00 for an event starting at 12:00.  The latest possible reminder is a minute before (11:59 in this example).

In earlier versions this was possible, and particularly useful in conjunction with zero-length events to pop up a reminder at a particular time.

(This is korganizer 4.4.9, which doesn't appear in Bugzilla's drop-down list.)

Reproducible: Always

Steps to Reproduce:
Create a new incidence.
Turn on reminders.
Spin the dial down to "1 minute", then try to reduce it further to 0 minutes.
(Or: type in the box.)

Actual Results:  
0-minute delays aren't allowed; the minimum is 1 minute.

Expected Results:  
0-minute delays are allowed (although -1 isn't).
Comment 1 Denis Kurz 2016-09-24 18:46:13 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:24:32 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.