Xlib: extension "GLX" missing on display "localhost:12.0"

Hi H,
If you simply do a Google search on the error message, you'll see that it's not an uncommon error. I believe that one reference used the term "infamous". The problem appears to be that the app tries to use the 3-D acceleration of the graphics card directly.

Naturally you should try "ssh -Y" but if it works please let us know; I'd be amazed if you could do 3-D graphics acceleration with XWindows forwarding.
--
Gary
~~~~
<SomeLamer> what's the difference between chattr and chmod?
<SomeGuru> SomeLamer: man chattr > 1; man chmod > 2; diff -u 1 2 | less
-- Seen on #linux on irc

ssh -Y -- it doesn't seem to exist on my computer. Is it specific to OSX 10.4?

I'm using 10.3.9. "-Y" doesn't appear in the man pages. And, "-Y" is returned as an illegal option.

Does anybody have any solid info on this?

thx

It's specific to the newer verion of ssh that comes with 10.4.

I've got one:

This happens on one specific linux application (an Xray data processing program)

_X11TransSocketINETConnect: Can't get address for localhost
Error: Can't open display: localhost:10.0

I get that with either -Y or -X. Everything else works.

I've googled this, and implemented the suggestions I found but to no avail.

Anyone have any ideas?

Hi Bill,
I don't understand how you implemented the fix in the suggestion you found; OS X doesn't have a gdm, does it? Anyway, the closest thing to the gdm.conf would be the ~/Library/Preferences/com.apple.x11.plist file and there's a nolisten_tcp preference there. Is that what you meant? If not, changing that to false would be my recommendation. Otherwise, make sure that ports 6000-6063 are open in your firewall.

Actually, there's one other thing I didn't think about when I wrote the above. (Sorry, I'm sleepy) If the app were trying to connect through the tunnel that ssh sets up, both of the above suggestions would be useless but the connection would work. It kind of sounds like the app is trying to open other connections to the X server without using the tunnel. However, if it tries to connect outside of the tunnel, then DISPLAY 10 would be wrong. Maybe in order to reconcile these, you should not use ssh -Y and and set up the connection the old fashioned way. In that case, both of the above suggestions would be meaningful.

The only other thing I can think of is that maybe the "can't get address" error is valid. I seem to remember issues with IPv6 addresses being returned before 127.0.0.1. Maybe you could comment out the IPv6 address for localhost (::1) in the /etc/hosts file of the remote machine. Of course that would only be meaningful if the app were using the tunnel so maybe it is trying to use the tunnel. I agree with you, this is perplexing!
--
Gary
~~~~
Immature artists imitate, mature artists steal.
-- Lionel Trilling

Hi again Bill,
I edited the above answer so many times that editing timed out. I'm sorry the above is so rambling but the suggestion you found clearly doesn't involve an ssh tunnel because the "nolisten_tcp" doesn't apply to the server listening on the other end of the tunnel. That got me thinking on the wrong track. I am really sleepy; I need to borrow your old Homer icon. The attempt to connect to localhost:10 means that the app is trying to use the tunnel and I see no reason for it not to work. Thus, my third paragraph above must be closer to the right direction and this app is too stupid to resolve localhost.

If the suggestion in the third paragraph doesn't work, you would have to figure out how the app is trying to resolve localhost and that will involve your reporting the contents of the /etc/hosts file and the configuration of lookupd on the remote machine. (ssh server, X11 client)
--
Gary
~~~~
Anyone who thinks UNIX is intuitive should be forced to
write 5000 lines of code using nothing but vi or emacs.
AAAAACK!
-- Discussion on the intuitiveness of commands,
especially Emacs

Thanks, Gary, but I apologize for making you lose more sleep over this than I have.

There was a new version of Ubuntu released yesterday, so after I tried your suggestions, I thought maybe a new version would cure it.

Now it seg faults when I try to display remotely.

I think your analysis about the stupidity of the program was probably warranted.

I'm new here, but I got the same problem here.

I tried ssh -X host, and it gave me the error message.
when I change to ssh -Y host, it got the simulation window, except it's all black. None of my graphics figures are there. Could you let me know what should I do?

Thanks a lot.