Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1057074: emacs: A package-refresh-contents or M-x mastodon 'hangs' my emacs
41 views
Skip to first unread message
Johan Laenen
Nov 29, 2023, 3:10:05 AM11/29/23
to
Package: emacs
Version: 1:29.1+1-5
Severity: important
X-Debbugs-Cc: johan.laene...@gmail.com
Dear Maintainer,
I'm on trixie/sid and I noticed last week that whenever I'd do a
package-refresh-contents or whenever I'd try to launch mastodon.el (M-x
mastodon) my emacs would hang. The command package-refresh-contents only
showed 'Contacting host: elpa.gnu.org:443' and didn't do much more. I had to
ctlr-g to break out or wait a couple of minutes before emacs would say that
the package refresh was done. The package mastodon.el is a different beast.
After a wait I'd get 'Wrong type argument: stringp, nil'.
Switching to ipv4 only made the problem disappear:
root@msi:/home/gargle# /sbin/sysctl -w net.ipv6.conf.all.disable_ipv6=1net.ipv6.conf.all.disable_ipv6 = 1
root@msi:/home/gargle# /sbin/sysctl -w net.ipv6.conf.default.disable_ipv6=1net.ipv6.conf.default.disable_ipv6 = 1
I moved these two lines above in my /etc/sysctl.conf and double checked my
/etc/network/interfaces. I had nothing extra about ipv6 in my configuration.
This is what I had and what I still have:
root@msi:/home/gargle/whoami# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto loiface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
I'm baffled because I never experienced this behaviour before. My company's
laptop runs wsl2 with debian on windows 10 and doesn't show this problem. My
setup at home used to work in september and october. On october the
22nd I posted a message on mastodon at floss.social from within emacs by means
of mastodon.el. I don't actually know the exact date on which I started to get
errors.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages emacs depends on:
ii emacs-gtk 1:29.1+1-5
emacs recommends no packages.
emacs suggests no packages.
-- no debconf information
Version: 1:29.1+1-5
Severity: important
X-Debbugs-Cc: johan.laene...@gmail.com
Dear Maintainer,
I'm on trixie/sid and I noticed last week that whenever I'd do a
package-refresh-contents or whenever I'd try to launch mastodon.el (M-x
mastodon) my emacs would hang. The command package-refresh-contents only
showed 'Contacting host: elpa.gnu.org:443' and didn't do much more. I had to
ctlr-g to break out or wait a couple of minutes before emacs would say that
the package refresh was done. The package mastodon.el is a different beast.
After a wait I'd get 'Wrong type argument: stringp, nil'.
Switching to ipv4 only made the problem disappear:
root@msi:/home/gargle# /sbin/sysctl -w net.ipv6.conf.all.disable_ipv6=1net.ipv6.conf.all.disable_ipv6 = 1
root@msi:/home/gargle# /sbin/sysctl -w net.ipv6.conf.default.disable_ipv6=1net.ipv6.conf.default.disable_ipv6 = 1
I moved these two lines above in my /etc/sysctl.conf and double checked my
/etc/network/interfaces. I had nothing extra about ipv6 in my configuration.
This is what I had and what I still have:
root@msi:/home/gargle/whoami# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto loiface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
I'm baffled because I never experienced this behaviour before. My company's
laptop runs wsl2 with debian on windows 10 and doesn't show this problem. My
setup at home used to work in september and october. On october the
22nd I posted a message on mastodon at floss.social from within emacs by means
of mastodon.el. I don't actually know the exact date on which I started to get
errors.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages emacs depends on:
ii emacs-gtk 1:29.1+1-5
emacs recommends no packages.
emacs suggests no packages.
-- no debconf information
Johan Laenen
Nov 29, 2023, 4:10:04 AM11/29/23
to
gargle@msi:~$ time gnutls-cli elpa.gnu.org
Processed 140 CA certificate(s).
Resolving 'elpa.gnu.org:443'...
Connecting to '2001:470:142::89:443'...
Connecting to '209.51.188.89:443'...
- Certificate type: X.509
- Got a certificate list of 3 certificates.
- Certificate[0] info:
- subject `CN=elpa.gnu.org', issuer `CN=R3,O=Let's Encrypt,C=US',
serial 0x039d688ee4d536c2c5d180acd0b77dd534de, RSA key 2048 bits,
signed using RSA-SHA256, activated `2023-11-21 11:08:15 UTC', expires
`2024-02-19 11:08:14 UTC',
pin-sha256="QcwJ9TVQmsXtBHYcKDWyfyNR3X5gWYDtlVNItux6Rhg="
Public Key ID:
sha1:445b8bb7b09ad78854d5391cde68b9897a5a052c
sha256:41cc09f535509ac5ed04761c2835b27f2351dd7e605980ed955348b6ec7a4618
Public Key PIN:
pin-sha256:QcwJ9TVQmsXtBHYcKDWyfyNR3X5gWYDtlVNItux6Rhg=
- Certificate[1] info:
- subject `CN=R3,O=Let's Encrypt,C=US', issuer `CN=ISRG Root
X1,O=Internet Security Research Group,C=US', serial
0x00912b084acf0c18a753f6d62e25a75f5a, RSA key 2048 bits, signed using
RSA-SHA256, activated `2020-09-04 00:00:00 UTC', expires `2025-09-15
16:00:00 UTC', pin-sha256="jQJTbIh0grw0/1TkHSumWb+Fs0Ggogr621gT3PvPKG0="
- Certificate[2] info:
- subject `CN=ISRG Root X1,O=Internet Security Research Group,C=US',
issuer `CN=DST Root CA X3,O=Digital Signature Trust Co.', serial
0x4001772137d4e942b8ee76aa3c640ab7, RSA key 4096 bits, signed using
RSA-SHA256, activated `2021-01-20 19:14:03 UTC', expires `2024-09-30
18:14:03 UTC', pin-sha256="C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M="
- Status: The certificate is trusted.
- Description: (TLS1.3-X.509)-(ECDHE-SECP256R1)-(RSA-PSS-RSAE-SHA256)-(AES-256-GCM)
- Session ID: 1B:FA:A7:4C:81:3D:6B:3E:9C:2D:65:EB:5D:52:44:4B:E8:2E:58:C9:4C:67:DE:69:AB:4F:F7:2C:10:5C:03:C6
- Options:
- Handshake was completed
- Simple Client Mode:
- Peer has closed the GnuTLS connection
real 2m34.806s
user 0m0.014s
sys 0m0.009s
on my wsl2 gnutls-cli doesn't go for ipv6. It immediately connects to
'209.51.188.89:443'...
Processed 140 CA certificate(s).
Resolving 'elpa.gnu.org:443'...
Connecting to '2001:470:142::89:443'...
Connecting to '209.51.188.89:443'...
- Certificate type: X.509
- Got a certificate list of 3 certificates.
- Certificate[0] info:
- subject `CN=elpa.gnu.org', issuer `CN=R3,O=Let's Encrypt,C=US',
serial 0x039d688ee4d536c2c5d180acd0b77dd534de, RSA key 2048 bits,
signed using RSA-SHA256, activated `2023-11-21 11:08:15 UTC', expires
`2024-02-19 11:08:14 UTC',
pin-sha256="QcwJ9TVQmsXtBHYcKDWyfyNR3X5gWYDtlVNItux6Rhg="
Public Key ID:
sha1:445b8bb7b09ad78854d5391cde68b9897a5a052c
sha256:41cc09f535509ac5ed04761c2835b27f2351dd7e605980ed955348b6ec7a4618
Public Key PIN:
pin-sha256:QcwJ9TVQmsXtBHYcKDWyfyNR3X5gWYDtlVNItux6Rhg=
- Certificate[1] info:
- subject `CN=R3,O=Let's Encrypt,C=US', issuer `CN=ISRG Root
X1,O=Internet Security Research Group,C=US', serial
0x00912b084acf0c18a753f6d62e25a75f5a, RSA key 2048 bits, signed using
RSA-SHA256, activated `2020-09-04 00:00:00 UTC', expires `2025-09-15
16:00:00 UTC', pin-sha256="jQJTbIh0grw0/1TkHSumWb+Fs0Ggogr621gT3PvPKG0="
- Certificate[2] info:
- subject `CN=ISRG Root X1,O=Internet Security Research Group,C=US',
issuer `CN=DST Root CA X3,O=Digital Signature Trust Co.', serial
0x4001772137d4e942b8ee76aa3c640ab7, RSA key 4096 bits, signed using
RSA-SHA256, activated `2021-01-20 19:14:03 UTC', expires `2024-09-30
18:14:03 UTC', pin-sha256="C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M="
- Status: The certificate is trusted.
- Description: (TLS1.3-X.509)-(ECDHE-SECP256R1)-(RSA-PSS-RSAE-SHA256)-(AES-256-GCM)
- Session ID: 1B:FA:A7:4C:81:3D:6B:3E:9C:2D:65:EB:5D:52:44:4B:E8:2E:58:C9:4C:67:DE:69:AB:4F:F7:2C:10:5C:03:C6
- Options:
- Handshake was completed
- Simple Client Mode:
- Peer has closed the GnuTLS connection
real 2m34.806s
user 0m0.014s
sys 0m0.009s
on my wsl2 gnutls-cli doesn't go for ipv6. It immediately connects to
'209.51.188.89:443'...
Johan Laenen
Nov 29, 2023, 4:50:06 AM11/29/23
to
laenenj@L241362:/mnt/c/Windows/System32$ time gnutls-cli elpa.gnu.org
- Session ID: 8D:A7:2C:73:27:87:2D:12:1F:E3:C8:14:41:3F:12:CD:9B:3B:66:48:E4:C9:03:C4:09:D7:19:33:4B:17:AE:E4
user 0m0.041s
sys 0m0.000s
Processed 140 CA certificate(s).
Resolving 'elpa.gnu.org:443'...
Resolving 'elpa.gnu.org:443'...
- Options:
- Handshake was completed
- Simple Client Mode:
- Peer has closed the GnuTLS connection
real 0m20.525s
- Handshake was completed
- Simple Client Mode:
- Peer has closed the GnuTLS connection
user 0m0.041s
sys 0m0.000s
0 new messages