GNOME Bugzilla – Bug 115612
metacity fails to start with ORBIIOPIPv4=1
Last modified: 2006-05-10 22:08:51 UTC
metacity version 2.4.34 (as shipped with RedHat 9) dies with: _X11TransSocketINETConnect: not INET host<hostname> Window manager error: Unable to open X display <hostname>:1.0 and metacity version 2.4.55 (as shipped in Ximian Desktop 2) just segfaults if ORBIIOPIPv4=1 is specified in ~/.orbitrc or /etc/orbitrc when you log in. Not exactly sure where the problem lies, could be ORBit2 or metacity (or probably a number of other things), but metacity is (at long last) the only application that won't start with the IPv4 IIOP transport enabled.
Well, it turns out that this only happens when you're connecting to a remote display and it happens at (or below) the gdk level, which is odd given that it only happens with metacity. Specifying the hostname as an IP address gets rid of the "_X11TransSocketINETConnect" line, but still fails to connect (even with the approrpiate xauth line or X access controls turned off entirely).
Still happening? I have no idea what this might be. Seems like it pretty much has to be an ORBit/X/GDK bug.
it stills happens with latest gnome technologies packages
/me wonders how one would possibly debug such a thing Has any of the changes to x/gdk/orbit/gconf/metacity in the last two and a half years happened to fix this?
I'm not entirely sure as it's been so long since I reported this bug I've forgotten some of the details required to trigger it. If I remember correctly it pretty much just involved setting ORBIIOPv4=1 in an orbitrc and connecting to a remote X server, in which case it appears to be solved. I think it's safe to close the bug. If I run into a problem in the future I can reopen it ;-P
Cool, thanks for following up. I'll mark it fixed for now, and hopefully it really is and you don't need to reopen it. :)