Error writing data to TLS socket

[marqsman]

Hello everyone.
I’ve been having some problems with Evolution in my GNOME installation. Basically I cannot connect my GMail accounts via Evolution. I am greeted with the following error message in the GUI for failing to access a folder in my email account:

Failed to obtain an access token for “Folder1”: Failed to refresh access token (rest-proxy-error-quark, 4): Error writing data to TLS socket: The specified session has been invalidated for some reason.

and then another error regarding the connection of my email account:

The reported error was “Error reading data from TLS socket: The specified session has been invalidated for some reason.”.

I first got this error after a patch applied in my Leap 15.0 machine a couple weeks ago. At the openSUSE subreddit I learned this patch updated the gnutls libraries from version 3.6.2-lp150.6.1 to 3.6.7-lp150.9.1 which caused this behaviour. One workaround was to downgrade to the 3.6.2 version and locking the package, which restored the proper functionality of my mail client. Yesterday I upgraded my machine to Leap 15.1 which installed gnutls package version 3.6.7. The problem not surprisingly returned but this time I cannot find a previous package since I guess the older packages belonged to the previous oS version and are not available in Leap 15.1.

I am trying to solve this issue but I have some concerns/doubts. Could anyone give me some light on this?

1. I suppose I could search and install an RPM for the 3.6.2-lp150 package. I found this website with a library of distro packages, but I would be more confident to get it from the actual openSUSE repositories. Is it possible to get it there? Where do I find it?

2. Even if I install the older package, am I not overlooking a security issue? After all, when I applied the patch initially, it was labelled as a security patch.

3. What do you think it would be the proper thing to do here?

[nrickert]

I don’t really have any advice, and I don’t use Evolution. However, you could add the 15.0 repo as additional repo.

Checking, I see that the 15.0 update repo is the one with 3.6.2. I do not know whether you will run into conflicts when installing that. And there seem to be 4 related packages.

If you do that, then I suggest that you disable the added repo once you have installed those packages. And lock those packages so that they are not replaced on your next update of 15.1.

I think there’s an open bug report for this problem, and you might want to watch that.

[marqsman]

@nrickert

I don’t really have any advice, and I don’t use Evolution. However, you could add the 15.0 repo as additional repo.

Checking, I see that the 15.0 update repo is the one with 3.6.2. I do not know whether you will run into conflicts when installing that. And there seem to be 4 related packages.

If you do that, then I suggest that you disable the added repo once you have installed those packages. And lock those packages so that they are not replaced on your next update of 15.1.

I think there’s an open bug report for this problem, and you might want to watch that.

I have installed the older packages from Leap 15.0. This will have to do for now. Thank you for noticing the bug report. I’ll surely take a close look on that.
Thank you for the feedback