After restarting Akonadi server due to Bug 319157 - Excessive I/O usage during mail import with KMailCVT. the maildir resource finally starts processing file_db_data stuff into the maildir. During that I get said error messages on console. Reproducible: Didn't try Steps to Reproduce: 1. Import mails 2. Look ~/.xsession-errors Actual Results: AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/announce-ml/new" AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/announce-ml/cur" AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/backports-ml/new" AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/backports-ml/cur" AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/cut-ml/new" AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/cut-ml/cur" AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/devel-announce-ml/new" AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/devel-announce-ml/cur" AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/devel-changes-ml/new" AkonadiAgentServer(16654)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/devel-changes-ml/cur" Directories do exist. Two examples: martin@merkaba:~#1> ls -l /home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/devel-changes-ml/cur insgesamt 0 martin@merkaba:~> ls -l /home/martin/.local/share/local-mail/.KMail1.directory/.KMail-Import.directory/.Lichtvoll.directory/.Debian.directory/devel-announce-ml/new | head -5 insgesamt 26548 -rw-r--r-- 1 martin martin 102042 Mai 1 12:42 1367404968.R463.merkaba -rw-r--r-- 1 martin martin 5756 Mai 1 12:42 1367404968.R798.merkaba -rw-r--r-- 1 martin martin 7040 Mai 1 12:42 1367404969.R0.merkaba -rw-r--r-- 1 martin martin 4380 Mai 1 12:42 1367404969.R104.merkaba Expected Results: If its not a real error: Don´t noise the logs. If its a real error: Fix it :) KDE SC 4.10.2 on Debian Unstable during Akonadi post-processing KMailCVT import of 6,7 GB Mails.
I'm getting the same messages in 4.11 RC1, e.g. I started kmail, selected the JUNK-mail folder, did a "Select All" and hit the Shift-Del keys to remove all junk mails. In the konsole where I started kmail, I got lots of AkonadiAgentServer(5542)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know "/home/koller/Mail/.inbox.directory/JUNK-mail" whereby the folder of course exists.
I confirm it.
The KDirWatcher is used in MailDir resource, reassigning. (IIRC the message is not critical, it was just a debug message that sounds scary).
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
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.