Version: (using KDE 4.4.1) OS: Linux Installed from: openSUSE RPMs This is a weird one...tags in nepomuk multiply themselves. Or rather: some tags do. I'm not sure if this is the correct category to place this bug in so move it to a more appropriate place if necessary. It's kinda hard to explain but if I start with a clean nepomuk database (by doing a rm -rf ~/.kde4/share/apps/nepomuk before logging in to KDE) the nepomuk database contain 5 tags: Business, Family, Friend, Linguistics, and School. I assume nepomuk get those from akonadi but can't recall ever having tagged anything with "Linguistics" even though it's possible (the rest may be default tags). Well, so far so good. I can also create new tags myself from within Dolphin and search for files with those tags. However, it is only a matter of time before I get several entries with the same tag in the "Add tag" dialog - like say four "Friends", 3 "Family", and 2 "Business". But ONLY tags that come from akonadi (if that's where they come from). The ones I've created myself never exhibits this behavior. I have as yet not been able to determine when and why this happens. I thought at first it may have been caused by upgrades to KDE through the packaging system, but it has happened when no upgrades have been installed as well. It's starting to get really annoying, and I really wish I knew where to look for the problem. The software in use is KDE SC 4.4.1, virtuoso 6.1.0. and soprano-backend-virtuoso 2.4.1.
Confirmed. I can reproduce this since some months. It only appears to happen with contact groups (from the vcf-file resp. akonadi). Additionally, existing tags don't show up in the tag-list anymore (although they still are listed on the right in dolphin). I cannot start to seriously use nepomuk as long as I have to keep on deleting whole databases in order to re-initialize the whole thing and re-tagging all files again :( Thanks in advance for stabilizing this.
Update: it is present in 4.4.2 as well (virtuoso components the same version as previously)
Update 2: This bug seems to have vanished in 4.5.0. During the time I've had 4.5.0 installed, this bug normally would have occurred a few times (after having nuked the nepomuk database in between) already but so far nothing.
Closing as per last comment.