[weewx-user] Re: wxt5x0 v0.7 driver issue
Thanks, just wanted to know if anyone else had issues so I could decide whether to spend some time looking at it now. Since you had no issues, I spent 20 minutes and checked everything and then re-installed the drive one more time after downloading and inspecting the driver code. This time I got a prompt (y/n) during install that I'm 99% sure I didn't see before, not sure why. But after re-installing one more time it is working. I hate those 'suddenly works, not sure why' issues, but don't have time to spend a day re-creating the exact instance (from weekly backup) to figure it out. Thanks. On Tuesday, February 27, 2024 at 4:55:53 p.m. UTC-5 vince wrote: > Stephen - FWIW on v5 in a test I had no problems adding this driver or > seeing it available. Did the commands in the github page and then "weectl > extension list" saw the driver/extension had been installed ok. Tried the > reconfigure and it also appeared in the list (albeit in lower case near the > bottom of the list). > > On Tuesday, February 27, 2024 at 10:34:58 AM UTC-8 vince wrote: > >> No logs. No transcript of what you did. No info on your weewx version. >> No info on whether you have a 'pip' or dpkg or setup installation. >> >> We can't read minds. Need more info to even try to help. >> >> On Tuesday, February 27, 2024 at 9:53:23 AM UTC-8 Stephen Holden wrote: >> >>> I just updated my WXT5x0 driver to the latest version as per the README >>> on Matthew's github page, but now the wxt5x0 driver is not listed as an >>> option when I re-configure. >>> >>> Tried installing it again, but no luck. And the weewx.conf is unchanged >>> so points to the (older) wxt5x0 driver, which it can't find. >>> >>> Anyone else have issues updating the driver? >>> >>> Thanks in advance! >>> S. >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9dcb7ca6-9d41-4f51-8d40-4b769c0b3f67n%40googlegroups.com.
[weewx-user] wxt5x0 v0.7 driver issue
I just updated my WXT5x0 driver to the latest version as per the README on Matthew's github page, but now the wxt5x0 driver is not listed as an option when I re-configure. Tried installing it again, but no luck. And the weewx.conf is unchanged so points to the (older) wxt5x0 driver, which it can't find. Anyone else have issues updating the driver? Thanks in advance! S. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/46250096-9656-465d-8c3d-cf7007c6ee4an%40googlegroups.com.
[weewx-user] WXT520 message format
Hi All. Just started playing with weewx and trying to use aWXT520. The edssage are received, but not parsed. Running the wxt5x0.py code creates the data string in binary format, not ASCII, which I think is an issue. Also, parsing looks for only 1 '=' character and the binary string has 3 values with an = , so parsing fails. Is the msg config dfor WXT520 documented anywhere? Don't see it on the driver github page. Assume I'm missing something simple or the string format setup on WXT is incorrect Anyone with a working wxt5x0 that can provide any guidance? Thx. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/58520fe0-4fac-4146-b8ca-1e233e7cc516n%40googlegroups.com.
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 DistroRele
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 DistroRele
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 gnutls2
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 gnutls2
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
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
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
It suddenly started a few weeks ago in bionic. Official gnutls-bin 3.15.18-1ubuntu1.3. No changes to my system, where it was working for over a year, just suddenly started getting this error. Does affect Evolution on 18.04. Also affects it on CentOS 7, which I have on another machine. -- 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
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
It suddenly started a few weeks ago in bionic. Official gnutls-bin 3.15.18-1ubuntu1.3. No changes to my system, where it was working for over a year, just suddenly started getting this error. Does affect Evolution on 18.04. Also affects it on CentOS 7, which I have on another machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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."
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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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."
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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Started here yesterday accessing Rogers/Yahoo email using imap. Worked fine for the last year until yesterday...Gmail is still working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
Started here yesterday accessing Rogers/Yahoo email using imap. Worked fine for the last year until yesterday...Gmail is still working. -- 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
Excluding URL's help??
I get these errors constantly on PalmAddicts web-site, and I've tried the following URL Exclusion to try to skip the offending spots, to no avail. Any suggestions?? Errors: [1:29:48 PM] WARNING: Timed out: http://xs3.xs.to/pics/04476/DailyGadget.gif [1:29:49 PM] WARNING: Timed out: http://xs3.xs.to/pics/04476/proporta.bmp [1:30:11 PM] WARNING: Timed out: http://xs3.xs.to/pics/04474/pavacmain.jpg [1:30:11 PM] WARNING: Timed out: http://xs3.xs.to/pics/04475/tn_pic117.jpg [1:30:34 PM] WARNING: Timed out: http://xs.to/pics/04104/paforum.jpg [1:30:34 PM] WARNING: Timed out: http://xs2.xs.to/pics/04116/donate2.jpg [1:30:57 PM] WARNING: Timed out: http://xs.to/pics/04103/proporta_banner-1.gif [1:30:58 PM] WARNING: Timed out: http://pics.xs.to/pics/04092/weekly.jpg [1:31:21 PM] WARNING: Timed out: http://pics.xs.to/pics/04090/ps.GIF [1:31:22 PM] WARNING: Timed out: http://xs.to/pics/04103/phonemagic_ad_anim.gif [1:31:43 PM] WARNING: Timed out: http://xs.to/pics/04106/TripBossfinal190x90.gif [1:31:43 PM] WARNING: Timed out: http://xs.to/pics/04103/mm-banner-190x90.jpg [1:32:07 PM] WARNING: Timed out: http://pics.xs.to/pics/04094/pf.jpg [1:32:08 PM] WARNING: Timed out: http://pics.xs.to/pics/04085/eltintero-1.jpg Excludes: http://xs\.to/pics/ http://pics\.xs\.to/pics/* -- -- == Stephen Holden[EMAIL PROTECTED] ICQ: 10664404 == ___ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
[ERPS] Re: Hybrid Rocket Motor Concept
Stephen Holden Wrote: I am developing a new hybrid propellant concept that I would like to discuss...It's basically very similar to any hybrid, except that the propellant consists of a cylindrical grain of lightly bonded magnesium powder onto which is sprayed through injectors the oxidizer. What proportion of the reaction products are gaseous at the expected operating temperature? Russell McMahon Hey Ressell, I have recieved many many emails about the hybrid concept and slowly answering them, please be patient, especially those who have not had a response, I will respond to all emails:-) From my calculations (see Australian Experimental web site for update as I have added a brief thermochemical analysis) the proportion of gasses within the chamber is 67.8%. This means a faily high amount of solid phase primarily assumed to be MgO. The first propellant formulation considered, is ammonium nitrate, water and Mg. From the analysis we find: Optimum Isp(s)= 243s O/F = 1.9 Ratio of AN / water = 3 Tc = 3105 K Pc = 1000psi For a reasonble sized motor, it may be possible to achieve 200s of delivered Isp. It is most optimum to use a high as possible O / F ratio and to increase the amount of ammonium nitrate oxidizer and reduce the water content by increasing the concentration. Also, the lower the O/F and hence the amount of Mg fuel, the lower the losses due to residence time of the metals combustion within the chamber will be. However, the solubility limits this. A more oxidizing environment is desirable to, because it enhances the combustion efficiency of metals. Adding a proportion of AP would be desirable. We will also consider sodium nitrate perchlorate. Cheers, Stephen - Stephen J. Holden Owner/Founder Mechanical Engineer Australian Experimental Email: [EMAIL PROTECTED] Web Page: http://www.australianexperimental.com.au ___ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
[ERPS] Re: Hybrid Propellant Concept
Aloha, If you are using that solution for oxidizer, what is the viscosity? Will you need a large opening in your injector? If so, what will you do to make sure you have even distribution instead of chunky flow? What pressure will be needed for good atomization? Helium blowdown, or a pump? Things to consider. Larry -G'day Larry, I have had many emails from people about this idea, which is great. Looks like a guy has been experimenting with a similar concept for over 20years;-) This is good and may have to drop the phrase new (although it's still quite new because it's not being used in a significant way) and enlist his help:-) One problem that is apparent is to achieve even combustion. This was evident with tests of the reaction of Mg and oxidizer solutions. If you spray a fine jet of oxidizer onto the burning Mg grain, you get a localized increase in burning rate. The reaction is so violent that this does not seem to be a great issue as long as the grain surface is not cooled too much that it results in extinguishment. Of cause, we need even combustion and so, even pray of the oxidizer over the entire grain is better and should result in more stable combustion. How to achieve this even distribution is unknown at this stage. Ideas from impinging many jets of oxidizer at the bulkhead end of the motor to achieve reasonable atomization would help. Other ideas include having a SS tube that is positioned within the central cavity of the fuel grain and using many-many tiny holes to produce very fine stray. The limitations of this approach may be in the scaling to larger grains:-( Initially, will need to use the viscosity of water to start the design off for the injectors as, no data is available to me for water/oxidizer solutions (although I'm sure it exists somewhere). I opt to test it out and measure the flow rate. It's a good question, what pressure will be needed for good atomization? Any help to determining this is great. We may have to just test the atomization out. Although the dissolved oxidizers increase the density of the solution significantly, which means the jets of oxidizer have lots of flow energy and so if the jets impinge, they should shatter and atomize. But my knowledge is limited here. I have experience atomizing molten AN but none with injectors in rocket motors. To feed the oxidizer, we will off cause use blowdown. Most likely using Nitrogen contained within the ullage of the tank. However we should for the initial static tests control the tank pressure with a regulator. Any suggestions most welcome:-) Cheers, Steve - Stephen J. Holden Owner/Founder Mechanical Engineer Australian Experimental Email: [EMAIL PROTECTED] Web Page: http://www.australianexperimental.com.au ___ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
[ERPS] Hybrid Propellant Concept
Hello, I am developing a new hybrid propellant concept that I would like to discuss...It's basically very similar to any hybrid, except that the propellant consists of a cylindrical grain of lightly bonded magnesium powder onto which is sprayed through injectors the oxidizer. The oxidizer is a solution of water and various nitrates and perchlorates at high concentrations. There are many possibilities for testing and would like to get people together to explore the concept. I have placed a brief description on the Australian Experimental web site, which I will update with any developments made. The motor is a concept at this stage, but tests of the reactivity of lightly bonded magnesium powder and water / oxidizer solutions indicate a highly energetic reaction that with a little luck will produce a workable hybrid propellant. Any and all ideas and help is welcome...I think it's an interesting idea worth some investigation... Anyways, cheers from Australia, Stephen - Stephen J. Holden Owner/Founder Mechanical Engineer Australian Experimental Email: [EMAIL PROTECTED] Web Page: http://www.australianexperimental.com.au ___ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
[ERPS] Strand Burner Operator's Manual is now Available for Sale
To the Experimentalists, The Strand Burner Operator's Manual is now available for sale separately to the Strand Burners...It is 70 pages in length and covers the methods and operation of the strand burners in detail. Even for those who do not own a Strand Burner, it is valuable information and highly original. A 13 page sample of the manual/book can be downloaded from the website. I request the help of experimenters to inform other lists of this development. The website has been given a new look and projects are developing well... Please Visit: http://www.australianexperimental.com.au Best Regards, Steve - Stephen J. Holden Owner/Founder Mechanical Engineer Australian Experimental Email: [EMAIL PROTECTED] Web Page: http://www.australianexperimental.com.au - Stephen J. Holden Owner/Founder Mechanical Engineer Australian Experimental Email: [EMAIL PROTECTED] Web Page: http://www.australianexperimental.com.au ___ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
Sending Plcuker docs to multiple PDA's ??
Is there a way to specify two users to receive the output from Jpluck?? I can select a user from the drop-down, but I need to send the output to two different users. Used to be able to in Plucker desktop, but other than sending stuff to a folder and copying it in a background script..any easy way? -- -- = Stephen D. Holden Environment Canada (NWCN) Senior Design Engineer,Aviation Network Division Downsview, Ontario (416)739-4103 [EMAIL PROTECTED] = ___ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
[ERPS] Australian Experimental is back!
Dear ERPS List Members I sent this message to arocket and just to ensure that those who need to receive this information get it I'm sending to ERPS also. Gradually getting people signed up to the new list (see bellow), thanks again. The Australian Experimental site has been down due to our ISP shutting their doors. However, we are back and the new domain http://www.australianexperimental.com.au Our domain is now a .com.au rather than just .comPlease adjust links to your sites and help get us back up and running... If anyone would like link placed to their site, business or company then please email to: [EMAIL PROTECTED] and changes will be made. We have made some modifications to the web pages and worth a look. The 54page strand burner manual may be offered for sale for $55, thus send us an expression of interest so we know your interest. It allows you to make a more informed decision before purchasing the strand burner and contains lots of useful information about how to perform propellant characterization by strand burning and how to analyze data correctly. Any businesses interested in distributing the strand burner manual please contact also I have created a discussion list called AussieEx which is new list dedicated specifically to hybrid / solid / liquid propellant and motor research and development by the list members. Information about AE will be discussed here with special offers made and know where else...Come and join as it is the only list dedicated to this specialized field in Australia and possible in most of the world. The possibility for the members to help in testing and research of the products is very real and will be encouraged. It is not intended for general rocketry. Thanks to those who have helped with surveys and aspects of the strand burners! Those who have purchase products should join up so you can share results and problems with others. Best Regards, - Stephen J. Holden Owner/Founder Mechanical Engineer Australian Experimental Email: [EMAIL PROTECTED] Web Page: http://www.australianexperimental.com.au ___ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list