Bug 255638

Summary: 'Mark All Mails as Read' does not work anymore (Actions tab)
Product: [Unmaintained] KMail Mobile Reporter: Sabine Faure <sabine>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: CLOSED FIXED    
Severity: normal CC: adam, ludwig.reiter
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sabine Faure 2010-10-30 03:04:45 UTC 
Version:           unspecified (using Devel) 
OS:                Linux

The 'Mark All Mails as Read' entry from the Actions tab does not seem to work anymore whereas the 'Mark Mail as Read' from the view when clicking on an email folder and selecting a mail works fine.

This does not seem logical.

Reproducible: Always

Steps to Reproduce:
- Launch Kmail-mobile
- Go to an email folder containing two unread emails
- Click on the folder name
- Select one of the unread emails
- Click on 'Mark Mail as Read'
- The email is not longer marked as unread (it is displayed in black)
- Click on the arrow icon next to the folder name to go back to the main view
- Open the 'Actions' tab
- Click on 'Folder'
- Click on 'Mark All Mails as Read'

Actual Results:  
Nothing happens the unread mails is still displayed in red.

Expected Results:  
The remaining email should be marked as read ie displayed in black.

This is a regression since it worked fine last time I tested it on the 30/09/10.

N900, 4:4.6~20101029.1191021-1maemo1.1190669
Comment 1 Till Adam 2010-11-07 20:45:48 UTC 
Works fine for me with 1193974. Please re-test.
Comment 2 Ludwig Reiter 2010-11-11 13:20:39 UTC 
tested with kmail-mobile 20101111.1195418

Test:
Req: some unread mails are in the inbox.
1. Select the inbox.
2. Click again on the inbox to start maintaince mode.
3. Select one unread mail.
4. Click on "Mark Mail as Read" or "Mark Mail as Important" in the left list.
=> Nothing happens. (failure)
Comment 3 Sabine Faure 2010-11-12 20:55:03 UTC 
It is corrected now.

I retested this today and it works fine now.

N900, 4:4.6~20101112.1195992-1maemo1.1196001
Comment 4 Sabine Faure 2010-11-12 20:57:48 UTC 
Ludwig I think the bug you are describing in comment #2 is independent from the one I reported in my description so I'll open a new one instead since I can still partly reproduce that one.

N900, 4:4.6~20101112.1195992-1maemo1.1196001
Comment 5 Sabine Faure 2010-11-12 21:04:28 UTC 
Ludwig see new bug #256739.