Bug 324778 - Marking messages as unread not possible until re-entering folders
Summary: Marking messages as unread not possible until re-entering folders
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 4.11.1
Platform: Ubuntu Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-11 09:13 UTC by kde
Modified: 2017-01-07 22:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2013-09-11 09:13:34 UTC
When receiving a message while the contents of the selected inbox folder is displayed (including the newly received message), it is not possible to right click the folder Icon and mark all messages as read since this option is grey/disabled. Users have to click on another folder (eg. deleted messages) and then re-open the inbox folder to mark all messages as read.

This happens even though the inbox entry in the folder list displays the arrival and count of new messages. 

Reproducible: Always

Steps to Reproduce:
1. Open Kmail inbox folder.
2. Pray to receive new messages or have someone send you a test message.
3. Click get email button
4. New messages are in message list, inbox folder displayed in bold fonts and with the number of new messages
5. Right click on inbox folder

Actual Results:  
Mark all mesages as read is greyed out/disabled

Expected Results:  
Mark all messages as read should be available in the UI.
If the user switches folders and goes back to the inbox it works, but with additional clicks.
Comment 1 Denis Kurz 2016-09-24 18:24:02 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 2 Denis Kurz 2017-01-07 22:21:24 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.