Bug 332780 - Following kmail account wizard is very confusing
Summary: Following kmail account wizard is very confusing
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.13 Pre
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 335627 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-03-29 19:09 UTC by Rohan Garg
Modified: 2017-01-07 22:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Rohan Garg 2014-03-29 19:09:14 UTC 
When trying to follow the KMail account wizard after launching kmail for the first time leads to very confusing results.


Reproducible: Always

Steps to Reproduce:
1. Fill in GMail account details
2. Make sure "Find provider settings on the Internet" is checked
3. Click on next
4. Settings are correctly found
5. Click on next again
6. Nothing happens
Actual Results:  
Apparently, one needs to click on the "Create Account" button which I thought would create a new account on GMail and it was very counter intuitive to find that it actually adds the account locally.

Expected Results:  
Clicking next adds the account
Comment 1 Gerald Senarclens de Grancy 2014-05-31 17:43:52 UTC 
*** Bug 335627 has been marked as a duplicate of this bug. ***
Comment 2 Gerald Senarclens de Grancy 2014-05-31 17:45:14 UTC 
Agreed - this is very confusing.
Comment 3 Denis Kurz 2016-09-24 18:02:47 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:18:01 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.