since a few days, I am not able to connect to my ews-account with the error in the topic. And also my calenders get these errors:
Error setting property ‘ConnectionStatus’ on interface org.gnome.evolution.dataserver.Source: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.155 was not provided by any .service files (g-dbus-error-quark, 2)
Failed to invoke credentials required on ‘Kalender’ (dd390a4520c6ee393fb4666813be47215af68b2f): The name :1.155 was not provided by any .service files
I am using Linux Mint 22.3 and evolution 3.56.2-4
What exactly is my problem and how can I solve it?
I alreade deinstalled evolution and installed it again. Nothing
changed.
I did not say to uninstall it, I said to restart it, together with the
background processes (or the whole machine). Evolution talks to an
evolution-data-server background processes, which are not touched at
all when you install/uninstall the evolution itself.
should I try it with a fresh config?
This is not about settings, it’s about D-Bus services, something what
runs in the background. It can be even other than evolution-related
processes/services, which is the reason why I asked you whether you
restarted the machine as such after this error came up - it makes sure
all the processes start again.
If the evolution --force-shutdown won’t help, then try the whole
machine restart, please.
Aha, good, that’s a clue. In that case something is crashing. Does the
Linux mint have anything like coredumpctl, some app, which can show
you when anything crashes?
Okay, that explains it, the evolution-source-registry process crashed,
when it was trying to login the the Microsoft server, using a Prt SSO
Cookie, which talks to com.microsoft.identity.broker1 D-Bus service,
which probably did not return enough information for libsoup to be able
to create the cookie. I guess when you run from a terminal:
/usr/libexec/evolution-source-registry
it’ll crash, but it’ll also print some runtime warnings on the
terminal, which will be good to see. From what I understood the D-Bus
service returns some values which the libsoup3 rejects when creating
the cookie.
Does your account need that com.microsoft.identity.broker1? It’s
something you installed separately, it’s not part of the evolution*.
The things should be fine if you uninstall it, but only if you do not
need it - I mean, as a workaround, sort of.
You said this started happening recently. Did you update the libsoup3
to a newer version? What is the current version you have, please? What
was the previous one, if updated, please? Try to downgrade it to the
previous version.
$ dpkg --list|grep libsoup
ii gir1.2-soup-2.4:amd64 2.74.3-6ubuntu1.6 amd64 GObject introspection data for the libsoup HTTP library
ii gir1.2-soup-3.0:amd64 3.4.4-5ubuntu0.7 amd64 GObject introspection data for the libsoup HTTP library
ii libphodav-3.0-0:amd64 3.0-8build3 amd64 WebDAV server implementation using libsoup
ii libphodav-3.0-common 3.0-8build3 all WebDAV server implementation using libsoup (common files)
ii libsoup-2.4-1:amd64 2.74.3-6ubuntu1.6 amd64 HTTP library implementation in C -- Shared library
ii libsoup-3.0-0:amd64 3.4.4-5ubuntu0.7 amd64 HTTP library implementation in C -- Shared library
ii libsoup-3.0-common 3.4.4-5ubuntu0.7 all HTTP library implementation in C -- Common files
ii libsoup-gnome-2.4-1:amd64 2.74.3-6ubuntu1.6 amd64 HTTP library implementation in C -- GNOME support library
ii libsoup2.4-common 2.74.3-6ubuntu1.6 all HTTP library implementation in C -- Common files
The broker service returned some JsonObject (few lines above is a check
for it), but it seems like it returned some broken data, or maybe not
properly parsed JSON data by the library. It would be great to see what
the returned response variable looks like, like at line 353, with
removed private data from it (I do not know what it returns).
Hi,
it would be good to know what they changed in their response that it
breaks the evolution-data-server code. Could they rename the properties
or anything? That’s kinda important to know, on one of the two sides
(it can be a regression on their side, or an innovation of the
protocol, which should be addressed on the evolution-data-server side).
I will ping the author of the change on the evolution-data-server side
too.
Bye,
Milan
