[Linux] Portacle not starting without internet connection ?

[the-drunk-coder]

I'm on Arch Linux and observed the following oddity:

Whenever i try to start portacle without an internet connection running, the following
error appears:

Debugger entered: (("Error in timer" slime-attempt-connection (#<process inferior-lisp> nil 3) (error "localhost/46719 Der Name oder der Dienst ist nicht bekannt")))
  slime-timer-call(slime-attempt-connection #<process inferior-lisp> nil 3)
  apply(slime-timer-call (slime-attempt-connection #<process inferior-lisp> nil 3))
  timer-event-handler([t 23697 19577 754968 nil slime-timer-call (slime-attempt-connection #<process inferior-lisp> nil 3) nil 363999])

When the connection is running (configured using NetworkManager), everything seems fine. I don't quite understand where this is coming from, and it feels a little uncanny. Maybe somebody has a hint?

[Shinmera]

No idea. It is connecting to localhost as shown in the error, so the only idea I have is that your network configuration is messed up and doesn't loop back on localhost, but instead somehow depends on the internet connection.

[the-drunk-coder]

It is weird, especially as regular Emacs+Slime doesn't have that problem. Maybe it's some timeout issue ?

[Shinmera]

Ah- in that case: portacle has to use some really nasty workarounds to make glibc and libnss work. Basically the name resolution under portacle cannot use modules other than libnss_files, all other things like systemd and what have you are stubbed out to use libnss_files. Make sure you have the appropriate localhost entry in /etc/hosts and a useful value in /etc/resolv.conf

[Shinmera]

You might also have to look at /etc/nsswitch.conf

[the-drunk-coder]

The sbcl process is running on the correct port:

sudo ss -tulpn
tcp    LISTEN   0        5              127.0.0.1:35097          0.0.0.0:*      users:(("sbcl",pid=8938,fd=3))   

[the-drunk-coder]

Haven't had this problem for a long time now ... not even sure if i changed anything ? But I guess the issue could be closed.

[vyrsh]

could this be a arch linux thing? I got the same error. However I do have an internet connection.

Debugger entered: (("Error in timer" slime-attempt-connection (# nil 19) (error "localhost/34763 Name or service not known")))
slime-timer-call(slime-attempt-connection # nil 19)
apply(slime-timer-call (slime-attempt-connection # nil 19))
timer-event-handler([t 25204 4292 822648 nil slime-timer-call (slime-attempt-connection # nil 19) nil 829999])

[MGadhvi]

Can confirm that I am having the same issue on Arch

Debugger entered: (("Error in timer" slime-attempt-connection (#<process inferior-lisp> nil 4) (error "localhost/45895 No address associated with hostname")))
  slime-timer-call(slime-attempt-connection #<process inferior-lisp> nil 4)
  apply(slime-timer-call (slime-attempt-connection #<process inferior-lisp> nil 4))
  timer-event-handler([t 25249 10164 37944 nil slime-timer-call (slime-attempt-connection #<process inferior-lisp> nil 4) nil 825999])

[Shinmera]

do you have localhost in your /etc/hosts? If not your system is not set up correctly.

[MGadhvi]

do you have localhost in your /etc/hosts? If not your system is not set up correctly.

I believe so. My /etc/hosts is as follows

127.0.0.1    localhost
::1          localhost
127.0.1.1    myComputer.localdomain myComputer

[Shinmera]

Hrm. Probably another glibc/nss problem, then. Very annoying.

[MGadhvi]

If it helps, this is the output in the shell:

Desktop/portacle » ./portacle.run
/usr/lib/gio/modules/libdconfsettings.so: undefined symbol: g_log_structured_standard
Failed to load module: /usr/lib/gio/modules/libdconfsettings.so
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.

(Portacle:4334): GdkPixbuf-WARNING **: Error loading XPM image loader: Image type 'xpm' is not supported

[graven04]

is this issue fixed because I also have the same issue, and i am running arch linux as well.

[Brychlikov]

I have the same issue, also on Arch, and also using Network Manager. Although amusingly, it only occurs when my connection is active - when I disconnect from my network everything works fine.