Bug 333900

Summary:	nepomuk tags disappeared
Product:	[Applications] kaddressbook	Reporter:	Philippe ROUBACH <philippe.roubach>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	einmaladresse_2, jjm, meyerm, tokoe
Priority:	NOR
Version:	4.13
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Philippe ROUBACH 2014-04-26 10:46:44 UTC

i upgraded opensuse from kde 4.12.4 to 4.13.0

i use google contact

i assigned to all my contacts a nepomuk tag as for example "maison" , "restaurant" , "santé" to classify my contacts

for all contacts in the tag "Contact" the field "Catégories" is empty

if i want to add a nepomuk tag then the list is empty

Reproducible: Always

Comment 1 Jonathan Marten 2014-05-07 15:16:36 UTC

Not an exact duplicate, but root cause probably the same as bug 331896

Comment 2 Philippe ROUBACH 2014-09-22 06:41:48 UTC

i had to create again the "catégories" and assigned them to all my contacts (~130) .

please next time supply a tool which automaticaly import the data from the old version .

Comment 3 wuselwu 2014-09-22 07:07:10 UTC

Recreating does not help in all cases, as in combination with a CardDAV server, Akonadi messes up the categoeries with "akonditag:?=1" entries instead. I'm a bit disturbed as errors like this seemingly don't get any attention.

As data integrity of my PIM data is of high importance to me and at the moment I don't trust Akonadi any more, I had to switch to Evolution.

Comment 4 Denis Kurz 2016-09-24 20:52:26 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 5 Denis Kurz 2017-01-07 21:33:10 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.