Thank you Øystein Gisnås! > severity 392061 important > thanks > > This is possibly something that should be fixed before releasing 2.8.x > with etch, but not a serious policy violation. The ideal solution > would be migration of passwords stored in file and fallback on file. > One possible temporary strategy might be to disable gnome-keyring > support altogether. What do you think about that? >
I fully agree that it is not a serious policy violation. (I looked at http://www.debian.org/Bugs/Developer#severities and misread that about serious in severity.) My apologies! Both your suggested solutions are fine with me! If Evolution is not supposed (always) to work with a keyring manager (like gnome-keyring (or kwallet for that (k/c)ase))) or it is not possible to start gnome-keyring in KDE unless a huge effort is made then storing it in a (plain text) file works as well for me. If I want I can always choose to encrypt my /home/<user>/ dir if I want encryption although the keyring solution would be the best if possible. Best regards Anders Lind -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]