Bug 144556 - Source selection for avatar and nickname is unreliable
Summary: Source selection for avatar and nickname is unreliable
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: Contact list (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-23 09:06 UTC by Degand Nicolas
Modified: 2023-01-05 05:27 UTC (History)
0 users

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 Degand Nicolas 2007-04-23 09:06:55 UTC
Version:           0.12.4 (using KDE 3.5.6, Debian Package 4:3.5.6.r1.dfsg.1-4 (lenny/sid))
Compiler:          Target: x86_64-linux-gnu
OS:                Linux (x86_64) release 2.6.18-4-amd64

When I have a metacontact with several protocol subcontacts, if I specify a specific protocol subcontacts, it will frequently revert to another subcontact nickname and avatar (frequently the ICQ one).
Comment 1 Degand Nicolas 2007-04-24 18:21:23 UTC
I can predict the behaviour of this more accurately now. Let's say someone have an account A (on Gtalk with no nickname), an account B (on MSN), and an account C (on whatever but with a nickname) that he does not use anymore. 

If I select explicitly that I want it to use the nickname of account B, if for some reason, he connects with the account A only, it will fall back on the nickname of account C. Even if it reconnects with account B, it will keep the account C avatar and nickname, which may have been irrelevant for years (I only keep the account C in the contact list for logging reasons).
Comment 2 Andrew Crouthamel 2018-11-02 04:23:42 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-16 02:39:32 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 4 Justin Zobel 2022-12-06 00:56:51 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-21 05:17:51 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-05 05:27:02 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!