Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 307931 - kde-base/kmail-4.3.5 "cannot start pop3/pop3s/imap process"
Summary: kde-base/kmail-4.3.5 "cannot start pop3/pop3s/imap process"
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: AMD64 Linux
: High major (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-05 20:12 UTC by Carsten Milkau
Modified: 2010-03-11 21:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
output of emerge --info (emerge_info,4.34 KB, text/plain)
2010-03-05 20:13 UTC, Carsten Milkau 		Details
output of emerge -etvp kmail (dependencies,60.85 KB, text/plain)
2010-03-05 20:23 UTC, Carsten Milkau 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Carsten Milkau 2010-03-05 20:12:41 UTC 
After upgrading from 4.3.3 to 4.3.5, I get popup messages that kmail cannot start pop3 (or pop3s, or imap) process when attempting to retrieve mail. Filing as gentoo bug because it looks like a missing/broken dependency to me (Yes I ran revdep-rebuild until it could not find anything broken anymore). 

Reproducible: Always

Steps to Reproduce:
(that's how to reproduce on my system. I have no testing system available for larger experiments.)
1. emerge ~kde-base/kmail-4.3.3
2. configure some accounts
3. emerge -u kde-base/kmail
4. run kmail & attempt to retrieve new mail.
Actual Results:  
Error popup message telling that the process pop3 (or pop3s, or imap) could not be started.
Comment 1 Carsten Milkau 2010-03-05 20:13:39 UTC 
Created attachment 222205 [details]
output of emerge --info
Comment 2 Carsten Milkau 2010-03-05 20:23:08 UTC 
Created attachment 222211 [details]
output of emerge -etvp kmail
Comment 3 Andreas K. Hüttel archtester gentoo-dev 2010-03-11 20:57:04 UTC 
This can happen when you update KDE while running KDE. Logging out and back in again should solve the issue.

Does it work now for you, or does the problem persist?
Comment 4 Carsten Milkau 2010-03-11 21:43:06 UTC 
Of cause a full KDE restart was the first thing I attempted. Nevertheless, after masking PyQt-4.7 and repeating the upgrade everything worked just fine.

Changing resolution to resolved/worksForMe