Bug 259480

Version:           unspecified (using Devel) 
OS:                Linux

In each line edits the fist character is entered automatically as upper case but in case of passwords this is problematic since the password is found incorrect eventhough the user typed it correctly.

Reproducible: Always

Steps to Reproduce:
Prerequisite: having a transport server password not starting by an upper case character.

- Launch Kmail-mobile
- Click on 'Write new Email' button
- Open the 'Actions' tab
- Scroll down and click on 'Composer'
- Click on 'Configure Transport'
- Click on 'Add'
- A 'Create Outgoing Account' dialogue opens
- Select SMTP (the ligne is highlighted in blue)
- Enter the server name (ex: KDAB)
- Click on 'Create and Configure' button
- A 'Configure account' dialogue opens
- Enter the Mail server hostname (ex: KDAB server hostname)
- Check the 'Server requires authentication check box
- Enter your login
- Enter your password
- Check the 'Store SMTP password' check box
- Select 'SSL' as the encryption
- Select 'PLAIN' as the authentication
- Click on the 'Ok' button
- Select the server you've just created as the default one
- Click on 'Ok'
- In the Composer enter a subject, a recipient (your Imap address) and a few words
- Click on 'Send'

Actual Results:  
The email is not sent and in a yellow 'KDE Mail' dialogue appears containing an error about your password.

For some reason the first letter of each field is automatically entered as upper case which is a pb here since passwords are case sensitive. 

If the password did not contain an upper case character to start with you will get an error message when trying to send an email even if as a user you've entered the password correctly!

If you retry entering the password compensating for the first letter being upper case then it works fine.

Expected Results:  
There should not be an automatic upper case for the first character in the password field.



Note: this bug is extremely hard to reproduce once you've managed to get the transport server to work since the login and password are remembered in the wallet I did not find a way to remove them to retest this once I got the transport to work.

Before that I could reproduce this bug everytime.

N900, 4:4.6~20101210.1205130-1maemo1.1204898