On 28-Sep-2007 15:58.38 (BST), Stephane Aicardi wrote: > I have the same problem in my installation and I found out a work around. > To avoid the "_X11TransSocketINETConnect() can't get address for" error, the > name of the remote X server (aries.logilab.fr in your example) needs to be in > your /etc/hosts file. > > Obviously, nspluginwrapper doesn't use /etc/resolv.conf or libresolv to id > the > IP address of your X server.
That's an interesting side effect. I'm not quite sure what to make of this. Name resolution is handled by the C library, so you shouldn't have problems with inconsistencies between the 64-bit and 32-bit environments. And the X network transport is handled by Xlib, not by nspluginwrapper specifically. In theory, all of this should be totally abstracted and the application (nspluginwrapper) should be totally oblivious of this behaviour. The only thing I can think is that the DISPLAY environment variable is being munged before the i386 wrapper runtime is being executed. The use of i386 chroots has proved to be an issue in the past - can you possibly tell me if you have an i386 chroot installed? Furthermore, are you starting an application inside the chroot before starting your browser? Because if so, the 32-bit C library may be using the configuration files from the chroot if an application inside it has already been launched. I can test the xdmcp setup myself now, since I've finished unpacking the rest of my machines. I'll let you know if I find out what the problem is. rob. -- rob andrews :: pgp 0x5c205974 :: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
