Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36515 - [gnutls] update to 3.2.3-1 breaks TLS handling in evolution-ews

Attached to Project: Arch Linux
Opened by David Gabriel (b2c) - Tuesday, 13 August 2013, 07:11 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 03 January 2014, 13:58 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: ever since the update of gnutls from any version higher than gnutls-3.2.1-1 i can't sync mail with evolution-ews anymore.


Steps to reproduce:
* run 'pacman -Syu', which upgrades to the latest gnutls version
* try to sync mail in evolution(-ews)
* a TLS error gets logged:

(evolution:24387): evolution-mail-WARNING **: Failed to refresh folder 'Exchange: Inbox': No response: Error reading data from TLS socket: A TLS fatal alert has been received.

I already asked for the gnutls/webkit bug to be reopened, but to no avail.
related bugs (all closed, but same symptoms):
* https://bugs.archlinux.org/task/36212
* https://bugs.archlinux.org/task/36262
* https://bugs.archlinux.org/task/36207
* https://bugs.archlinux.org/task/36245
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Friday, 03 January 2014, 13:58 GMT
Reason for closing:  None
Comment by Andreas Radke (AndyRTR) - Tuesday, 13 August 2013, 15:23 GMT
This may be a different issue or a not yet fixed side effect. Please get in contact with upstream dev(Nikos) and find a solution.
Comment by David Gabriel (b2c) - Saturday, 31 August 2013, 18:46 GMT
I'm in contact with the dev now and will report if we find something.
Comment by David Gabriel (b2c) - Tuesday, 17 September 2013, 14:25 GMT
Guys, I'm a little bit at a loss here at the moment. Nikos worked with me to find a solution to the problem for the last 3 weeks, but although we could expose the bad commit, Nikos could not find anything bad with it or come up with a fix. I quote his latest response here:

----quote-----
Unfortunately I cannot find a reason for the failure you see. If the
attached patch doesn't fix the issue, the problem may be an interplay
of unrelated to gnutls issues that trigger the behavior you see. In
the latter case it may be better to report the problem to the programs
that are involved.

regards,
Nikos
----/quote-----

As stated, the latest patch didn't make evolution-ews work and I'm back to square one I guess. How should I proceed further or which components should be investigated next? I suspect that 'extra/glib-networking' could be involved, as some evolution debugging showed that 'libgiognutls.so' is used in the communiction with the exchange server.


for reference, this git commit in gnutls is the first one to trigger the evolution-ews error while syncing with Exchange:
gnutls git: 6fb9273afa06c6ec9822e4e71fad18db5b8fbf54
Comment by David Gabriel (b2c) - Monday, 07 October 2013, 18:16 GMT
Just an update: the error persists with gnutls-3.2.4 and gnome / evolution 3.10.
Comment by Andreas Radke (AndyRTR) - Sunday, 13 October 2013, 17:21 GMT
Maybe you will have better success if you bring evolution-ews devs together with Nikos. Just point them here and wherever you are talking to Nikos.

It's an upstream issue anyway on either gnutls or evolution side.
Comment by Andreas Radke (AndyRTR) - Monday, 23 December 2013, 19:57 GMT
Status?
Comment by David Gabriel (b2c) - Friday, 03 January 2014, 09:41 GMT
I have to admit that I never bothered to file yet another bug with the gnome folks and just masked any upgrades for gnutls instead, as I was busy with work and I couldn't find any other reports of this issue. I just now tested again with evolution(-ews)-3.10 and gnutls 3.2.8-1 and the problem now seems to be gone. I guess it was some strange issue somewhere between my company's exchange and my setup. Thank you for your time, please close the bug.

Loading...