Bug 476163 - IMAP and SMTP passwords are not saved
Summary: IMAP and SMTP passwords are not saved
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-12-12 06:40 UTC by Matthias Scheutz
Modified: 2009-01-09 09:38 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-01-09 09:38:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matthias Scheutz 2008-12-12 06:40:55 UTC
Description of problem:

IMAP and SMTP passwords are not saved even though the save password checkbox is checked

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Matthew Barnes 2008-12-12 07:14:34 UTC
Evolution version?

Comment 2 Matthias Scheutz 2008-12-19 02:20:01 UTC
2.24.2

Comment 3 Milan Crha 2008-12-19 11:20:33 UTC
I guess Matt also thinks it could be related to fix for bug #474257 (see its duplicates and links to other bugs, all that was caused by a single issue). 

Please try to update to evolution-2.24.2-2.fc10 , which should be now available for stable updates, and report back. Thanks in advance.

Comment 4 Matthias Scheutz 2008-12-19 12:50:19 UTC
Done.  I have evolution-2.24.2-2.fc10.i386 installed and it still does not remember the passwords even though the checkboxes are checked

Comment 5 Milan Crha 2009-01-07 18:07:00 UTC
What is your authentication mechanism you've set within your IMAP account in Evolution? Can you also try to run Evolution on console and paste here the output of some short session (after evolution --force-shutdown), like run Evolution, enter password, let it finish download changes from a server and close evolution. I expect some information from keyring on the console, which may help hopefully.
Thanks in advance.

Comment 6 Milan Crha 2009-01-09 09:38:00 UTC
I got a private response from Matthias, stating:

---
Milan, thanks for the suggestion to look at the debugging output, it
turned out to be keyring problem (it said that it could not access the
keyring even though it was there...), so I removed the login.keyring,
logged off and on again, and now it's working.
---

Thus closing. Feel free to reopen if you face again.


Note You need to log in before you can comment on or make changes to this bug.