Summary: | Authorization dialog keeps popping up despite "Keep password" checkbox being selected | ||
---|---|---|---|
Product: | kresources | Reporter: | Tristan Miller <psychonaut> |
Component: | remote | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | CONFIRMED --- | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Tristan Miller
2005-01-09 23:36:39 UTC
I attempted to work around the bug by removing the remote resource in question from KOrganizer and then re-adding it. However, the bug persists. Next I will try removing its associated entries in KWallet to see if that might fix the problem. Will report on my findings. I deleted the wallet containing the remote calendar's username and password. Next time KOrganizer tried to access the resource, I was prompted to create a new wallet to store the username and password. This had no effect on the bug; I'm still periodically prompted for authorization. Confirming the bug still exists with KDE 3.4 beta 1. I have also seen this behavior occasionally on KDE 3.4 Beta 2 (compiled from source using Konstruct, on Ubuntu Hoary), but it does not appear to be very deterministic. Sometimes killing all KDE program instances and restarting Kontact fixes this, but not always. I have Kwallet in use, and the calendar is behind webdavs, hosted on localhost with apache2. Moreover, if I do not enter the password and leave the dialog open, then error dialogs containing the message "Error while loading %s" where %s is the name of the calendar will appear, one per each time it tries to refresh the calendar. See http://www.hut.fi/~ptvirtan/kontact.png for an example. Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. I'm experiencing the same in kde 3.5.6 installed from FreeBSD(v6.2release) ports Oddly enough, it seems that the authorization dialog pops up at the reload-interval which is specified in the resource konfiguration, _even_ when automatic reload is set to "never" or "on startup" rather than "regular interval". *** This bug has been confirmed by popular vote. *** |