Version: 1.1 (using KDE KDE 3.5.8) Installed from: Compiled From Sources Compiler: gcc-4.2.2 glibc-2.7 OS: Linux Using courier imap server on remote machine. Locally there is KDE-3.5.8 on a LFS build. Sending/Receiving mails using that imap server works prefectly fine. I now tried to store my contacts on that imap server. For this i followed http://docs.kde.org/development/de/kdebase/userguide/kontact-imap-clients.html as closly as i can. When now entering a new contact using the the contacts plugin in Kontact, a popup comes up saying "No writable resource was found, saving will not be possible. Reconfigure KMail first.". (yes, I enabled the groupware thing in kmail) The entered data are lost. This also happens when trying to save an local stored contact in that imap resource. Same popup comes up, and contact is lost. Some other bugs which are flying around and seems to describe that problem, too: http://people.debian.org/~terpstra/message/20071029.195612.444f4187.en.html http://www.mail-archive.com/kubuntu-bugs@lists.ubuntu.com/msg13317.html Btw, i cannot say whether it worked in 3.5.7 - i first tried that in 3.5.8.
Found another machine with 3.5.7 so i was able to verify that against 3.5.7 (built on LFS too). With the previous version it works prefectly. After I enabled the groupware thing in KMail, it asked whether the folders (like Contacts, Calendar etc.) should be created. This didn't appear when trying it on 3.5.8.
Could you please check if this is the same problem as described in bug 150790?
dunno what the reporter meant with "...IMAP resources are not used in Kontact..." but all in all it seems to go the same direction, yes. Seems that the refered ubuntu-thread at https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/139433 is taking about a quite simmilar problem. The discussed key named 'TheIMAPResourceAccount' isn't set here too. So finally i think it could be the same problem.
>So finally i think it could be the same problem. Well, try the workaround mentioned in comment 2 and 3 of that bug report.
Sorry for being so late - yes, tat solves the problem. Do you think there will be a 3.5.9 which has this bug fixed?
*** This bug has been marked as a duplicate of 150790 ***