| Summary: | kopete forgets display name source custom setting | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Divan Santana <divan> |
| Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | jan.molnar |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Divan Santana
2009-11-20 10:33:32 UTC
Cannot reproduce with Kopete from KDE 4.3, which protocol does the contact use? I believe the contact is MSN/WLM. I'd like to double check however since upgrading to KDE 4.4 beta and now RC1 I still can not see any contacts via kopete or via kmail composer. I can see the contacts in address book of kontact just not via kopete/kontact. I'd update this bug when it works in KDE 4.4 The kde I am running (4.4 beta2 on kubuntu) I can now access my contacts and link the accounts again. I'll close this bug as the problem is not in kopete its that kopete opens before the addressbook is available to KDE. This will be fixed once akonadi starts on boot and if kopete opens after the bug doesn't exist. Ok this bug does exist. It only happens with Windows Live Messager contacts. It doesn't remember the linking details to your address book. I have the same problem, every time I change Display Name Source to Custom, write there something and reconnect my Facebook jabber account my text is replaced by facebook name of that person. (Kubuntu 10.04 beta 2, Kopete 1.0.0) 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! 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! Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version? If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you! 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! 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! |