Bug 294629 - Reminders don't trigger (or appear in Plasma's Digital Clock plasmoid) if on a remote Calender
Summary: Reminders don't trigger (or appear in Plasma's Digital Clock plasmoid) if on ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: reminder daemon (korgac) (show other bugs)
Version: 0.9
Platform: Chakra Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-22 18:13 UTC by Kubuntiac
Modified: 2017-01-07 22:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kubuntiac 2012-02-22 18:13:32 UTC
Version:           0.9 (using KDE 4.8.0) 
OS:                Linux

If I create an event with a reminder in Kontact's personal calender, it shows up fine. If I do the same thing, but on a calender stored in ownCloud, the event shows in Kontact fine (even after restarting) but it doesn't show in the calender you see when clicking on KDE's default clock, nor does the reminder ever display.

Reproducible: Always

Steps to Reproduce:
1. Create a calender in Kontact using the webdav resource and the owncloud option.
2. Create an event with a text reminder set to display 5 minutes before the event.

Actual Results:  
5 minutes before the event, nothing happens, even if I wait 5 more minutes

Expected Results:  
At 5 minutes before the event, the reminder displays

OS: Linux (i686) release 3.2-CHAKRA
Compiler: gcc

Kontact 4.8
ownCloud 3
Comment 1 Denis Kurz 2016-09-24 18:49:31 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 22:49:08 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.