Bug 83998 - metacity fails to do host lookups from the display string
metacity fails to do host lookups from the display string
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: metacity (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
: Triaged
Depends On:
Blocks: 79579 CambridgeTarget
  Show dependency treegraph
 
Reported: 2003-02-10 16:24 EST by P Jones
Modified: 2007-04-18 12:50 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-03 13:35:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
/etc/hosts file used in problem (441 bytes, text/plain)
2003-02-14 17:00 EST, P Jones
no flags Details

  None (edit)
Description P Jones 2003-02-10 16:24:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
on remote machines with addresses in the address part of the display var,
metacity fails to load.



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.enable xdmcp gdm
2.Xnest :2 -query ***MACHINENAME***
3.login 

    

Actual Results:  gnome-session crashed. wm crashed

Expected Results:  normal login

Additional info:

Logging in failsafe (where blip==machinename)
and running metacity by hand I see the error message:
_X11TransSocketINETConnect: not INET hostblip
Window manager error: Unable to open X display blip:2.0

(Then I have to ^C metacity as it loops)

I ran these to make sure that DNS, etc was functional:
$ host blip
blip.internal.datastacks.com has address 10.1.2.6
$ grep blip /etc/hosts
10.1.2.6        blip
$ dig +search blip
...
blip.internal.datastacks.com. 300 IN    A       10.1.2.6
...



When manually setting the display to "10.1.2.6:2.0", it runs Fine.
Comment 1 Havoc Pennington 2003-02-11 09:42:17 EST
Looks like an Xlib problem to me - does xterm work? or xclock?
Comment 2 Havoc Pennington 2003-02-11 20:01:45 EST
Please reopen on adding info.
Comment 3 P Jones 2003-02-11 20:24:41 EST
xterm, mwm, gnome-panel, and nautilus all work.

More looking into it seems that this condition only happens if the name in
address *IS* in /etc/hosts.
In this case, "blip".
Comment 4 Havoc Pennington 2003-02-13 12:45:12 EST
I really have no initial guess how metacity is different from other apps in this 
area, but will have a look.
Comment 5 Havoc Pennington 2003-02-14 16:24:17 EST
That error message occurs when gethostbyname() thinks the host is not a TCP/IP 
host; can you attach your /etc/hosts file? I don't know how it would happen or 
how it could be metacity-only.

I tried reproducing the problem with Xnest/xdmcp and it works for me, 
tried both with and without the hostname in /etc/hosts. I am trying with 
the latest beta though, not with 8.0.
Comment 6 P Jones 2003-02-14 17:00:40 EST
Created attachment 90098 [details]
/etc/hosts file used in problem
Comment 7 Havoc Pennington 2004-05-25 14:56:49 EDT
Please reopen if still present in Fedora Core 2

Note You need to log in before you can comment on or make changes to this bug.