| Summary: | remote calendars' alarms don't go off | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | Fernando Schapachnik <fernando> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aaronw, avasaralak, finex, petyr, rjwgnr27 |
| Priority: | NOR | Keywords: | investigated, needs_verification, triaged |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Fernando Schapachnik
2004-06-10 19:28:57 UTC
Instrumenting korgac to use dumpAlarms() shows that it doesn't reload the remote resource on modification. *** Bug 96553 has been marked as a duplicate of this bug. *** This is a pretty major bug for us. Our company, in its infinite wisdom, decided to "upgrade" us to Microsoft Exchange, despite the fact that 2/3's of engineering runs Solaris. The biggest complaint is that there is no meeting notification. Now that Korganizer can finally download calendar information from Exchange, this should work. I'm surprised it's taking so long for a fix for this bug. Any chance of this bug getting fixed anytime soon? As far as I can tell, it doesn't even load the remote resource to begin with. If I kill the alarm daemon and restart it, it never pops up for any upcoming events when the events are stored on the Exchange server. *** Bug 105166 has been marked as a duplicate of this bug. *** I created a new bug 116086 reporting a similar problem. I did some debugging to verify that the problem is not due to mis-configuration on my part. Please find below an explaination of my debugging and results. 1)Enabled Exchange plugin. 2)Since the reminder functionality was working for local calendar, I downloaded my calendar from the Exchange 2000 server using the Exchange plugin into the standard resource file std.ics at ~/.kde/share/apps/kroganizer/std.ics 3)Saved the default resource 4)Restarted the korgac daemon and I fully expected a reminder. However, I did not get one. 5)Saved the existing std.ics 6)Starting with a clean std.ics, I locally added an event and restarted the korgac daemon. 6)The reminder popped up at the expected time. I compared the working and non-working std.ics files and I found out that the ACTION field of the VALARM block of the test event is empty in the downloaded std.ics whereas it is set to DISPLAY for the locally configured alarm. Please find below the 2 VALARM blocks. Working BEGIN:VALARM DESCRIPTION: ACTION:DISPLAY TRIGGER;VALUE=DURATION:-PT10M END:VALARM Not working BEGIN:VALARM ACTION: TRIGGER;VALUE=DURATION:-PT15M END:VALARM I think the possible reasons that reminders are not working for remote calendars are 1)The ACTION field for the VALARM block of an event is not set to DISPLAY and/or 2)As observed above the korgac daemon just ignores the remote calnedar. This bug is pretty old. Any chance of it getting fixed? This also affects OpenXchange calendars on the current version of Kubuntu (6.06 at this time) Just added the repository for the current version of KDE (3.5.4) This bug appears to have been fixed, at least for OpenXchange! Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. I've tried using a remote calendar using ftp, it works correctly (using current trunk). Maybe someone with exchange could test it too. set status to "waitingforinfo" until somebody will give more informations :-( Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |