I have been using stable (fresh install) for few months and this morning I
decided to upgrade to testing.

As soon as I login, the Korganizer Reminder Daemon tells me that I have 3 tasks
due.  Perfect as this is indeed the case.  However, the Daemon keeps reminding
me every 30 seconds about (I get the beep).  More interestingly, it keeps
adding the same 3 tasks to my list of due tasks.

So after few iterations, my "Reminders - Korganizer Reminder Daemon" windows
looks like
Task 1
Task 1
Task 1
Task 1
Task 2
Task 2
Task 2
Task 2
Task 1
Task 2
Task 1
Task 2
.... (tens of times)
Task 3
Task 3
Task 3
Task 3
.... (tens of times).

I tried to dismiss and suspend.  No success, the reminder comes back after 30
seconds.

Hello,

Friday 13 January 2012 16:18:06 rašė:

Can you reproduce this with the new tasks? What if you delete and recreate
those tasks?

Hi Modestas,

I still have the problem.  I will try to create new tasks to see whether I still have the problem.  I am actually using KDE for quite a few years now and have a bunch of day-to-day tasks.  But I will for sure try to do some tests.

For now, I can confirm that I still have the problem (I have the latest version of testing as I am updating every mornings).

Let me know if you want me to conduct any particular tests.

Gilles

Modestas,

I dug a little bit and it appears that the problem is only with the recurring tasks.

Gilles

severity 655757 important
thanks

Once again, I think we have here a bug severity that is overflated.

Let's re-read the definition of "grave":

          makes the package in question unusable or mostly so, or causes
          data loss, or introduces a security hole allowing access to the
          accounts of users who use the package.

On the other hand, let's read the definition of "important":
          a bug which has a major effect on the usability of a package,
          without rendering it completely unusable to everyone.

I think this bug deserves to have "important" severity.

severity 655757 important
thanks

Once again, I think we have here a bug severity that is overflated.

Let's re-read the definition of "grave":

          makes the package in question unusable or mostly so, or causes
          data loss, or introduces a security hole allowing access to the
          accounts of users who use the package.

On the other hand, let's read the definition of "important":
          a bug which has a major effect on the usability of a package,
          without rendering it completely unusable to everyone.

I think this bug deserves to have "important" severity.

tag 655757 +moreinfo
thanks

There are newer versions of kmail are available in the Debian repos. Could you
please check that this bug still applies?

Regads, sandro

tag 655757 +moreinfo
thanks

There are newer versions of kmail are available in the Debian repos. Could you
please check that this bug still applies?

Regads, sandro

Hi Sandro,

Thanks for following up.

Before I answer your question, I am using the AMD64 testing version.

Back to your question, I do not have this problem anymore as I recreated all my entries. However, I have noticed two "problems":
1. the reminder daemon does not work in the sense that I have very very few reminders for my tasks (and I have not been able to identify a pattern, i.e. why those which work work and not the others)
2. the recurrence does not work if I only specify a start date (so no due date). That means that if i flag a to-do as complete, the next start date is not set.

An important information is how I installed testing. I followed the recommended approach: I install the bare minimum of the stable version and then upgraded to the testing one.

Let me know if you need anything else. I understand the information I have provided you with is pretty limited so feel free to let me know if there is anything I can test for you.

Thanks,

Gilles

Hi,

well than I would suggest to close this bug, cause it can't be reproduced
anymore.
reminders for my tasks (and I have not been able to identify a pattern, i.e.
why those which work work and not the others)
date). That means that if i flag a to-do as complete, the next start date is
not set.

Please create own bugreports, that makes it easier to track things
independently. And  it would be nice, if you search for matching upstream bug
reports (http://bugs.kde.org).

recurrence task have really problems, I also saw that in kolab issue tracker:
https://issues.kolab.org/show_bug.cgi?id=3949
https://issues.kolab.org/show_bug.cgi?id=3944


Regads,
sandro

Hi,

well than I would suggest to close this bug, cause it can't be reproduced
anymore.
reminders for my tasks (and I have not been able to identify a pattern, i.e.
why those which work work and not the others)
date). That means that if i flag a to-do as complete, the next start date is
not set.

Please create own bugreports, that makes it easier to track things
independently. And  it would be nice, if you search for matching upstream bug
reports (http://bugs.kde.org).

recurrence task have really problems, I also saw that in kolab issue tracker:
https://issues.kolab.org/show_bug.cgi?id=3949
https://issues.kolab.org/show_bug.cgi?id=3944


Regads,
sandro