Re: [Evolution] evolution 3.20.0 hiccups - Yahoo calender password requests - Send Account

[Milan Crha <mcrha redhat com>]

On Mon, 2016-04-11 at 12:28 +0200, Ralf Mardorf wrote:
> Preferences > Composer preferences > Send Account
> does not work

        Hi,
it does work for me, but I do not know your setup of the Send Account
Override.

> there are tons of hiccups

Hmm.

> but the most annoying is, that I can't get rid of Yahoo calender
> password requests for my Yahoo and Rocketmail POP accounts.

Only the Yahoo! and Google mail accounts can have associated also the
calendar (and eventually contacts) parts with them, when created in the
Evolution itself. I do not know how your Rocketmail POP account got to
think it has a calendar part with it too. I suppose you did configure
both accounts in the Evolution, not in GNOME (or eventually Ubuntu)
Online Accounts. If it's configured from the Online Accounts, then go
there and disable the Calendar part. Otherwise the only way to achieve
it is to configure the account again and do not enable the Calendar
part at the end of the New Mail Account wizard. That's from the UI. If
you want to play with the internal evolution-data-server files (at your
own risk), then stop the evolution-source-registry and then go to
~/.config/evolution/sources and find there the files which reference
the Yahoo! and/or Rocketmail server's calendars. These will have in
them a word "caldav", eventually also "[Calendar]" (quotes for clarity
only). Delete them or move them away. Then re-login, to have the
background processes started in the right order. You might see the
calendars in the Calendar view too.

I'd like to know more about the repeated password prompts for a CalDAV
calendar. There was a bug for it, which I wasn't able to reliably
reproduce. Running the evolution-calendar-factory from a terminal with
a CalDAV debugging on may give a hint what failed there. The command
would look like:
   $ CALDAV_DEBUG=all /usr/libexec/evolution-calendar-factory -w
then run the evolution and just wait for the password prompt and reply
to it with a correct password. If it's shown multiple times, then the
console with the evolution-calendar-factory will show some information
what failed. Beware, the output is a raw communication between the
server and the client, thus it can contain private information.

The thing with the Yahoo! server is that it returns broken headers, the
response contains '\0' character in the middle of the headers (twice),
which libsoup didn't like. It's fixed in current latest stable, if I
recall correctly, thus the Yahoo! calendar begins to work and thus
eventually asks for the password. before the fix in the libsoup it
failed with a "Message Corrupt" error. That might be the reason why you
didn't notice it earlier.

Partly related bug report is
https://bugzilla.gnome.org/show_bug.cgi?id=758878
but it was an issue mainly the first time when a new account was
created, not after that. This fix doesn't correct already created
accounts.

> I suspect this isn't one of the GTK bugs, but really an Evolution
> issue.

You are right, the password prompt is fully under the evolution control
since 3.18.0 or so. With respect of the gtk+ 3.20.0 issues and the
evolution, it can be that some things you face are already covered,
like:
https://bugzilla.gnome.org/show_bug.cgi?id=763796
https://bugzilla.gnome.org/show_bug.cgi?id=764542

If you have more, then it'll be good to know about them. Here is a list
of changes which were done in the today's 3.20.1 release of the
evolution:
https://download.gnome.org/sources/evolution/3.20/evolution-3.20.1.news

        Bye,
        Milan