Version: (using KDE KDE 3.4.3) Installed from: Ubuntu Packages OS: Linux kaddressbook doesn't seem to care about what vCards are actually on an imap server when you store address on it. I used to have all my address on an imap server, then I reinstalled kde (lost kaddressbook's cache) and selected storage on the same server (the vCards are still there - I've checked) but it doesn't recognise them any more (not even any errors). There seems to be no way to get it to actually *see* what is on the server. If I add a new contact it correctly adds a vCard, but then if I delete that from the server it never realises the contact has gone. Can you please add a 'refresh list' action (preferably automatically) that actually downloads the Contacts folder from the IMAP server and updates the local cache with its contents?
On Sat, Nov 12, 2005 at 01:56:13PM -0000, Tim Hutt wrote: Hi, > kaddressbook doesn't seem to care about what vCards are actually > on an imap server when you store address on it. > > I used to have all my address on an imap server, then I reinstalled > kde (lost kaddressbook's cache) and selected storage on the same server > (the vCards are still there - I've checked) but it doesn't recognise them any more (not even any errors). Have you setup KMail correctly as well? KAddressBook uses KMail to access the IMAP server, so when you haven't configured an IMAP account it won't work... Ciao, Tobias
Of course. KMail works fine, and is using the IMAP server properly. I can even open the vCards in my Contacts folder if I have have the groupware folders shown.
In fact, I just discovered that if I just open a vCard in my IMAP/Contacts folder and close it again without doing anything else, then KAddressBook somehow now recognises it. There must be some cache thing that doesn't get updated properly.
Undoing automatic change to status NEW. Sorry for the noise.
Is this still a problem in KDE 4.3?
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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 mark the bug 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!