I’m puzzled. Whenever I do a package-refresh-contents or whenever I try to launch mastodon.el (M-x mastodon) my #emacs hangs. package-refresh-contents only shows ‘Contacting host: elpa.gnu.org:443’ and doesn’t do much more. I have to ctlr-g to break out or wait a couple of minutes before emacs says that the package refresh is done. mastodon.el is a different beast. After a wait I get ‘Wrong type argument: stringp, nil’.
Thing is, this does not happen when I’m on the vpn for work!
My two other computers at home experience the exact same issue. These two don’t have any vpn software installed, just plain debian. The computer with the vpn is a Windows 10 with WSL2 running debian as well. I use cntlm when on the vpn and I set my proxy accordingly. On my plain debian home boxes I don’t use any proxy. I use the same .emacs file on all three machines.
Was it a debian apt-get update that did this to me? I have no idea. Anyone here with a similar issue?
You must log in or register to comment.
I’ll be damned… Switching to ipv4 makes it work again:
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 = 1Now I can M-x mastodon and I can use package-refresh-contents.
Why this? I have to look at all of the debian changes of the month.
What config do you have for
mastodon.elin yourinit.elfile?Do you get any warnings or errors when starting Emacs?
No error messages during start up, that’s the confusing thing. I have been using this configuration for months without any trouble at all. I set mastodon-instance-url and mastodon-active-user in my .emacs file. As I said before, when on my companies vpn it works without a glitch. Without the vpn I get a ‘Wrong type argument: stringp, nil’.