On ven, 2008-12-19 at 10:49 +0100, Emanoil Kotsev wrote: > Yves-Alexis Perez wrote: > > By the way, you can export your mail from evolution, to import them in > > another evolution. There's a backup plugin for that, which will then > > appear in the File menu. > > Yes, Iknow this and I was thinking to give it a try, but I'm really willing > to > track the problem down and to solve it. I already have a backup from what was > working.
Ok. > > >> > >> The information you gave here brought me to the idea to try one very > >> simple thing. I removed everything evolution and gnome-keyring realted > >> and reinstalled. > >> This didn't help, so I created a new account, logged in and configured > >> evolution with my exchange account data. It worked! It said it can not > >> communicate with gnome-keyring. the keyring was not running. I started it > >> I logged in into my mailbox after creating a passphrase. > > > > Nice. > >> > >> I changed to my own account. I removed the exchange configuration and ... > >> deleted .evolution/exchange and the .gnome2/keyrings/default.keyring > >> > >> I created a new configuration and logged into my mail account. > >> As I clicked the checkbox "remember password" it runs the gnome-keyring > >> prompt to enter or initially to create password key. > > > > Because gnome-keyring was running, yes. If you don't want gnome-keyring, > > remove it, you'll be sure it'll not get in the way (as in the “new > > account” case). > > I think I made it clear that it is not working without the gnome-keyring > I just made the test: removed gnome-keyring (apt-get purge) and made sure there was no gnome-keyring running. Then ran evolution, it asked me the account password, and wether I wanted to save it or not. I entered it, and checked yes. The quit evo, and re-run it, and everything was ok, it didn't ask me for the password. But I had to make sure gnome-keyring wasn't running and wasn't installed. At a moment gnome-keyring was purged, but still running in the session and there was problems. > >> > >> This makes me think that your statement that it saves the password to > >> gconf is not valid at least for, which means that may be I have a problem > >> with gconf. > > > > Well, I'm not really sure it saves it in gconf, but I'm sure it saves it > > somewhere I'm not interested in when gnome-keyring isn't available. > > Unfortunately exactly this is not happening, that makes me think the other > system is not available. > It's happening here. > > > > >> This would be also a very good explanation why I was not prompted for > >> keyring password in Suse or kubuntu, though honestly this is my > >> hypothesis. > > > > “this” being? > > The hypothesis is that it tries to store the PW in gconf but fails and then > tries to store in gnome-keyring. I see evidence only for the second part. > If I remove the gnome-keyring, then no password storage method is available > and evolution behaves funny. > As I already said above, it perfectly works here. I'm on lenny, btw. > > >> > > When I try to reconfigure (upgrade etc) gconf related apps I always see some > errors regarding scrollkeeper-omf files. I don't know if it's related > I don't think so. > > > > > Oh, and last things: > > > > PLEASE LET THE BUG ON CC: > > DONT ANSWER TO THE LIST. > > IS THAT CLEAR? > > Well, this is because I post over gmane and my yahoo account. I hope it's > fine > now. Yep, thanks! > I couldn't understand what exactly means "contact me if you have a ...." > in some of the previous mails Hmhm, what is this? -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
