Bug 265982

Summary:	kopete lost contact after psi plus
Product:	[Unmaintained] kopete	Reporter:	Belomir <leggis>
Component:	Contact list	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	1.0.80
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Belomir 2011-02-10 14:00:07 UTC

Version:           1.0.80 (using KDE 4.6.0) 
OS:                Linux

There was a contact in two groups in kopete contact list. Psi plus support multiple groups only for show. But I tried to change group for the contact and it changed to only one. Later I started kopete (kopete and psi didn't worked simultaneously). And the contact lost. Once it blinked for a second on kopete startup in right group.
Psi plus shows this contact right. Online jabber server utility shows that contact in place.
This contact don't present in ~.kde/share/apps/kopete/contactlist.xml

Reproducible: Didn't try




OS: Linux (i686) release 2.6.35-26-generic
Compiler: cc

Comment 1 Belomir 2011-02-10 14:29:56 UTC

Manipulations with contactlist.xml are not successful:
getting the contact to one group, restoring last version of contactlist.xml (where the contact still presents) and setting right group for contact and metacontact.
After kopete startup it shows for a moment and dissapears, removing all contact's traces in contactlist.xml

Comment 2 Andrew Crouthamel 2018-11-05 03:11: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 3 Andrew Crouthamel 2018-11-17 04:56:55 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-14 03:09:03 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 2022-12-29 05:23:46 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-13 05:14:42 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!