Bug 249463 - Kopete accumulates empty meta-contacts
Summary: Kopete accumulates empty meta-contacts
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: Contact list (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-29 22:43 UTC by Alex
Modified: 2023-01-01 05:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2010-08-29 22:43:23 UTC
Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

while using kopete with adding accounts and adding/moving contacts, creating meta-contacts, etc. kopete accumulates empty meta-contacts. i think they could be silently deleted, as there is no use in a completely empty contact.

Reproducible: Sometimes

Steps to Reproduce:
using kopete in a normal everyday use

Actual Results:  
many empty metacontacts spamming the contact-list when showing offline contacts

Expected Results:  
no useless meta-contacts
Comment 1 Störm Poorun 2010-09-17 00:13:53 UTC
I agree this is a problem. However, there should be a user option to delete empty meta contacts. It should not occur automatically, or silently.

I sometimes create empty meta-contacts for a reason - when I am ordering large numbers of contacts, and will later add IM sub-account details to those contacts. 

Alternatively, retention of empty meta-contacts can be useful in identifying when contacts have removed you from a service (such as facebook) :)

So I propose that there be an option instead to purge empty meta contacts.

Additionally it would be good to filter on just empty meta contacts so that a user can view them alone, and determine what action to take manually.
Comment 2 Alex 2010-09-17 20:11:55 UTC
there are several good ways to do it. automatically removing alone is not so useful.

- remove or ask to remove a metacontact if the last entry left. handle it good if there are many empty metacontacts because of some action
- make an menu-option "purge empty contacts". not so useful, because you need it not so often, but easy to use and not automatic.
- make a filter for "empty metacontacts". Easy to use, easy to remove the metacontacts, but the filter does not seem to be useful to the user, why should he want to view empty contancts?!

maybe the best:
- allow filtering for contacts by protocol with multiple-choice selection:
  - contacts with (at least) icq
  - contacts with (at most) icq
  - contacts with at least icq AND jabber
  - contacts with at least icq OR jabber
  - ...
  - contacts with at most [] (empty list)

this function is useful for other purposes at organizing the contact-list, too, can can be used to find empty contacts.

Gui:

Choice Field:
- one of those
- all of those

list:
  ChoiceField (protocol) checkbox (NOT)
  button + (add another listitem for protocol selection)


another option would be a view grouping contacts by protocol:

None:
empty contacts
ICQ:
contacts with at least icq
MSN:
contacts with at least msn


so long for some brainstorming :).
Comment 3 Sven Krohlas 2012-06-11 12:34:03 UTC
That bug has become a real problem for me, as Kopete has accumulated thousands of those empty meta contacts during the last months. Consequently startup literally takes hours!

Is there a simple way to delete all empty meta contacts?
Comment 4 Andrew Crouthamel 2018-11-09 00:58:25 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Alex 2018-11-09 07:29:11 UTC
(In reply to Andrew Crouthamel from comment #4)
> Dear Bug Submitter,
> 
> This bug has been stagnant for a long time. Could you help us out and
> re-test if the bug is valid in the latest version? I am setting the status
> to NEEDSINFO pending your response, please change the Status back to
> REPORTED when you respond.
> 
> Thank you for helping us make KDE software even better for everyone!

I do not use kopete anymore since a long time.
Comment 6 Justin Zobel 2022-12-02 01:23:08 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-12-17 05:13:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-01-01 05:19:58 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!