Version: unspecified (using KDE 4.4.4) OS: Linux When addresses are moved between address books, they are not stored in the backing file immediately. Only after the address is edited (even without any change) does the address get saved (it always saved to the database, but not to the real file) Background story: I recently switched from KDE 3.5.9 to KDE 4.4.4 (by moving from Debian Lenny to Debian Squeeze); my addresses from ~/.kde/share/apps/kabc/std.vcf were correctly imported, but updates were not written to the vcf file, only to the mysql DB (i.e. updates were visible in kaddressbook, even after a restart, but the vcf file was never touched). Trying to solve this, I created a new address book (also as a vcf file, under ~/.local/share/contacts.vcf). I moved all addresses to the new adressbook using kaddressbook. This also worked, but the file remained empty. Surprisingly, new addressses were immediately visible in the file! Also, entries were stored in the vcf file after I opened them to edit them and immediately clicked "Save". However, this is very unsatisfying, because I have several command line tools which read the vcard file directly, so I need to have it up-to-date. And manually saving 600+ contacts is quite tedious. Reproducible: Always Steps to Reproduce: * Create two address books, both backed by a vcf file (no read-only mode set) * Create two contacts, one in each address book * Move the first contact from the first to the second address book Actual Results: * The vcf file that backs the second address book contains only one address, the one that was added directly Expected Results: * Both addresses should be visible in the address book
That sounds a lot like the bug I recently fixed in 4.5 branch: http://websvn.kde.org/branches/KDE/4.5/kdepimlibs/akonadi/monitor_p.h?view=log Anyone still having a 4.4 build around for backporting?
@Kevin This patch alone doesn't solve the problem. I can still reproduce the bug. Is there any server change involved? Ciao, Tobias
Yes, I am pretty sure there is a server change involved as well. Volker should know, he found and fixed the problem in trunk and I think he backported the server side change, but I have no idea which version that went into
is there some news about this issue ?
As Kevin mentioned ,this should be fixed already for some time and I was unable to reproduce the issue with Akonadi/KDE PIM.