https://bugs.kde.org/show_bug.cgi?id=524080
Bug ID: 524080
Summary: Contact name displayed twice in kdeconnect-sms
conversation list
Classification: Applications
Product: kdeconnect
Version First 26.04.3
Reported In:
Platform: KDE Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: messaging-application
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
***
If you're not sure this is actually a bug or valid feature request, instead
post about it at https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Do not paste LLM output.
Please remove this comment after reading and before submitting - thanks!
***
DESCRIPTION
In kdeconnect-sms's conversation list, some contacts occasionally show up with
their name duplicated (e.g. instead of "Megatron", it shows "Megatron,
Megatron"). This happens for contacts that have only one saved phone number and
one name — not contacts with multiple numbers, so it doesn't seem to be a case
of the app correctly joining multiple real numbers into one display name.
STEPS TO REPRODUCE
I haven't found a reliable way to trigger this on demand. It appears
intermittently on some conversations in the list. In one case it resolved on
its own for a conversation that had been showing the duplicate, without me
changing any settings or contacts.
OBSERVED RESULT
The contact's name is shown twice, comma-separated, in the conversation list,
even though the contact has a single name and a single phone number.
EXPECTED RESULT
The contact's name should be shown once.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.7.3
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
ADDITIONAL INFORMATION
Setup: kdeconnect 26.04.3-1 (Arch Linux), paired with an Android 16 phone using
Google Messages as the default SMS app.
My guess (unconfirmed) is that this may be related to how the conversation list
builds a display name from a thread's list of participant addresses — if a
single phone number is somehow represented more than once in that address list
(e.g. two different formats of the same number, such as with and without a
country code), the name-joining logic might not be deduplicating by underlying
number, only by exact string match, and would print the resolved contact name
once per address entry instead of once per unique person.
--
You are receiving this mail because:
You are watching all bug changes.
