Bug 416148 - inbox, new messages,quantity "3" and only one displayed in the folder
Summary: inbox, new messages,quantity "3" and only one displayed in the folder
Status: REPORTED
Alias: None
Product: kmail2
Classification: Applications
Component: folders (show other bugs)
Version: 5.13.1
Platform: OpenSUSE Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-12 08:41 UTC by Philippe ROUBACH
Modified: 2021-01-28 09:04 UTC (History)
1 user (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 Philippe ROUBACH 2020-01-12 08:41:22 UTC
SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT

For inbox 3 new messages are announced and only one is displayed in the folder 

EXPECTED RESULT

For inbox 3 new messages are announced and 3 are displayed in the folder 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66
Qt Version: 5.14.0

ADDITIONAL INFORMATION

kde apps 19.12.1

i must quit kontact then relaunch it to see 3 messages in the folders
Comment 1 stakanov.s 2020-01-12 10:19:05 UTC
I would suggest you control for the following:
in opensuse the Kmail/Kontact application is given with a preconfigured Agregator group considering linux, kde and opensuse activities. 
Once you have a mail, you are shown "1" in the counter, respectively more if you have more mail. Once you read them, the counter goes down. If all mails are read, by hierarchy, now you are shown the number of unread messages in the aggregtor app. So if there are 3 news, you are shown the number three. Once mail is available again, the number will show the number of mails. 
I am not aware if you can deactivate the monitoring of the aggregator app. But you can surely, if you do not use the aggregator, take of the groups. So the problem would vanish. 
If instead you should encounter that one of the mails is always "unread" although it had been opened, you may have run into a bug crashing kmail (and hanging the status of mails until a "akonadictl restart" in CLI and a closing of the "zombie" kmail via the syscontrol application. 
This bug mentioned is known and reported. 
So you will have to live with it until the new version of kmail that should arrive with 15.1. 
Else this would then not be a bug but a feature (no pun intended) and somebody more educated may enlighten you about the possibility to change this (wanted) behavior. 
Kind regards.
Comment 2 stakanov.s 2020-01-12 10:25:22 UTC
And while reading that this is probably the latter case:
bare in mind that if you use spamassasin, clamav (especially) and also a lot of filters, there may be a considerable time span (several minutes until half an hour) until all the filters are through and the messages are correctly attributed, thus in the meanwhile they may be listed as arrived but are not visible because not attributed to the right folder. 

I do not know if this could be your case. Just a guess.
Comment 3 Philippe ROUBACH 2020-01-12 11:48:25 UTC
thanks

i use spamassassin and 3 other filters to route to different boxes.

if i manually apply all filters then it takes 3 or 4 s. for 3 messages.

i don't think this is a filter problem.

>> So you will have to live with it until the new version of kmail that should 
>> arrive with 15.1. 

15.1 for what software ?

i know kde apps 19.12.1 , kmail 5.13.1 but 15.1 ...
Comment 4 stakanov.s 2020-01-12 16:09:55 UTC
(In reply to Philippe ROUBACH from comment #3)
> thanks
> 
> i use spamassassin and 3 other filters to route to different boxes.
> 
> if i manually apply all filters then it takes 3 or 4 s. for 3 messages.
> 
> i don't think this is a filter problem.
> 
> >> So you will have to live with it until the new version of kmail that should 
> >> arrive with 15.1. 
> 
> 15.1 for what software ?
> 
> i know kde apps 19.12.1 , kmail 5.13.1 but 15.1 ...

My bad sorry, I meant the 15.2 version of Leap. I think currently you are maybe using the KDE repos with the 15.1? 
Supposing you are using mariadb (as opposed to postfix that some do) did you check if (after this happens and you simply exit kmail) there is a non reactive instance of kmail staying resident once you exited via the menu bar? 
When I encounter here the problem, if you exit and reenter without manually terminating it, I have kmail segfaulting, this whether I restart akonadi or not. If instead I terminate it manually and restart thereafter, then the mails are correctly shown. 
I think the very same problem is present in the kmail 5.10.3 Version of the main repo (KDE Frameworks 5.55). 
You never get any segfault / backtrace?
Comment 5 Philippe ROUBACH 2020-01-12 16:25:56 UTC
As indicated in "description" I get last version of:

plasma : 5.17.5
frameworks 5.66.0
kde apps 19.12.1

with the last kmail 5.13.1 I get only one time a crash when launching kontact. since no more.

fir severa
Comment 6 stakanov.s 2020-01-13 17:18:04 UTC
I was able today to reproduce the issue on the "base installation" of kmail, from Leap 15.1 that is:
Plasma 5.12.8
Frameworks 5.55.0
QT 5.9.7
As filters I use spamassassin and clamav. 
Now, the issue was that two messages arrived on the same postbox with a certain lag of time. (About 1 h of difference). 
The first was visible, the second not. 
Issues encountered: the message that was visible would not shift to "read" status even if selected long time in preview (against the settings) and shifted only when double clicked and read (note: only after applying the workaround mentioned hereafter). The second message was not visible and stayed
invisible. 
I found however a workaround that you may try and that avoids to restart every time the program. Worked for me, that does of course not mean it will work for you. But if, it it would be nice if you report back: 
You have in the main view of kmail/kontact a "search bar". Here you can select to show you only new or also only unread messages. When selecting: show only new messages:
First I was now able to shift the message status of the message visible. 
Once "read" this one, the other one "reappeared". It was then possible to read the message normally and the status changed correctly. 

Regards.
Comment 7 Philippe ROUBACH 2020-01-13 18:13:28 UTC
ok thanks i will try next time it occurs.
Comment 8 Philippe ROUBACH 2021-01-17 13:16:39 UTC
kde apps 20.12.1
kde plasma 5.20.5
kde frameworks 5.78.0
qt 5.15.2

problem still there
Comment 9 Philippe ROUBACH 2021-01-28 09:04:21 UTC
kde apps 20.12.1
kde plasma 5.20.5
kde frameworks 5.78.0
qt 5.15.2

problem still there