| Summary: | 'To' field completion only works for recent addresses | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | davidebasilio <marsicanbear> |
| Component: | contact completion | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | clay, dvratil, fetzt_doch, ingo, maf, miso, montel, public, stephan.kueffner, tobias |
| Priority: | NOR | ||
| Version: | 5.5.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
davidebasilio
2015-11-06 15:44:16 UTC
I have the same problem with a owncloud (carddav) account. Autocompletion not working with carddav addresses, only recent addresses. When clicking to "Auswählen" (right button on the line of the "to" field), carddav addresses are in the list. I can confirm this. There is no completion from the address book, not even from the local one. I fixed a bug in 5.1.1 about it. I have 5.1.3 but it still doesn't work. Only recent addresses get completed, not CardDAV. 5.1.x is very old. could you verify with 5.5.x or future 5.6.0 ? I am using openSUSE Tumbleweed with latest 5.5.3 and can confirm that it doesn't work. I have 2 google contacts/calendar accounts. Thanks for the update; changing status. There doesn't seem to be 5.5.3 tags in bugzilla yet, so using 5.5.2. Also doens't work for me - and hasn't for a while - presently running OpenSuSE Leap 42.3 and tumbleweed, but I'm pretty sure it was broken in 42.2 as well.
Turning off "recent contacts" in kmail settings means nothing is ever offered as a To:, CC: or BCC: address suggestion
To test further, I made a completely fresh install of Leap 42.3, with a single user. added one local contact and tried to send them an email. no match.
Pressing the select button found the contact.
My normal user has several loacl and CardDav addressbooks. Trying to search for something that should match gives several of these in akonadiconsole Debugger:
kontact-1186278907-SearchSession (0x18fc460) 127 { Command: "Search" Query: "{ "limit": -1, "negated": false, "rel": 0, "subTerms": [ { "cond": 0, "key": "name", "negated": false, "value": "Dave" } ] } " Collections: "QVector()" Mimetypes: "(application/x-vnd.kde.contactgroup)" Fetch Scope: { Fetch Flags: "QFlags(0x4|0x10|0x20|0x40|0x100|0x200)" Tag Fetch Scope: "QSet()" Changed Since: "QDateTime( Qt::TimeSpec(LocalTime))" Ancestor Depth: "0" Requested Parts: "QVector(PLD:RFC822)" } Recursive: "false" Remote: "false" }
kontact-1186278907-SearchSession (0x18fc460) 127 { Response: "Search" Error Code: "0" Error Msg: "" }
(the contact "Dave" should return at least 4 or 5 possibles)
I have deleted the all akonadi* directories & files under ~/.local/share, ~/.config and ~/.cache and re-created all accounts / resources. No change.
Should have said: Currently on vesrions: Kmail 5.5.3, using KF 5.36.0 Qt 5.9.1 but is affects more than just that version. I can confirm this bug, seen with various Kubuntu releases (12.04, 16.04, 17.10) with and without KDE backports PPA. Latest Kubuntu package version of kmail and akonadi is 4:17.04.3-0ubuntu1 (Kubuntu 17.10 with backports PPA). Behaviour is as described in comment #1, carddav/caldav server is Open Xchange. 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! |