| Summary: | Loose link to address book entry, if address book is closed in KAddress | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Gehold Bertin <NewsAssi> |
| Component: | Addressbook integration | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | wmhilton |
| Priority: | NOR | ||
| Version: | 0.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Gehold Bertin
2006-12-28 11:19:01 UTC
This particular issue appears to be fixed in Kopete 0.50.80 (Using KDE 4.0.85, Kubuntu package 20080708+svn829713-0neon1 in the KDE-nightly Neon repository) however a worse behavior has replaced it. If the contact resource (System Settings > KDE Resources) containing the Kopete contact's name is disabled, Kopete keeps the "Use addressbook name" option checked, so when the contact resource is re-enabled, the address book link is restored and the correct name is shown again. (This is good.) However, if the contact resource containing the Kopete contact information is disabled, the contact is shown with a blank name! (This differs from KDE3, where it would show the IM screenname.) Rather than showing a blank name, a better behavior would be: if the address book link for a contact is broken, default to showing the IM screenname with "(Broken Address Book Link)" in parentheses after the name. *** Bug 149995 has been marked as a duplicate of this bug. *** I've filed a new bug report (Bug 167496), since I deem the new behavior significantly different from the old behavior. This bug resulted from an unwanted persistant change in Kopete's settings, and that has been fixed. The new bug is the need for a better fallback routine when fetching the name from the address book fails. 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 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! 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! |