Bug 335876

Summary: User is stuck on 'Welcome to KMail' page after viewing it
Product: [Applications] kmail2 Reporter: Sabine Faure <sabine>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: montel
Priority: NOR    
Version: 4.12.3   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sabine Faure 2014-06-06 11:46:36 UTC 
When checking KMail version the user is stuck on that view and cannot get back to reading emails.
He has to quit Kmail and relauch it to do so whereas it worked in previous versions.

Reproducible: Always

Steps to Reproduce:
1. Launch Kmail
2. Click on a folder from folder view and then on an email to view it
3. Now go to menu Settings/Configure Kmail...
3. A black background page is displayed with 'Welcome to KMail 4.12.2'
4. Now try clicking back on the folder to display the same email
Actual Results:  
It does not work whereas it did in previous versions.

The users is stuck on the 'Welcome to KMail' view and even if he tries to select a different folder from folder view it does not work either.

The only option is to quit Kontact.

Note: This is not due to the fact that Kmail is synching for new emails as I have waited until the sync was done and tried to click on a folder and it still did not work.

Kmail 4.12.2


Note: This is not due to the fact that Kmail is synching for new emails as I have waited until the sync was done and tried to click on a folder and it still did not work.
Comment 1 Laurent Montel 2014-06-11 05:58:04 UTC 
Can't reproduce for the moment.
After syncing we can see mail here.
I will continue to investigate.
Comment 2 Denis Kurz 2016-09-24 18:02:06 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 3 Denis Kurz 2017-01-07 21:44:31 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.