Bug 263807 - huge amount of Empty Tags on Nepomuk
Summary: huge amount of Empty Tags on Nepomuk
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-21 02:42 UTC by Tomas
Modified: 2017-01-07 22:04 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
List of Categories is full of empty records (104.03 KB, image/png)
2011-01-21 02:42 UTC, Tomas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas 2011-01-21 02:42:11 UTC
Created attachment 56266 [details]
List of Categories is full of empty records

Version:           4.6 (using KDE 4.5.95) 
OS:                Linux

I can see a huge amount of empty Tags when i want to set Category to Contact 

Reproducible: Always

Steps to Reproduce:
* run Kontact
* edit any contact
* on Contact Tab attempt to select any Category 

Actual Results:  
see attached screenshot

Expected Results:  
no empty records are available (used metadata are the only available)

I am using Nepomuk and Strigi since it is available in KDE. This might be a result of previous versions of it.
I suspect Nepomuk to store empty tags since i allowed "Read Metadata from Nepomuk" in digiKam (and I had to remove those empty tags from digiKam one by one to be able to use tags on digiKam again).

Ask me if more info if necessary.
Comment 1 Robby Engelmann 2011-01-21 07:34:18 UTC
I found similar duplicate tags for "mark message...", but recently I found a possibility to delete them in Kontact settings.
Comment 2 Tomas 2011-06-17 12:59:45 UTC
I have finally found the bug - All empty Tags are imported from invalid values in IPTC tag from digiKam in my case.

I do not know how did it happens, but I found I do have a lot of photos marked as "My Tag" id digiKam, which came from "" (empty value) in IPTC tag. Once again, I do not know the origin of it, but I am suspicious about some earlier version of digiKam as I do not use other application to access photos and I do save all digiKam information in files as well (so this empty value can be result of "dirty playing" with tags).
Nevermind, when I allowed both directional sync between digiKam and Nepomuk, it did created thousands of empty tags. I have tried to delete these in KAdressBook (as contacts may contain Categories (Nepomuk Tags), which can be removed), but I did not succeed in deleting empty Tags.

To be sure, I have successfully verified on small group of these files with invalid IPTC tag. I am willing to provide a sample if needed.

How to proceed now:
* Nepomuk guys: There is "Bug 275859 - Deleting "empty" tag in Dolphin results in a crash" From Michał Zając 2011-06-16. Can you please advise how to get rid of empty Tags in Nepomuk?
 
* Gilles, would it be possible to prevent importing empty Tag when Reread metadata from images? Could you please advise how to remove empty tags from files?
Comment 3 Gary Waap 2012-05-24 07:43:55 UTC
I have just under 800 contacts and see the list of empty tags and "nemopuk" tags growing daily, there are thousands and thousands of them.  I have created a new user account a week ago and imported my contacts to the new user, after day one there were some empty tags, now a week later the tags have again infested the system with hundreds of empty or nemopuk tags slowing down the system.  I don't think this can be attributed to digikam as digikam is not part of the new user's setup. I use my computer for work and I simply can't work like this...
Comment 4 Anders Lund 2012-08-16 20:19:10 UTC
I have a number of empty tags in kaddressbook if I look at categories, There is no way to delete them that I found out. The category chooser for a contact have an 'x' icon to delete them, but it does not work :((((((
Comment 5 Denis Kurz 2016-09-24 20:52:01 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 6 Denis Kurz 2017-01-07 22:04:35 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.