Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
I can confirm it working (yahoo). Thanks for the efforts! After running apt upgrade and seeing amongst others, things were fine: Get:10 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgnutlsxx28 amd64 3.5.18-1ubuntu1.4 [13,7 kB] Get:11 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgnutls28-dev amd64 3.5.18-1ubuntu1.4 [660 kB] Get:12 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgnutls-dane0 amd64 3.5.18-1ubuntu1.4 [21,0 kB] Get:13 http://de.archive.ubuntu.com/ubuntu bionic-updates/main i386 libgnutls30 i386 3.5.18-1ubuntu1.4 [660 kB] Get:14 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgnutls30 amd64 3.5.18-1ubuntu1.4 [645 kB] On Thu, 2020-07-02 at 14:56 +, Launchpad Bug Tracker wrote: > This bug was fixed in the package gnutls28 - 3.4.10-4ubuntu1.8 > > --- > gnutls28 (3.4.10-4ubuntu1.8) xenial; urgency=medium > > * d/p/50_Update-session_ticket.c-to-add-support-for-zero-leng.patch: > - add support for zero length session tickets returned from the server, > thanks Rod for the backport and testing! (lp: #1876286) > > -- Sebastien Bacher Wed, 17 Jun 2020 23:06:13 > +0200 > > ** Changed in: gnutls28 (Ubuntu Xenial) >Status: Fix Committed => Fix Released > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Thanks. I thought just replacing gnutls-bin would be enough. Now that I've updated all three .deb files, Evolution is once again pulling emails, etc from my ISP's rogers-yahoo server! Thanks to all who worked on fixing the problem. I know a few people on this mailing list will be very happy, myself included. Regards,Stephen Stephen Holden Ontario, Canada On Monday, June 22, 2020, 3:11:05 p.m. EDT, Rod Rivers <1876...@bugs.launchpad.net> wrote: @@stephenholden both of these have to be updated. This is where the code change was made: ii libgnutls30:amd64 3.5.18-1ubuntu1.3 amd64 GNU TLS library - main runtime library ii libgnutls30:i386 3.5.18-1ubuntu1.3 i386 GNU TLS library - main runtime library -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Status in Gnutls: Unknown Status in claws-mail package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in gnutls28 source package in Xenial: Fix Committed Status in gnutls28 source package in Bionic: Fix Committed Status in claws-mail source package in Focal: Invalid Status in evolution source package in Focal: Invalid Status in gnutls28 source package in Focal: Fix Committed Status in claws-mail source package in Groovy: Invalid Status in evolution source package in Groovy: Invalid Status in gnutls28 source package in Groovy: Fix Released Status in gnutls28 package in CentOS: Unknown Bug description: [Impact] Evolution and Claws email clients stopped connecting to Yahoo, AOL, Verizon, AT, Bell South, etc email servers which are run by the same group. Users are unable to get to their email. The underlying problem is that GnuTLS does not support zero length session tickets. The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). Nominating for SRU, fulfills: "Updates that need to be applied to Ubuntu packages to adjust to changes in the environment, server protocols, web services, and similar, i. e. where the current version just ceases to work." [testcase] GnuTLS 3.6: $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 [...] - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. the error should be fixed with the update GnuTLS 3.5: $ gnutls-cli pop.verizon.net:995 GnuTLS 3.4: $ gnutls-cli -p 995 pop.verizon.net [regression potential] The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). This creates two separate execution paths: 1) If the session ticket length > 0, which is the primary use case, the original code block will be executed. 2) If the session ticket len is 0, then the original code block will be skipped. Testing will need to include connections to servers that return session ticket length > 0 as well as ones that return session ticket length of 0. Wireshark can be used to look at the NewSessionTicket handshake message to confirm the session ticket length. [Other Info] The GnuTLS project's merge request 1260 fixes this bug. It was reviewed and approved by Daiki Ueno: https://gitlab.com/gnutls/gnutls/-/merge_requests/1260 According to the GnuTLS project: "We utilize two continuous integration systems, the gitlab-ci and travis. Gitlab-CI is used to test most of the Linux systems (see .gitlab-ci.yml), and is split in two phases, build image creation and compilation/test. The build image creation is done at the gnutls/build-images subproject and uploads the image at the gitlab.com container registry. The compilation/test phase is on every commit to gnutls project." Here are the results of the gitlab-ci pipeline showing all 19 tests passed for merge request 1260: https://gitlab.com/rrivers2/gnutls/-/pipelines/149155018 Page 8, section 3.3 of RFC5077 describes the NewSessionTicket handshake message and indicates that a zero length session ticket is a legitimate value: https://tools.ietf.org/pdf/rfc5077.pdf -- When GnuTLS connects to servers that return zero length session tickets using older TLS versions it returns the error code GNUTLS_E_MEMORY_ERROR and the connection is closed. This prevents Evolution and Claws email clients from connecting to Yahoo, AOL, Verizon, AT, Bell South, etc email servers. Evolution displays the message "Error performing TLS handshake: Internal error in memory allocation" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnutls30 3.5.18-1ubuntu1.3
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Sure thing. Pasted below and attached .txt with same content as well... Regards,Stephen Rogers Email Account: address: stephenhol...@rogers.com imap server: imap.broadband.rogers.com:993 username: stephenhol...@rogers.com password: smtp: similar as above, replace "imap." with "smtp.", port 465, same user/pass $gnutls-cli pop.verizon.net:995 Processed 127 CA certificate(s). Resolving 'pop.verizon.net:995'... Connecting to '66.218.85.35:995'... - Certificate type: X.509 - Got a certificate list of 3 certificates. - Certificate[0] info: - subject `CN=pop.verizon.net,O=Verizon Data Services LLC,L=Temple Terrace,ST=Florida,C=US', issuer `CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US', serial 0x0128e5987aac5428187b44269bcc4722, RSA key 2048 bits, signed using RSA-SHA256, activated `2020-01-17 00:00:00 UTC', expires `2021-12-07 12:00:00 UTC', pin-sha256="aNhhzcfwYqhSipKi6Wxk4Gs9+tKNo8L76OEHVxi9wxw=" Public Key ID: sha1:4ebacc7c149d8ba94aaf0ce3909b6d695e19a625 sha256:68d861cdc7f062a8528a92a2e96c64e06b3dfad28da3c2fbe8e1075718bdc31c Public Key PIN: pin-sha256:aNhhzcfwYqhSipKi6Wxk4Gs9+tKNo8L76OEHVxi9wxw= Public key's random art: +--[ RSA 2048]+ | | | | | . . | | . o | | E + S+ . | | . = o ++ . | |o +.+ .o. | | *+* =... | |o++ +o*. | +-+ - Certificate[1] info: - subject `CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US', issuer `CN=Baltimore CyberTrust Root,OU=CyberTrust,O=Baltimore,C=IE', serial 0x0182f8098ea2e626b91a3b27841fb9af, RSA key 2048 bits, signed using RSA-SHA256, activated `2015-12-08 12:05:07 UTC', expires `2025-05-10 12:00:00 UTC', pin-sha256="56higu/MFWb/c2b0avLE5oN2ECS2C43RvzSUgx/2xIE=" - Certificate[2] info: - subject `CN=Baltimore CyberTrust Root,OU=CyberTrust,O=Baltimore,C=IE', issuer `CN=Baltimore CyberTrust Root,OU=CyberTrust,O=Baltimore,C=IE', serial 0x02b9, RSA key 2048 bits, signed using RSA-SHA1 (broken!), activated `2000-05-12 18:46:00 UTC', expires `2025-05-12 23:59:00 UTC', pin-sha256="Y9mvm0exBk1JoQ57f9Vm28jKo5lFm/woKcVxrYxu80o=" - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. *** handshake has failed: Internal error in memory allocation. $dpkg -l | grep gnutls ii gnutls-bin 3.5.18-1ubuntu1.4 amd64 GNU TLS library - commandline utilities ii libcurl3-gnutls:amd64 7.58.0-2ubuntu3.8 amd64 easy-to-use client-side URL transfer library (GnuTLS flavour) ii libcurl4-gnutls-dev:amd64 7.58.0-2ubuntu3.8 amd64 development files and documentation for libcurl (GnuTLS flavour) ii libgnutls-dane0:amd64 3.5.18-1ubuntu1.3 amd64 GNU TLS library - DANE security support ii libgnutls-openssl27:amd64 3.5.18-1ubuntu1.3 amd64 GNU TLS library - OpenSSL wrapper ii libgnutls30:amd64 3.5.18-1ubuntu1.3 amd64 GNU TLS library - main runtime library ii libgnutls30:i386 3.5.18-1ubuntu1.3 i386 GNU TLS library - main runtime library ii libneon27-gnutls:amd64 0.30.2-3~ubuntu18.04.1 amd64 HTTP and WebDAV client library (GnuTLS enabled)$ Stephen Holden Ontario, Canada On Monday, June 22, 2020, 2:35:53 p.m. EDT, Rod Rivers <1876...@bugs.launchpad.net> wrote: @stephenholden could you provide: 1) details on your connection type (pop/imap), server and port (in my case this was pop to pop.verizon.net on port 995). 2) output of "dpkg -l | grep gnutls" 3) test my server using "gnutls-cli pop.verizon.net:995" (you may need to install the gnutls-bin package) and let me know if you see the error or a message that ends with "+OK Hello from jpop-0.1" I just tried with the proposed repo and was able to connect, details in another comment. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Status in Gnutls: Unknown Status in claws-mail package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in gnutls28 source package in Xenial: Fix Committed
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
I have installed on bionic and still have TLS memory error when trying to connect to my Rogers-Yahoo account. No change. Confirmed that new package is installed...Tried creating new Rogers-Yahoo account and it fails as well. Dang. Pls let me know what I can do to help diagnose further! Appreciate the work to date. Stephen Holden Ontario, Canada On Monday, June 22, 2020, 11:20:55 a.m. EDT, Łukasz Zemczak <1876...@bugs.launchpad.net> wrote: Hello Rod, or anyone else affected, Accepted gnutls28 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnutls28/3.5.18-1ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnutls28 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic ** Changed in: gnutls28 (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Status in Gnutls: Unknown Status in claws-mail package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in gnutls28 source package in Xenial: Fix Committed Status in gnutls28 source package in Bionic: Fix Committed Status in claws-mail source package in Focal: Invalid Status in evolution source package in Focal: Invalid Status in gnutls28 source package in Focal: Fix Committed Status in claws-mail source package in Groovy: Invalid Status in evolution source package in Groovy: Invalid Status in gnutls28 source package in Groovy: Fix Released Status in gnutls28 package in CentOS: Unknown Bug description: [Impact] Evolution and Claws email clients stopped connecting to Yahoo, AOL, Verizon, AT, Bell South, etc email servers which are run by the same group. Users are unable to get to their email. The underlying problem is that GnuTLS does not support zero length session tickets. The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). Nominating for SRU, fulfills: "Updates that need to be applied to Ubuntu packages to adjust to changes in the environment, server protocols, web services, and similar, i. e. where the current version just ceases to work." [testcase] GnuTLS 3.6: $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 [...] - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. the error should be fixed with the update GnuTLS 3.5: $ gnutls-cli pop.verizon.net:995 GnuTLS 3.4: $ gnutls-cli -p 995 pop.verizon.net [regression potential] The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). This creates two separate execution paths: 1) If the session ticket length > 0, which is the primary use case, the original code block will be executed. 2) If the session ticket len is 0, then the original code block will be skipped. Testing will need to include connections to servers that return session ticket length > 0 as well as ones that return session ticket length of 0. Wireshark can be used to look at the NewSessionTicket handshake message to confirm the session ticket length. [Other Info] The GnuTLS project's merge request 1260 fixes this bug. It was reviewed and approved by Daiki Ueno: https://gitlab.com/gnutls/gnutls/-/merge_requests/1260 According to the GnuTLS project: "We utilize two continuous integration systems, the gitlab-ci and travis. Gitlab-CI is used to test most of the Linux systems (see .gitlab-ci.yml), and is split in two phases, build image creation and compilation/test. The build image creation is done at the
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Can I install this version on 18.04 without causing other issues? First time had to go outside simply adding a PPA and installing... Stephen Holden Ontario, Canada On Friday, June 12, 2020, 11:25:46 a.m. EDT, Sebastien Bacher <1876...@bugs.launchpad.net> wrote: It's unclear to me, if that issue new and what created it? If it has been existing in Xenial and Bionic and not reported in years, is it really important enough to justify a stable update? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Status in Gnutls: Unknown Status in claws-mail package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in claws-mail source package in Focal: Invalid Status in evolution source package in Focal: Invalid Status in gnutls28 source package in Focal: Triaged Status in claws-mail source package in Groovy: Invalid Status in evolution source package in Groovy: Invalid Status in gnutls28 source package in Groovy: Fix Released Status in gnutls28 package in CentOS: Unknown Bug description: [testcase] $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 [...] - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. When Evolution checks my verizon.net account it displays the message "Error performing TLS handshake: Internal error in memory allocation" and doesn't download any new email messages. This started happening two days ago shortly after updates were applied. Normally it would download the new email messages. Searching the web I found a Linux Mint forum with users having the same issue. Some users felt it maybe an expired certificate while others thought it might be related to the recent update. What can I do to get more information about this issue? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.5-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Will the update be back-ported to 18.04 and/or 18.10 of Ubuntu automatically as well? Not sure how the process works... Stephen Holden Ontario, Canada On Wednesday, June 10, 2020, 9:11:28 a.m. EDT, Sebastien Bacher <1876...@bugs.launchpad.net> wrote: The issue has been fixed in the current serie now https://launchpad.net/ubuntu/+source/gnutls28/3.6.13-4ubuntu1 ** Changed in: gnutls28 (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Status in Gnutls: Unknown Status in claws-mail package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in claws-mail source package in Focal: Invalid Status in evolution source package in Focal: Invalid Status in gnutls28 source package in Focal: Triaged Status in claws-mail source package in Groovy: Invalid Status in evolution source package in Groovy: Invalid Status in gnutls28 source package in Groovy: Fix Released Status in gnutls28 package in CentOS: Unknown Bug description: [testcase] $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 [...] - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. When Evolution checks my verizon.net account it displays the message "Error performing TLS handshake: Internal error in memory allocation" and doesn't download any new email messages. This started happening two days ago shortly after updates were applied. Normally it would download the new email messages. Searching the web I found a Linux Mint forum with users having the same issue. Some users felt it maybe an expired certificate while others thought it might be related to the recent update. What can I do to get more information about this issue? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.5-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Hear hear! Thanks all. On Jun. 7, 2020, 5:15 p.m., at 5:15 p.m., Rod Rivers <1876...@bugs.launchpad.net> wrote: >Big shout out to Daiki Ueno and Andreas Metzler of the GnuTLS project >and everyone on this thread for helping out! Testing with Debian >Bullseye and Ubuntu Groovy + proposed repo was successful. Both >included version 3.6.13-4 of GnuTLS. Hopefully it won't be much longer >before this fix is pushed out to a wider audience. > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1876286 > >Title: > Evolution reports "Error performing TLS handshake: Internal error in > memory allocation." > >Status in Gnutls: > Unknown >Status in claws-mail package in Ubuntu: > Invalid >Status in evolution package in Ubuntu: > Invalid >Status in gnutls28 package in Ubuntu: > Fix Committed >Status in claws-mail source package in Focal: > Invalid >Status in evolution source package in Focal: > Invalid >Status in gnutls28 source package in Focal: > Triaged >Status in claws-mail source package in Groovy: > Invalid >Status in evolution source package in Groovy: > Invalid >Status in gnutls28 source package in Groovy: > Fix Committed >Status in gnutls28 package in CentOS: > Unknown > >Bug description: > [testcase] > > $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 > [...] > - Status: The certificate is trusted. > *** Fatal error: Internal error in memory allocation. > > > When Evolution checks my verizon.net account it displays the message > "Error performing TLS handshake: Internal error in memory allocation" > and doesn't download any new email messages. This started happening > two days ago shortly after updates were applied. Normally it would > download the new email messages. Searching the web I found a Linux > Mint forum with users having the same issue. Some users felt it maybe > an expired certificate while others thought it might be related to the > recent update. What can I do to get more information about this > issue? > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: evolution 3.28.5-0ubuntu0.18.04.2 > ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 > Uname: Linux 5.3.0-51-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri May 1 07:03:51 2020 > InstallationDate: Installed on 2017-12-12 (870 days ago) >InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 >(20170801) > ProcEnviron: > PATH=(custom, no username) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: evolution > UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago) > >To manage notifications about this bug go to: >https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
It is obviously related to yahoo for all of us, but that does not mean Yahoo caused it. While it might be that Yahoo has done some changes, I have other mail clients (Thunderbird on Ubuntu, K9 on Android, Mailmate on Mac) that have not been updated and have had no problem with yahoo. We are very specifically looking at Evolution in relation to Yahoo. Two mere suspicions, and I have no way to check due to lack of knowledge, a) there was an update on Ubuntu that caused the issue. b) indeed, yahoo did some changes, but they were no problem before. Whatever library in the background handles this, worked fine so far, but could not cope with this hypothetical change. Then it must be that Thunderbird works differently. cheers, Martin On Fri, 2020-05-15 at 14:17 +, richard wrote: > This same problem started the first week of May with my IMAP+ AT "Error > performing TLS handshake: ..." > Ubuntu Mate 16 Evolution 3.18.5.2-0ubuntu3.2 > > Sending SMTP still works. > > Reading through the posts it's clear that it's a Yahoo issue since Yahoo > manages AT, AOL, Verizon and Yahoo mail and those are the only ones > affected. > > Why has no fix-update been created yet? > It's not like people are so swamped with work they don't have time to. > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
I used the built in backup on the file menu, "Backup Evolution Data ...". The following output appeared: evolution-backup-Message: 18:00:36.504: dconf dump /org/gnome/evolution-data-server/ >/home/user/.local/share/evolution/backup-restore-dconf-eds.ini evolution-backup-Message: 18:00:36.537: dconf dump /org/gnome/evolution/ >/home/user/.local/share/evolution/backup- restore-dconf-evo.ini evolution-backup-Message: 18:00:36.605: cd /home/user && tar chf - .local/share/evolution .config/evolution evolution.dir | gzip > '/home/user/evolution-backup-20200508.tar.gz' evolution-backup-Message: 18:12:05.909: rm /home/user/evolution.dir On Fri, 2020-05-08 at 23:10 +, Yi Li wrote: > @Rob > > Did you know where the evolution data is located? > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Uninstalling the apt version and then installing the Flatpak version didnt make any difference for me - very disappointed. I prefer Evolution to Thunderbird (sorry..mozilla) Though I wonder if there were remnant files left behind from the apt because my emails were still there when i installed the Flatpak. Would those left behind filed after the uninstall cause carry over problems to the flatpak installed version ? On Wed, May 6, 2020 at 9:05 PM Rod Rivers <1876...@bugs.launchpad.net> wrote: > Joe, > > If your not sure if there is any sensitive information in the trace > please do not send the files. I was able to get wireshark to decrypt > and decode the pcap and was certain that no username/password was > recorded in the files I posted. > > The next logical step would be to get the source code, compile it and see > if you can trace through it to find the line that is failing. I looked at > the build instructions but they look complicated: > https://wiki.gnome.org/Apps/Evolution/Building > > At this point I'm looking into either upgrading to Ubuntu 20.04 or > installing the flatpack version that was mentioned in the Linux Mint > forum. > > Rod > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1876286 > > Title: > Evolution reports "Error performing TLS handshake: Internal error in > memory allocation." > > Status in evolution package in Ubuntu: > Confirmed > > Bug description: > When Evolution checks my verizon.net account it displays the message > "Error performing TLS handshake: Internal error in memory allocation" > and doesn't download any new email messages. This started happening > two days ago shortly after updates were applied. Normally it would > download the new email messages. Searching the web I found a Linux > Mint forum with users having the same issue. Some users felt it maybe > an expired certificate while others thought it might be related to the > recent update. What can I do to get more information about this > issue? > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: evolution 3.28.5-0ubuntu0.18.04.2 > ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 > Uname: Linux 5.3.0-51-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri May 1 07:03:51 2020 > InstallationDate: Installed on 2017-12-12 (870 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > ProcEnviron: >PATH=(custom, no username) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: evolution > UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
I am new to Linux and not that computer savvy. I don’t understand how to decode encrypted packets. Also will this solve the problem? It would be better for someone like myself to just have an ungrade to Evolution that would contain the solution and have it work properly. Thanks for your consideration. -Original Message- From: Rod Rivers Sent: Tuesday, May 05, 2020 7:39 PM To: th.cl...@verizon.net Subject: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Joe, Thanks for the info! I made some progress on this today. Evidently Evolution uses GnuTLS to communicate with the pop server. If you run the following commands on a terminal you should get plenty of output that will allow you to decode the encrypted packets: export GNUTLS_DEBUG_LEVEL=99 evolution It looks like the handshake has just finished and the pop server is returning its first message: Post Office Protocol +OK Hello from jpop-0.1\r\n Response indicator: +OK Response description: Hello from jpop-0.1 I have attached the pcap, debug output and keys. Rod ** Attachment added: "EvolutionVerizonHandshakeFailure.zip" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+attachment/5367101/+files/EvolutionVerizonHandshakeFailure.zip -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Status in evolution package in Ubuntu: Confirmed Bug description: When Evolution checks my verizon.net account it displays the message "Error performing TLS handshake: Internal error in memory allocation" and doesn't download any new email messages. This started happening two days ago shortly after updates were applied. Normally it would download the new email messages. Searching the web I found a Linux Mint forum with users having the same issue. Some users felt it maybe an expired certificate while others thought it might be related to the recent update. What can I do to get more information about this issue? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.5-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
