Autocomplete feature in KMail address fields cause deadkeys to stop working as they should
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| KDE PIM |
Fix Released
|
Medium
|
|||
| kdepim (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
vitor@seattle:~$ lsb_release -rd
Description: Ubuntu intrepid (development branch)
Release: 8.10
vitor@seattle:~$ uname -a
Linux seattle 2.6.27-7-generic #1 SMP Fri Oct 10 03:55:24 UTC 2008 i686 GNU/Linux
apt-get dist-upgrade last run today - 13/10.
KDE version 4.1.2
KMail version 1.10.1
Being used inside Kontact 1.3
----
My computer has an international QWERTY keyboard configured to use deadkeys to make accented letters. Therefore, if I press the "'" (single quote) key, nothing happens, but pressing the "e" key in sequence produces "é".
That's not what happens in KMail's address fields. If I want to search for a contact named "André", typing the usual keys for writing that name produces "Andr'e".
The problem is probably the autocomplete mechanism, because if I type "Andr" and then press ESC to close the autocompletion suggestions, I can then type "'" + "e" and get "é" as it's supposed to.
Let me know if you need any other information or if I haven't explained myself well. English is not my native language. Thank you.
| Vítor E. Silva Souza (vitorsouza) wrote | #1 |
| Jonathan Thomas (echidnaman) wrote | #2 |
| Changed in kdepim: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| Changed in kdepim: | |
| status: | Unknown → New |
| Vítor E. Silva Souza (vitorsouza) wrote | #3 |
| Jonathan Thomas (echidnaman) wrote | #4 |
| Changed in kdepim: | |
| status: | Confirmed → Fix Released |
| Changed in kdepim: | |
| status: | New → Fix Released |
| Changed in kdepim: | |
| importance: | Unknown → Medium |
Oh, forgot to mention that this did not happen when I was using Kubuntu 8.04 with KDE 3.5. If I remember well, I think that it started recently and that when I first installed Kubuntu 8.10 alpha 6 it was working correctly. One of the updates from that point to the beta version caused this, I think. I'm not sure though.