Bug 227664

Summary:	Kopete won't download any contact information using Jabber-ICQ-transport
Product:	[Applications] kopete	Reporter:	Ben M. <bmarwell>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Ben M. 2010-02-19 13:39:39 UTC

Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    Ubuntu Packages

Scenario:
* I created a ICQ-over-jabber.transport, using an account from gmx.de
* I had to restart kopete for the transport contact to appear (this is another bug, see https://bugs.kde.org/show_bug.cgi?id=194249)

Well, here's the issue:
* I see my ICQ contacts now. But they do have their UINs as display name.
* They are in no group at all.
* When trying to acces the contact's information, kopete display the vcard dialog and loads forever
* No avatars.

Expected behaviour:
* Look up existing ICQ-Contacts in contactlist.xml for more information 
and/or
* Be able to recieve information directly. At very least screen names.

I'm pretty sure this is a kopete-bug/-non-feature, since it does work in gajim.

Comment 1 Andrew Crouthamel 2018-11-02 23:02:34 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 2 Andrew Crouthamel 2018-11-16 05:38:03 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?

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

Comment 3 Justin Zobel 2022-12-13 02:54:16 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 4 Ben M. 2022-12-13 07:03:07 UTC

Sorry, I didn't react to the comment you posted five years ago (which was already 8 years after I opened this bug).
I haven't been using  neither of the components for a long time now, thus I will close it. Since there was no answer within years after opening, I think "unmaintained" would be a suitable status. Feel free to change it as you see it fit.