https://bugs.kde.org/show_bug.cgi?id=382216
--- Comment #5 from Nick <ndor...@gmail.com> --- (In reply to Bug Janitor Service from comment #4) > 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 > mark the bug 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! Hello, It is a while since these events happened . Since then my machine as well as KDE/Kmail2 were upgraded . Now I use opensuse leap 15.4 and kmail /kontact is at level 5.19.3(21.12.3 ) With very few exceptions [ response time ] I haven't noticed the symptoms reported in 2017 . So I cannot recreate the 2017 failures . I still have problems with akonadictl fsck message regarding records with no RID. It is possible to have akonadictl fsck repair .... option that will [re]move the affected emails to another directory ... i.e. TB_handled_by_the_user ? The we can decide about them ..... If this comment helps, as far as I am concerned this bug can be closed . Thank you for your support . Best regards, Nick -- You are receiving this mail because: You are the assignee for the bug.
