X11 in Leopard
MacBook Pro, Mac OS X (10.5), HOLY CRAP I HAVE LEOPARD!!!!!
MacBook Pro, Mac OS X (10.5), HOLY CRAP I HAVE LEOPARD!!!!!
Son of a Beach wrote:
With the new Leopard implementation of X11, there appears to be no way to host X11 apps from remote machines that do not allow SSH X11 forwarding. We have all our Solaris systems at work set up with X11 forwarding set to "no", and now I cannot use ANY X11 applications on those remote machines, because I have no normal X11 display on the Mac for them to connect to.
How am I supposed to get these remote systems to use my Mac as an X11 host without SSH forwarding (ie, using plain old X11 withough SSH forwarding)?
automat wrote:
bbyer wrote:
It took a little bit of digging, but that Debian patch made it into X.org here: http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=commit;h=7dc7ef398b6ad90c cd1680ed9cd1cfdd47312f5a
... which fell between X.org's 1.1.1 and 1.1.2 releases. Leopard shipped with 1.1.2 (which had a bad flaw in it, so I've made available a built version of 1.1.3), so that's one bug that should not be responsible for the problems you're seeing.
That's all, carry on. 🙂
Ben
In the case of Debian based distros, it was necessary to revert to a version of libX11 pre- 1.1.2 release (Debian actually dropped back to 1.0.2, whereas Mandriva rolls back to 1.1.1). So if it is the libX11 patch that's causing the error on Leopard's X11 (as in the case of my linux machines), it would be necessary to build an old version of libX11 for Leopard. On linux, it was possible to downgrade only libX11 without affecting the rest of the Xorg distribution. Would this be even remotely feasible on Leopard?
I know it's inherently stupid to roll back to a broken lib (if its even possible), but it would be a good temporary solution until we can sort out the switch to the IDL 6.4 license server.
X11 in Leopard