Bug 310910 - Sometimes new mails are not received/shown
Summary: Sometimes new mails are not received/shown
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: 4.10.2
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-30 10:14 UTC by Roger Larsson
Modified: 2017-01-07 22:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Download stuck at 89% (82.21 KB, image/png)
2012-12-02 15:46 UTC, Roger Larsson
Details
After cancel and restart stuck at 0% (6.34 KB, image/png)
2012-12-02 15:48 UTC, Roger Larsson
Details
Strace of kontact - NOTHING (really nothing) (74 bytes, application/octet-stream)
2012-12-02 15:48 UTC, Roger Larsson
Details
Strace of akonadi_pop3 (3.48 KB, application/octet-stream)
2012-12-02 15:49 UTC, Roger Larsson
Details
lsof of akonadi_pop3 (15.36 KB, application/octet-stream)
2012-12-02 15:49 UTC, Roger Larsson
Details
akonadi_pop3 strace of download cancel and restart (55.72 KB, application/octet-stream)
2012-12-02 15:51 UTC, Roger Larsson
Details
kontact strace of same download cancel restart cycle (37.41 KB, application/x-gzip)
2012-12-02 15:53 UTC, Roger Larsson
Details
akonadi_pop3 reaktions to a restart of kontact (115.53 KB, application/octet-stream)
2012-12-02 15:54 UTC, Roger Larsson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Larsson 2012-11-30 10:14:59 UTC
Noticed that I had received some mails on my mobile (IMAP) that I had not received on Kmail.
Tried to check email several times - did not help...
- No error message

Restarted kmail
Mails showed up!

My wife had similar problems, a while ago - that time not even a restart of kmail helped...
(if I remember correctly I had to kill the background pop3 daemons)

Reproducible: Sometimes

Steps to Reproduce:
1. No idea...
2.
3.
Comment 1 Laurent Montel 2012-12-01 13:50:15 UTC
" No idea..." too how to test/debug it :)
I need more infos.
Comment 2 Roger Larsson 2012-12-01 22:47:55 UTC
Laurent, I have no idea myself...
To rare to debug - review?

Is there working error propagation? (errors from servers, daemon)
Is there some kind of watchdog, if pop3 daemon freezes?
How are these shown to user? (console log is not good enough)
Comment 3 Roger Larsson 2012-12-02 15:43:45 UTC
Happened to my wife again... have some traces - will add
resolved by killing 'akonadi_pop3_resource'
Comment 4 Roger Larsson 2012-12-02 15:46:47 UTC
Created attachment 75582 [details]
Download stuck at 89%
Comment 5 Roger Larsson 2012-12-02 15:48:00 UTC
Created attachment 75583 [details]
After cancel and restart stuck at 0%
Comment 6 Roger Larsson 2012-12-02 15:48:46 UTC
Created attachment 75584 [details]
Strace of kontact - NOTHING (really nothing)
Comment 7 Roger Larsson 2012-12-02 15:49:23 UTC
Created attachment 75585 [details]
Strace of akonadi_pop3
Comment 8 Roger Larsson 2012-12-02 15:49:52 UTC
Created attachment 75586 [details]
lsof of akonadi_pop3
Comment 9 Roger Larsson 2012-12-02 15:51:26 UTC
Created attachment 75587 [details]
akonadi_pop3 strace of download cancel and restart
Comment 10 Roger Larsson 2012-12-02 15:53:47 UTC
Created attachment 75588 [details]
kontact strace of same download cancel restart cycle
Comment 11 Roger Larsson 2012-12-02 15:54:50 UTC
Created attachment 75589 [details]
akonadi_pop3 reaktions to a restart of kontact
Comment 12 Roger Larsson 2013-05-21 19:46:52 UTC
happened twice again, needs to kill akonadi_pop3_resource (or logout)
Learned about akonadiconsole - will try that next time...
Note: new version 4.10.2
Comment 13 Denis Kurz 2016-09-24 18:15:51 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 14 Denis Kurz 2017-01-07 22:22:32 UTC
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.