Bug 235259

Summary: Evolution Continues to Ask for Password
Product: [openSUSE] openSUSE 10.2 Reporter: Simon Hildenbrand <simonedice>
Component: EvolutionAssignee: Harish Krishnaswamy <kharish>
Status: RESOLVED DUPLICATE QA Contact: A Nagappan <anagappan>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Simon Hildenbrand 2007-01-15 21:31:07 UTC 
I have a bug with Evolution.  I installed KDE with openSUSE 10.2.  After installed, I also installed Evolution.  The installation went fine and it runs ok.  I am using Evolution to connect to a Microsoft Exchange server.  That is fine.  The problem is that it cotinually asks for my password.  I check the box to save the password, but it doesn't.  It always asks me to continue to enter my password every time that I go from the messages, to calendar, contacts, or open a new message to send and type in contacts. 

I think the problem is that there was a setting that is telling it to use a program like KDEWallet in Gnome.  I'm not sure what that program is called, but I think that is the problem. So, the problem to fix might be to require that as a dependency when installing Evolution on KDE, or by allowing Evolution to store passwords in Evolution. 

However, because battery life is so much better on KDE, I think that Evolution should be able to be installed and working on KDE.

I would be glad to provide any other assistance or help in resolving this if needed.  Please let me know.
Comment 1 Harish Krishnaswamy 2007-01-16 03:29:46 UTC 
Simon : Thanks for the reporting the bug and the offer to help. The program that you have referred to in your description is the gnome-keyring application. 
Bug #232337 and Bug #231050 are also related to the same issue. Marking this is a duplicate of Bug #231050. Please watch the bug for further updates.


*** This bug has been marked as a duplicate of bug 231050 ***