Re: [gdm-list] trouble with gdm

[Brian Cameron <Brian Cameron Sun COM>]

Jean:

> thank you for your prompt answer.

No problem.  I'm sorry to hear that my ideas didn't help at all.  You
might check the gdm-list email archives.  One user not long ago
complained that XDMCP wasn't working for him and then discovered that
the problem was because a firewall was setup disabling some traffic.

Also, you could try configuring GDM to disable IPv6 to see if that
makes a difference.

Note comments below.

> > Also, you might try upgrading to the latest version of GDM.  GDM 2.19.1
> > has newly rewritten XDMCP code that should work better.  You might find
> > more joy with it.
> I downloaded the version GDM 2.19.1 and I installed it. Unfortunately, I 
> have the same problem. By the way, by doing that, I have a new gdm (when 
> I type gdm --version I got 2.19.1) but gdmlogin and gdmgreeter have not 
> been upgraded by this new installation, is it worthwhile to upgrade them 
> and if yes how?

When you say that gdmgreeter and gdmlogin have not been upgraded.  How
can you tell?  Are you seeing a message complaining that they are a
different version when they try to startup?  If so, then this sounds
like you may have two versions of GDM installed on your system, perhaps
to different directories.

Note that older versions of GDM installed gdmlogin/gdmgreeter to
/usr/bin while they are now installed to /usr/lib.  Some distros also
may move them to other locations.

If so, make sure you aren't using mix-matched versions of the
daemon and GUI programs.  The GDM configuration file should specify
what commands it is actually using.  For example, note the Greeter
configuration option.  You can check what configuration options the
daemon recognizes with this command:

gdmflexiserver --command="GET_CONFIG daemon/Greeter"

(using the daemon/Greeter key as an example).

> I have the impression that my problem is may be not related to gdm. 
> Indeed, using a linux PC (with Fedora Core 6) I can connect via xdmcp my 
> server. Turning the debugging on, I got the following information:
>
> part of /var/log/messages lappc-f020 : server, lappc-f021 Linux PC and 
> lapxt144 : X Terminal
>
> using the Linux PC to connect the server:
>
> May 16 17:27:24 lappc-f020 gdmlogin[3993]: Sending command: 'GET_CONFIG 
> greeter/RemoteWelcome[C] lappc-f021.in2p3.fr:0'
> May 16 17:27:24 lappc-f020 gdm[2406]: Handling user message: 'GET_CONFIG 
> greeter/RemoteWelcome[C] lappc-f021.in2p3.fr:0'
> May 16 17:27:24 lappc-f020 gdm[2406]: Error returning config key 
> greeter/RemoteWelcome[C]
> May 16 17:27:24 lappc-f020 gdmlogin[3993]:   Got response: 'ERROR 50 
> Unsupported key <greeter/RemoteWelcome[C]>'
> May 16 17:27:24 lappc-f020 gdmlogin[3993]: Sending command: 'CLOSE'
> May 16 17:27:24 lappc-f020 gdm[2406]: Handling user message: 'CLOSE'
> May 16 17:27:24 lappc-f020 gdm[3983]: gdm_slave_wait_for_login: In loop
> May 16 17:27:37 lappc-f020 gdm[3983]: gdm_slave_wait_for_login: end 
> verify for 'root'
> May 16 17:27:37 lappc-f020 gdm[3983]: gdm_slave_wait_for_login: 
> got_login for 'root'
> May 16 17:27:37 lappc-f020 gdm[3983]: Sending LOGGED_IN == 1 for slave 3983
> May 16 17:27:37 lappc-f020 gdm[2406]: Handling message: 'LOGGED_IN 3983 1'
> May 16 17:27:37 lappc-f020 gdm[2406]: Got logged in == TRUE
>
> using the X Terminal to connect the server:
>
> May 16 12:58:27 lappc-f020 gdmlogin[2920]: Sending command: 'GET_CONFIG 
> greeter/RemoteWelcome[C] lapxt144.in2p3.fr:0'
> May 16 12:58:27 lappc-f020 gdm[2406]: Handling user message: 'GET_CONFIG 
> greeter/RemoteWelcome[C] lapxt144.in2p3.fr:0'
> May 16 12:58:27 lappc-f020 gdm[2406]: Error returning config key 
> greeter/RemoteWelcome[C]
> May 16 12:58:27 lappc-f020 gdmlogin[2920]:   Got response: 'ERROR 50 
> Unsupported key <greeter/RemoteWelcome[C]>'
> May 16 12:58:27 lappc-f020 gdmlogin[2920]: Sending command: 'CLOSE'
> May 16 12:58:27 lappc-f020 gdm[2406]: Handling user message: 'CLOSE'
> May 16 12:58:28 lappc-f020 gdm[2910]: gdm_slave_wait_for_login: In loop
> May 16 12:58:29 lappc-f020 gdm[2910]: term_quit: Final cleanup
> May 16 12:58:29 lappc-f020 gdm[2910]: gdm_slave_quick_exit: Will kill 
> everything from the display
> May 16 12:58:29 lappc-f020 gdm[2910]: Running gdm_verify_cleanup and 
> pamh != NULL
> May 16 12:58:29 lappc-f020 gdm[2910]: gdm_slave_quick_exit: Killed 
> everything from the display
> May 16 12:58:29 lappc-f020 gdm[2406]: mainloop_sig_callback: Got signal 17
> May 16 12:58:29 lappc-f020 gdm[2406]: gdm_cleanup_children: child 2910 
> returned 65
> May 16 12:58:29 lappc-f020 gdm[2406]: gdm_child_action: In remanage
> May 16 12:58:29 lappc-f020 gdm[2406]: gdm_display_unmanage: Stopping 
> lapxt144.in2p3.fr:0 (slave pid: 0)
> May 16 12:58:29 lappc-f020 gdm[2406]: gdm_display_dispose: Disposing 
> lapxt144.in2p3.fr:0
> May 16 12:58:29 lappc-f020 gdm[2406]: gdm_display_unmanage: Display stopped
>
>
> So in the two case, I got the same error message from gdmlogin (which 
> seems not responsible of the problem) but mysteriously with the X 
> Terminal the process stops ...........

I wonder if this is a firewall issue.

Brian