After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 634113 - Categories in Contact View Cannot Be Deleted
Categories in Contact View Cannot Be Deleted
Status: RESOLVED DUPLICATE of bug 630361
Product: evolution-data-server
Classification: Platform
Component: Contacts
2.32.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
evolution[categories]
Depends on:
Blocks:
 
 
Reported: 2010-11-05 19:52 UTC by arthur.machlas
Modified: 2011-01-19 12:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description arthur.machlas 2010-11-05 19:52:30 UTC
This may be a duplicate of bug: 626505, however that bug has been mark fixed and I am not sure whether it is possible to re-open.

The categories chooser dialog available in the contact editor mode displays a list of default categories, and provides the option to add new categories or delete existing ones. The delete option does not work, either for existing default categories or newly created ones. 

Steps to reproduce:
1) Open the contact editor, and choose the categories editor. Create a new category. Close category editor, save and close contact editor.
2) Re-open contact editor, and delete the newly created category as well as one or more of the default categories. Close category editor, save and close contact editor.
3) Re-open contact editor, the deleted categories are still present.
Comment 1 Akhil Laddha 2010-11-08 04:38:52 UTC
I cann't reproduce the problem with the steps mentioned here. I have tried on master (2.91.2)
Comment 2 Ari Torhamo 2010-11-13 09:24:32 UTC
I'm experiencing this bug exactly as described with Evolution version 2.30.3 (on Ubuntu 10.10).
Comment 3 Milan Crha 2011-01-19 12:15:06 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 630361 ***