Bug 261373

Summary:	Kopete does not change the ICQ status message via Jabber transport
Product:	[Unmaintained] kopete	Reporter:	Tobias Stegmann <stegmannt>
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tobias Stegmann 2010-12-27 14:21:08 UTC

Version:           unspecified (using KDE 4.5.90) 
OS:                Linux

If Kopete is connected to my ICQ account via jabber transport and if I try to change my global status message, Kopete changes the status message of each account except for the transports status message.

The only way to change the transport's status message is to change the default status message and restart Kopete.

Reproducible: Always

Steps to Reproduce:
- Login to an ICQ account over a Jabber transport.
- Change your global status message or the status message of the Jabber account.

Actual Results:  
The Jabber account's status message changes, the ICQ status message does not, even if Kopete shows up the new status message.

Expected Results:  
The ICQ status message should be changed.

I'm not sure if this is a bug or an enhancement since the setOnlineStatus method doesn't look fully implemented yet.

See: http://websvn.kde.org/branches/KDE/4.6/kdenetwork/kopete/protocols/jabber/jabbertransport.cpp?view=markup

Comment 1 Andrew Crouthamel 2018-11-05 03:13:13 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-17 05:01:52 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 3 Justin Zobel 2022-12-18 08:18:32 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 4 Bug Janitor Service 2023-01-02 05:26:45 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 5 Bug Janitor Service 2023-01-17 05:18:03 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!