On Tue October 5 2010 15:03:57 Martin Schlander wrote:
Tirsdag den 5. oktober 2010 13:51:59 skrev Michael Henatsch:
"Nepomuk was not able to find the configured database backend 'redland'. Existing data can thus not be accessed."
the following redland related packages are installed: - libraptor1 - librasqal2 - libredland0 - redland - soprano-backend-redland
Puzzled
Are you reusing /home from an older version of opensuse/kde?
Yes, I am.
Check in .kde4/share/config/nepomukserverrc that you have:
"Used Soprano Backend=virtuosobackend"
I checked: soprano was set up as the backend. I changed the line as you instructed and now Nepomuk and strigi work (apparently) without any hitches.
And make sure you have these packages installed:
soprano-backend-redland soprano-backend-virtuoso
Yep, both are installed.
IIRC redland is still needed, even if it isn't used for storage.
So the nepomuk problem appears to be solved. However, the discrepancy between the addressbook proper and the "select-list" remained. I have now renamed all std.vcf* files in ~/.kde4/share/apps/kabc to "ex-std.vcf*" and exported the kaddressbook to that directory as "std.vcf". The contact in question now shows up as in the addressbook, i.e. with the correction properly applied. At this point I feel I have found a kludge (exporting the addressbook to the "kabc" directory every time I have edited a contact) but the problem that the contacts between the two sources are not in synch obviously remains. Any further ideas? cheers Mike Besides the new std.vcf there is also a std.vcf_2. Why that? -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org