Based on the various Google searches I did, this all looks normal.  It
really appears to me that the Labtam X server on your Windows system is
refusing to authorize/authenticate the Linux system.

As someone else pointed out, when you use MI/X, you need to SSH to the Linux
system (make sure you have X Forwarding turned on in /etc/ssh/sshd_config)
and start your X client there.  It should display just fine on your Windows
system.

I am curious, though, why you want to have a GNOME desktop running on your
mainframe.  Seems like an awful waste of CPU cycles and network bandwidth.


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Pinion
Sent: Monday, August 23, 2004 3:30 PM
To: [EMAIL PROTECTED]
Subject: Re: Slack/390


I give up, I've tried everything suggested and everything I can think of
(which ain't much!!!).

One last attempt here's the debugging stuff thrown to /var/log/syslog

Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_decode: Received opcode QUERY
from client 172.30.0.249
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_handle_query: Opcode 2 from
172.30.0.249
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_host_allow: client->hostname is
dabmi40801.bhsetdc.org
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_send_willing: Sending WILLING
to 172.30.0.249
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_decode: Received opcode REQUEST
from client 172.30.0.249
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_handle_request: Got REQUEST
from 172.30.0.249
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_host_allow: client->hostname is
dabmi40801.bhsetdc.org
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_handle_request:
xdmcp_pending=0, MaxPending=4, xdmcp_sessions=0, MaxSessions=16,
ManufacturerID=
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_display_dispose_check
(dabmi40801.bhsetdc.org:0)
Aug 23 10:26:26 linux390 gdm[228]: gdm_auth_secure_display: Setting up
access for dabmi40801.bhsetdc.org:0
Aug 23 10:26:26 linux390 gdm[228]: gdm_auth_secure_display: Setting up
access
Aug 23 10:26:26 linux390 gdm[228]: gdm_auth_secure_display: Setting up
access for dabmi40801.bhsetdc.org:0 - 1 entries
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_display_alloc:
display=dabmi40801.bhsetdc.org:0, session id=-1671202951, xdmcp_pending=1
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_send_accept: Sending ACCEPT to
172.30.0.249 with SessionID=-1671202951
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_decode: Received opcode MANAGE
from client 172.30.0.249
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_handle_manage: Got MANAGE from
172.30.0.249
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_host_allow: client->hostname is
dabmi40801.bhsetdc.org
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_handle_manage: Got Display=0,
SessionID=-1671202951 Class=MIT-unspecified from 172.30.0.249
Aug 23 10:26:26 linux390 gdm[228]: gdm_xdmcp_handle_manage: Looked up
dabmi40801.bhsetdc.org:0
Aug 23 10:26:26 linux390 gdm[228]: gdm_choose_indirect_lookup: Host
172.30.0.249 not found
Aug 23 10:26:26 linux390 gdm[228]: gdm_forward_query_lookup: Host
172.30.0.249 not found
Aug 23 10:26:26 linux390 gdm[228]: gdm_display_manage: Managing
dabmi40801.bhsetdc.org:0
Aug 23 10:26:26 linux390 gdm[228]: loop check: last_start 0, last_loop 0,
now: 1093271186, retry_count: 0
Aug 23 10:26:26 linux390 gdm[228]: Resetting counts for loop of death
detection
Aug 23 10:26:26 linux390 gdm[228]: gdm_display_manage: Forked slave: 280
Aug 23 10:26:26 linux390 gdm[280]: gdm_slave_start: Starting slave process
for dabmi40801.bhsetdc.org:0
Aug 23 10:26:26 linux390 gdm[280]: gdm_slave_start: Loop Thingie
Aug 23 10:26:26 linux390 gdm[280]: gdm_slave_run: Opening display
dabmi40801.bhsetdc.org:0
Aug 23 10:26:26 linux390 gdm[280]: gdm_slave_greeter: Running greeter on
dabmi40801.bhsetdc.org:0
Aug 23 10:26:27 linux390 gdm[228]: (child 280) gdm_slave_child_handler
Aug 23 10:26:27 linux390 gdm[280]: gdm_slave_greeter: Greeter on pid 285
Aug 23 10:26:27 linux390 gdm[280]: Sending GREETPID == 285 for slave 280
Aug 23 10:26:27 linux390 gdm[280]: Sending GREETPID 280 285
Aug 23 10:26:27 linux390 gdm[228]: Handling message: 'GREETPID 280 285'
Aug 23 10:26:27 linux390 gdm[228]: Got GREETPID == 285
Aug 23 10:26:27 linux390 gdm[228]: (child 280) gdm_slave_usr2_handler:
dabmi40801.bhsetdc.org:0 got USR2 signal
[EMAIL PROTECTED]:/var/state/gdm#


I've even tried a different Windows Xserver, MicroImages MI-X 4.1.  All I
have is the blue screen with the little mouse clock or whatever that mouse
pointer thingy is!

>>> [EMAIL PROTECTED] 08/23/04 12:29PM >>>
I'm not at all familiar with Labtam, but it looks as though your problem
involves authorization, perhaps having to do with the MIT Magic Cookie.  You
might want to try looking at your X server setup on your Windows system, and
see what kind of authentication/authorization is needed.

Another option is to find the [debug] section in gdm.conf, and change the
line "Enable=false" to "Enable=true" and restart gdm.


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Pinion
Sent: Monday, August 23, 2004 8:41 AM
To: [EMAIL PROTECTED]
Subject: Re: Slack/390


I think I have this line coded as you suggested,

[xdmcp]
# Distributions: Ship with this off.  It is never a safe thing to leave
# out on the net.  Alternatively you can set up /etc/hosts.allow and
# /etc/hosts.deny to only allow say local access.
Enable=true

I don't know if this will be of any benefit but I am including the log from
Labtam's Xserver.


I am not able to get xdm to start as well.

Thanks!

>>> [EMAIL PROTECTED] 08/22/04 05:54PM >>>
Richard,

/etc/X11/gdm/gdm.conf, line number 131 needs to be changed to "Enable=true"
and then gdm restarted.

Did you ever get xdm to start?  If not, I'd like to try to get that problem
figured out and fixed.


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Richard Pinion
Sent: Thursday, August 19, 2004 9:57 AM
To: [EMAIL PROTECTED]
Subject: Re: Slack/390


What do I need to add/change in the gdm config file to enable this?

>>> [EMAIL PROTECTED] 08/19/04 08:53AM >>>
On Iau, 2004-08-19 at 13:49, Richard Pinion wrote:
> I login as root and type in gdm and the same for xdm.  gdm comes up but I
can't get a session using Labtam's Xserver Windows software.

gdm defaults to local access only. Either gdmconfig or fiddling with the
config file by hand can be used to change that

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to