After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 115612 - metacity fails to start with ORBIIOPIPv4=1
metacity fails to start with ORBIIOPIPv4=1
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
2.4.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2003-06-20 15:55 UTC by Shahms E. King
Modified: 2006-05-10 22:08 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Shahms E. King 2003-06-20 15:55:21 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.
Comment 1 Shahms E. King 2003-07-02 17:47:16 UTC
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).
Comment 2 Havoc Pennington 2003-09-26 01:27:10 UTC
Still happening? I have no idea what this might be. Seems like it
pretty much has to be an ORBit/X/GDK bug.
Comment 3 Michel Galle 2003-11-04 15:06:10 UTC
it stills happens with latest gnome technologies packages
Comment 4 Elijah Newren 2006-05-03 18:11:05 UTC
/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?
Comment 5 Shahms E. King 2006-05-10 22:01:06 UTC
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
Comment 6 Elijah Newren 2006-05-10 22:08:51 UTC
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.  :)