Summary: | kmail The process for the pop3 protocol died unexpectedly. | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Stephen Dunn <nzlbob2332> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | dnlbtz, kollix |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
kontact can't even start because missing of akonadi/akonadiconnectionrc
kmail startup messages new kmail output without failure |
Description
Stephen Dunn
2009-08-28 22:52:39 UTC
I can not reproduce. Does it occur always? Does it happen only with a specific POP3 account (can you test with a different POP3 server) ? I had the same problem as I updated from 4.2.x to 4.3.0. Yesterday I updated from 4.3.0 to 4.4.0 and I have the same issue again. Unfortunately I don't remember how I fixed the problem; could be that I did something in the .kde/share/apps/kmail/ folder. This happens for all my POP3 accounts (I have no IMAP accounts) and I get one popup for each of them. Restart of KDE or kmail didn't fixed this failure. There is no kio_pop3 in my process list (read from that in http://lists.kde.org/?l=kdepim-users&m=124043386004619&w=2 ). I don't know how the kio_pop3 process is started, so I am not immediately able to provide a bt or core dump. Created attachment 40909 [details]
kontact can't even start because missing of akonadi/akonadiconnectionrc
Created attachment 40910 [details]
kmail startup messages
I should mention that the failure occurs always at my place; not only under the special circumstances described in the original bug report.
Restart of KDE once again fixed the problem. I provide the kmail output once again for comparison. Created attachment 40923 [details]
new kmail output without failure
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you! |