Re: [Evolution] using evolution with google suite?

[Milan Crha <mcrha redhat com>]

On Thu, 2017-04-27 at 13:18 +0200, Kristian Rink wrote:
> (with a mail address that is not gmail.com but
> actually @<our-company-tld>), and I am trying to connect evolution to
> this. 

        Hi,
that's possible too and works fine here (I'm not on such a bleeding
edge as Arch Linux is with respect of evolution dependencies, but I'm
on the development version of evolution itself - nothing changed in
this regard between your and mine version). One catch-up with GMail
without gmail.com domain is to let autodetect settings using a fake
gmail.com address, then press Previous button and change the e-mail
addresses and user names as appropriate, while keeping server address
and such as they are. That's one option for lazy folks like me. You
seem to manage this fine.

> IMAP access is enabled in the Google Mail web application, however I
> fail to connect evolution to that. After configuring the account,

One thing, did you configure the account in Evolution or in GNOME
Online Accounts? I guess it was in Evolution, but just in case.

> I just see something like "an error has occured" in the web view for
> a fraction of a second and then the web part of that login screen
> turns white.

Regardless of the two methods, the widget is WebKitGTK+ web view and
from what you see I'd guess that WebKitWebProcess crashed for some
reason. Either you've something what can catch such crashes and it logs
somewhere what and where (backtrace) crashed, or we've a bad luck with
this. Anyway, WebKitGTK+, the same as evolution-ews, uses libsoup. It
turned out that libsoup 2.58.0 has some regression [1], thus try to
downgrade it to 2.56.0 first. Maybe it'll help, maybe not.

If it won't help, then I'd try to configure a Google account in GNOME
Online Accounts (gnome-control-center->Online Accounts), as I believe
you have the account configured directly in Evolution right now.

You can even try to downgrade WebKitGTK+ itself. I do not know what
package name it is on Arch Linux. The current upstream version is
2.16.1 (released ~3 weeks ago), where I'd try to step even further,
like to 2.14.6. Try this only as the last resort, it can break other
things due to (not only build) dependencies (I've a feeling the libsoup
downgrade will do the trick, though).

Otherwise not much idea, a backtrace of the crash would be needed to
know what actually happened, or at least to have a clue. You can run
evolution from a terminal, which can print something on console too.
        Bye,
        Milan

[1] https://bugzilla.gnome.org/show_bug.cgi?id=781590