Bug 201529 - Kopete with jabber ICQ transport adds icq contacts many times
Summary: Kopete with jabber ICQ transport adds icq contacts many times
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-26 10:12 UTC by Marcello Ceschia
Modified: 2023-01-12 05:16 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 Marcello Ceschia 2009-07-26 10:12:58 UTC
Version:            (using KDE 4.2.98)
OS:                Linux
Installed from:    SuSE RPMs

I use my own jabber server with icq transport.
In kopete i configured the jabber account and no icq account.
If I connect to the jabber server, all the contacts from icq will be added to contact list. For the first time this is not a problem. But after closing kopete and restart it, kopete adds the contacts again.
So after 10 times of restarting kopete, all icq contacts are listed 10 times.
This is not a version specific issue, it also happens with with kopete on kde 3.5 or kde 4.2 or kde 4.3rc2.

My jabber server is a openFire with latest version.
Comment 1 Sebastian Vöcking 2010-06-30 12:32:23 UTC
I have exactly the same setup as mentioned above and I can acknowledge that the bug still exists in Kopete 1.0.0 with KDE 4.4.5.
Comment 2 Sebastian Vöcking 2010-06-30 12:35:02 UTC
I should add that it seems that Kopete adds a new meta contact every time. So that it is not possible to assign an addressbook contact to the ICQ contact..
Comment 3 Stephan Wienczny 2011-02-12 00:36:39 UTC
This still happens in Ubuntu Natty with Kopete 1.0.80 and KDE 4.6.0
Comment 4 Andrew Crouthamel 2018-11-05 03:14:49 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 Andrew Crouthamel 2018-11-17 04:50:46 UTC
Dear Bug Submitter,

This is a reminder that 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2022-12-13 02:53:32 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2022-12-28 05:23:56 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-12 05:16:55 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!