Bug 304319

Summary:	Jabber ICQ transport contacts are not visible in contact list (Kopete v1.2.3)
Product:	[Unmaintained] kopete	Reporter:	Doctor Drive <docdrive>
Component:	Contact list	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Doctor Drive 2012-07-31 09:10:18 UTC

I registered at pyicq.aftar.ru ICQ transport.
The account mycooljid/pyicq.aftar.ru was added to identity. I can receive messages and reply, but the contacts are not appearing in contactlist.
Pidgin / qutIM shows these contacts.

Reproducible: Always

Steps to Reproduce:
1. Register at pyicq.aftar.ru transport (or any else?)
2. Accept authorization requests
3. Look at the contact list.
Actual Results:  
The transport was added but ICQ contacts are not in the contactlist.

Expected Results:  
The transport should be added and ICQ contacts from this transport should be visible in contactlist.

Tried from qip.ru and jabber.org accounts.

Comment 1 Doctor Drive 2012-07-31 09:40:35 UTC

Also confirmed for icq.jabber.org.by transport (Spectrum)

Comment 2 Andrew Crouthamel 2018-11-09 00:58:30 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 3 Andrew Crouthamel 2018-11-18 03:27:20 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 4 Justin Zobel 2022-12-20 22:51:50 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 5 Bug Janitor Service 2023-01-04 05:26:30 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 6 Bug Janitor Service 2023-01-19 05:16:49 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!