Version: 4.4.2 (using KDE 4.4.2) OS: Linux If korgac runs into trouble (in my case no connectivity when it tries to read my calendars on a remote DAV server) it throws up an error dialog. This is good. However if the problem has not corrected itself by the time korgac tries again, it piles another window on top. And another. And another. etc. Korgac should not display another error window if one is already on the screen. This makes for a poor user experience because each window has to have its "OK" button clicked. A single error window is sufficient. Reproducible: Always Steps to Reproduce: Set up a remote calendar via DAV with an item with a reminder. Sync up Unplug the network cable Wait. Actual Results: korgac throws up the error dialog when it can't connect to the DAV server. When it tries again and fails, it will throw up another dialog window. Then another. Then another. Then another Expected Results: korgac should throw up one dialog. When it goes to try again and fails, it should NOT display another window, as there is already one error window up on the screen. Likely a single static variable (bool errorWindowDisplayed) that is set just before the dialog is displayed, and which is cleared by the dialog when OK is pressed. Not 100% sure since I am not fully aware of the exact architecture of the program.
I also got this problem several times. It is really anoying. Additionally, if a remote calendar does not exist anymore or had to be changed, the error message for the old calendar still appears, although it is not valid anymore. Reproducible: Always Steps to Reproduce: Set up a wrong remote calendar via remote ical file. Reload calendar wait. when the errors appear, change the remote calendar link to a correct remote ical file Actual Results: korgac throws up the error dialog when it can't connect to the wrong remote file. When it tries, even after a change to a corrent remote file again and fails, it will throw up another dialog window. Then another. Then another. Then another Expected Results: korgac should check, if the calendar is still valid and delete the error entry.
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 korgac (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
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.