Bug 164093 - kopete messes up contacts
Summary: kopete messes up contacts
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-14 20:49 UTC by Cristi
Modified: 2023-01-11 05:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cristi 2008-06-14 20:49:38 UTC
Version:           0.50.80 (using 4.00.82 (KDE 4.0.82 >= 20080610), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.25-gentoo-r4

I have 2 yahoo accounts and they have some contacts in common, and here starts the problem:
if I have only one account online the contact in common is displayed under the group of the account that is offline. Furthermore if I have both accounts online then the "common contacts" are displayed only once, just under an account and just under a contact group. I tried to be clear, let me know if my English is not up to the job
Comment 1 Cristi 2008-07-07 15:37:36 UTC
would have been nice to at least let me decide if common buddys should be displayed once or twice
Comment 2 Matt Rogers 2009-03-27 03:39:31 UTC
you haven't combined the two contacts into a single "metacontact" have you?
Comment 3 Cristi 2009-03-27 17:38:39 UTC
nope, I just made 2 accounts that had some common buddies
Comment 4 Matt Rogers 2009-09-06 03:42:16 UTC
Do you have two accounts on another protocol and if so, does that protocol also exhibit this behavior? It's no problem if you don't, I'm just looking for an additional data point so I know where to start looking for this bug.
Comment 5 Cristi 2009-09-06 22:32:21 UTC
sorry I don't
Comment 6 Roman Jarosz 2009-11-01 14:45:16 UTC
Do you still use 0.50.80, if so could you update to newer version?
Comment 7 Cristi 2009-11-10 15:50:12 UTC
svn version updated at least in a weekly basis
Comment 8 Andrew Crouthamel 2018-11-02 23:02:12 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 9 Andrew Crouthamel 2018-11-16 05:30:48 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 10 Justin Zobel 2022-12-12 01:56:17 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 11 Bug Janitor Service 2022-12-27 05:20:20 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 12 Bug Janitor Service 2023-01-11 05:18:17 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!