[Evolution] Bug#413142: evolution-exchange: Evolution stopped working with exchange - probably depends on keyring problem

[Emanoil Kotsev]

Yves-Alexis Perez wrote:

> On mer, 2008-12-17 at 23:04 +0100, emanoil wrote:
>> 
>> I have noticed that it depends somehow on keyring, because it worked
>> yesterday only after I created a
>> keyring with password and this after cheking the option to remember
>> the password. How was evolution remembering
>> the password previously, why does it want to put it in the keyring,
>> If I ignore this option or remove the keyring it says translated in
>> english "no password pair for exchange
>> account owa http://<servername> ...
> 
> Well, if it depends on the keyring, maybe (I don't maintain it so I'm
> not really sure) it can only store the passwords and the settings, and
> maybe that was just transparent in suse and/or kubuntu. Please check
> that gnome-keyring *is* runnning when you are experiencing the problem.
> 
> Cheers,

Unfortunately part of (my long mail/bug) report yesterday was that I
mentioned that I'm using KDE. I don't want to have to do anything with
gnome if possible, to keep my work simple. I don't think the gnome-keyring
was running in Suse or in kubuntu. I just think there are 3 possibilites

1) dbus providing the keyring manager (thus pointing to kwallet)
I uninstalled the gnome-keyring now it's proven that evolution depends on
it, but not directly. It expects from dbus to provide: org.gnome.keyring.

** (evolution:19240): WARNING **: couldn't communicate with gnome keyring
daemon via dbus: The name org.gnome.keyring was not provided by
any .service files

Is it possible to provide this key pointing to kwallet. I think it is, but
I'm not that familiar with the dbus system and config. I'll investigate at
the weekend as now I'm preoccupied and it takes long to do my mails with
the webinterface.

2) libraries with Evo version 2.22 changed so that it depends on the keyring
now.

3) there is also some other option I can not think of

Anyway I'm going to try to run Suse or Kubuntu from backup and check if it's
really debian related, or may be the admins changed something on server
side which I would exclude from the options.

regards