** Changed in: evolution
Importance: Unknown => Medium
--
Evolution not storing passwords
https://bugs.launchpad.net/bugs/292806
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu
the new version is available as an intrepid update and in jaunty
** Changed in: evolution (Ubuntu)
Status: Fix Committed => Fix Released
--
Evolution not storing passwords
https://bugs.launchpad.net/bugs/292806
You received this bug notification because you are a member of Ubuntu
Desktop
upstream rolled a new stable version today which has been uploaded as a
candidate update to intrepid now
--
Evolution not storing passwords
https://bugs.launchpad.net/bugs/292806
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desk
** Changed in: evolution
Status: Unknown => Fix Released
--
Evolution not storing passwords
https://bugs.launchpad.net/bugs/292806
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.
the bug has been fixed upstream now
** Changed in: evolution (Ubuntu)
Status: Triaged => Fix Committed
--
Evolution not storing passwords
https://bugs.launchpad.net/bugs/292806
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I am having a similar problem. Passwords are saved, but if the server
becomes unavailable, it prompts for the password of the user (as
before). However, unlike in earlier versions, it no longer has the
password in the popup box, and you have to re-enter it every time.
It is otherwise saving the pa
** Also affects: evolution via
http://bugzilla.gnome.org/show_bug.cgi?id=552583
Importance: Unknown
Status: Unknown
** Changed in: evolution (Ubuntu)
Status: New => Triaged
--
Evolution not storing passwords
https://bugs.launchpad.net/bugs/292806
You received this bug notific
I'm only using the default keyring unlocked with the login password.
The account in question is a pop3/smtp type with ssl encryption and
logintype "login". (gmx.at)
A second account from the same provider, which was already configured in
hardy, does work without problems.
As for gnome bug tracke
thank you for your bug report. do you have several gnome-keyring
available in seahorse? which one do you use? what is the account type
you are using there? could you open the bug on bugzilla.gnome.org where
the people writting the software will read it too?
** Changed in: evolution (Ubuntu)
Imp
