Bug 8643 - Address completion does not work for the To: Cc: Bcc: fields in the kmail composer window
Summary: Address completion does not work for the To: Cc: Bcc: fields in the kmail com...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords: Triaged, UPSTREAM
Depends on:
Blocks:
 
Reported: 2013-01-10 12:48 CET by Martin Ward
Modified: 2013-11-23 16:12 CET (History)
2 users (show)

See Also:
Source RPM: kmail-4.8.5-1.2.mga2
CVE:
Status comment:


Attachments

Description Martin Ward 2013-01-10 12:48:14 CET
Description of problem:

Address completion does not work in the To: Cc: Bcc: box in the kmail composer window

Version-Release number of selected component (if applicable):

kmail-4.8.5-1.2.mga2

How reproducible:


Steps to Reproduce:
1. Open kmail
2. Click "New" to start composing a new email
3. Type the first few characters of an address in the address book

Expected result: the first matching address shows up in grey text
and the address can be completed by pressing tab.

Actual result: nothing!

I wasn't sure about the severity: in one respect, address completion
is a major feature of an email client (I use it many times per day).
On the other hand, it can be worked around (eg: enter the address book,
search for the person, click on the email address to start a new email).
However, the workaround is fiddly compared to just typing a few letters
and pressing TAB.
Martin Ward 2013-01-10 12:48:42 CET

CC: (none) => martin

Manuel Hiebel 2013-01-11 22:54:04 CET

Keywords: (none) => UPSTREAM
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=259949

Comment 1 Samuel Verschelde 2013-08-28 18:15:02 CEST
This is an upstream bug. Assigning to maintainer in case he wants (and has time to) to track its status and provide a fix in Mageia.

Keywords: (none) => Triaged
CC: (none) => stormi
Assignee: bugsquad => nicolas.lecureuil

Comment 2 Manuel Hiebel 2013-10-22 12:09:19 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 3 Manuel Hiebel 2013-11-23 16:12:57 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.