Opened 8 years ago

Closed 7 years ago

#24143 closed defect (fixed)

ELinks 0.11.5 - won't load some pages

Reported by: ryan.wy.chan@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: expiation@…
Port: elinks


Performed a selfupdate and now elinks will not load some pages (it used to work before the selfupdate). I can load but if I try to connect to or I get an "unable to retrieve <website address>" "Error Reading from socket"

I tried loading and from Links and it works fine. Works fine using Safari as well.

Read a similar complaint online where the fix was to toggle the async.dns option, but this did not work for me.

Using a late 2008 MBP, OS X 10.6.2 if that helps.

Change History (9)

comment:1 Changed 8 years ago by mf2k (Frank Schima)

Cc: ryan.wy.chan@… removed
Keywords: elinks webpage doesn't load 0.11.5 async.dns removed
Owner: changed from macports-tickets@… to simon@…
Port: elinks added; ELinks 0.11.5 removed

comment:2 Changed 8 years ago by rmsfisher@…

I get the same behavior when running 'elinks' but can browse to in Firefox.

comment:3 Changed 8 years ago by joergahrens (Jörg Ahrens)

The problem is related to zlib version. It appears with zlib @1.2.4_1 and zlib @1.2.5_0 . It does not appear with zlib @1.2.3_4

comment:4 Changed 8 years ago by simon@…

Owner: changed from simon@… to macports-tickets@…

comment:5 Changed 8 years ago by expiation@…

Cc: expiation@… added

Cc Me!

comment:6 Changed 8 years ago by expiation@…

What's the likely resolution here? It seems to affect all the elinks versions up to the current 0.11.7 and affects a very large number of sites. Is it something specific to the zlib we have in Macports or something upstream?

For those wanting to work around this for the time being, go back to your old version of zlib (see

comment:7 Changed 8 years ago by perry@…

You can also use the port elinks-devel. elinks works for me.

The following ports are currently installed:
  elinks-devel @0.12pre5_1+universal (active)
  zlib @1.2.5_0+universal (active)

comment:8 Changed 8 years ago by perry@…

Also note that this version is older than upstream, which is at 0.11.7. Updating the port might fix the problem.

comment:9 Changed 7 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.