Bug 245581 - Regression: Imap account emails displayed as unread even when read.
Summary: Regression: Imap account emails displayed as unread even when read.
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-07-23 22:29 UTC by Sabine Faure
Modified: 2018-10-27 02:34 UTC (History)
5 users (show)

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 Sabine Faure 2010-07-23 22:29:04 UTC
Version:           unspecified (using Devel) 
OS:                Linux

Read messages are displayed as unread next to the Imap account Inbox and folders whereas this should not be the case.

Reproducible: Always

Steps to Reproduce:
Prerequisite: having a working Imap account set up

- Launch Kontact and go to Kmail
- Check the number in between () next to the Imap account Inbox ex: Inbox (4)
- Click on 'New Message'
- Enter the recipient (Imap account email address), the subject and a few words.
- Click on 'Send'
- The recipient receives the email which is displayed in blue in the Message list view and the number next to the Imap account Inbox is now displaying one more email as it should ex: Inbox (5)
- Click on the newly received email in the Message list view

Actual Results:  
The newly received email is not displayed in blue anymore since it has been read however, the number remains the same ex: Inbox (5)

Expected Results:  
whereas it should have been decreased by 1 ex: Inbox (4).



So atm the number can only increase and eventhough emails are read they are still marked as unread.

Moreover, when accessing the same Imap account from another computer using Kontact 4.4.1 this does not happen: the read messages are not shown as unread.

Trunk, Svn Rev 1153490
Comment 1 Gael Beaudoin 2010-11-26 14:25:45 UTC
I also have the problem, using 4.6 beta 1.
Comment 2 Tobias Koenig 2010-12-12 16:52:48 UTC
Hej Sabine,

can you try current SVN trunk, please?
I have commited a patch that should fix this issue.

Ciao,
Tobias
Comment 3 simon 2011-01-28 14:27:59 UTC
hi,

have the same problem in recent git and a local kmail dir: some messages always stay unread, even when they were read and had the "read" state, but after updating the folder they are back in unread state

kmail during selecting a unread mail:

kmail2(6087) MessageList::Core::View::slotSelectionChanged: View message selected [ "Fwd: Server Büro" ]
kmail2(6087) KMReaderWin::setMessage: void KMReaderWin::setMessage(const Akonadi::Item&, MessageViewer::Viewer::UpdateMode) QSplitter(0xc319a0, name = "splitter2")
kmail2(6087)/kdewebkit KWebPage::acceptNavigationRequest: url:  QUrl( "file:///home/user" )  , type: 5 , frame: QWebFrame(0xb485b0)
kmail2(6087)/kio (Scheduler) KIO::SchedulerPrivate::doJob: KIO::SimpleJob(0x1a662e0)
kmail2(6087)/kdepimlibs (kpgp) Kpgp::Module::checkForPGP: Kpgp: gpg found
kmail2(6087)/kdewebkit KWebPage::acceptNavigationRequest: url:  QUrl( "file:///" )  , type: 5 , frame: QWebFrame(0xb485b0)
kmail2(6087)/kio (Scheduler) KIO::SchedulerPrivate::cancelJob: KIO::TransferJob(0x1a662e0) QObject(0x0)
kmail2(6087)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished: KIO::TransferJob(0x1a662e0) QObject(0x0)
kmail2(6087) MailCommon::SendMdnHandler::Private::handleMessages: AKONADI PORT: Disabled code in   void MailCommon::SendMdnHandler::Private::handleMessages()
kmail2(6087)/kdecore (kdelibs) KStandardDirs::findExe: findExe(): returning  "/usr/bin/update-mime-database"
Comment 4 Matěj Laitl 2011-05-01 14:29:22 UTC
Once I was able to reproduce this problem, but now it seems fixed in kmail 4.5.95.
Comment 5 Andrew Crouthamel 2018-09-22 02:02:59 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 02:34:54 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!