Summary: | KOrganizer gives me two reminders for the same event upon startup | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Tristan Miller <psychonaut> |
Component: | reminder daemon (korgac) | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christophe, smartins |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Screenshot showing two reminders for the same event. |
Description
Tristan Miller
2005-06-23 04:06:23 UTC
Created attachment 11553 [details]
Screenshot showing two reminders for the same event.
This screenshot shows KOrganizer immediately upon startup; two alarm dialogs
for the same event are visible. I have moved the dialogs so that they are
side-by-side; originally they were on top of one another.
Do you log out of KDE between entering the appointment and the alarm date? If not, do you close KOrgac (the reminder daemon) after closing KOrganizer? At first glance I thought this could be related to #102489, which is fixed in 3.4.2, but I'm not sure anymore. > Do you log out of KDE between entering the appointment and the alarm date? No. The appointment and alarm are entered at the same time. > If not, do you close KOrgac (the reminder daemon) after closing KOrganizer? Yes. KOrganizer, KOrgac, and KDE were all closed. In fact, step #2 could well have read "Shut down the computer", since that's what I did in this case. I shut down my laptop and turned it back on again less than five days before the appointment. *** Bug 109139 has been marked as a duplicate of this bug. *** Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. I don't think this is valid anymore, at least in KDE4. Can you retest? Thanks. As I reported this bug, I used SuSE with KDE 3.4.1? This was 3 years ago. I do not use this distro anymore. But now with Debian 5.0 and KDE 3.5.9/10 only one dialog exists for all alarms, so the problem seems to be gone, I thought. But in the end I'm not sure, because after the first alarm occurs, I pressed the "dismiss" button for this event (the only one), it was grayed out but the window was not gone. After reopening kontact, the alarm reoccurred! Dismissing it again the item was now deleted and did not occure anymore. I can not say if this is the same error, I did not have any problems with Debian 4.0 and KDE 3.5.5. I'm the original reporter, and haven't had any recurrence with KDE 3.5.10. (In reply to comment #7) > As I reported this bug, I used SuSE with KDE 3.4.1? This was 3 years ago. > I do not use this distro anymore. But now with Debian 5.0 and KDE 3.5.9/10 > only one dialog exists for all alarms, so the problem seems to be gone, > I thought. But in the end I'm not sure, because after the first alarm occurs, > I pressed the "dismiss" button for this event (the only one), it was grayed > out but the window was not gone. After reopening kontact, the alarm reoccurred! > Dismissing it again the item was now deleted and did not occure anymore. > I can not say if this is the same error, I did not have any problems with > Debian 4.0 and KDE 3.5.5. The "dismiss" button was greyed out because you didn't have any alarm selected, if you select a line on the list the button will be enabled. (In reply to comment #8) > I'm the original reporter, and haven't had any recurrence with KDE 3.5.10. Closing then. |