Wie XDMCP mit GDM? (gdm_slave_child_handler: 1900 died)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hallo,
ich möchte mich mit X-Win32 von einem Win32 Rechner aus an meinem Debian
Server anmelden.
Leider habe ich das bisher nur mit kdm und xdm hinbekommen.
Der gdm macht da irgendwie Probleme.
Auf dem Remotebildschirm erscheint zwar der Umriss des
gdm-login-Fensters, aber bevor alles richtig dargestellt ist, wird die
Verbindung wieder getrennt.
Syslog hat im Debugmodus des gdm folgendes zu bieten:
Apr 26 20:05:53 lenox gdm[1864]: gdm_server_start: Completed :0!
Apr 26 20:05:53 lenox gdm[1864]: Sending XPID == 1865 for slave 1864
Apr 26 20:05:53 lenox gdm[1864]: Sending XPID 1864 1865
Apr 26 20:05:53 lenox gdm[1499]: Handeling message: 'XPID 1864 1865'
Apr 26 20:05:53 lenox gdm[1499]: Got XPID == 1865
Apr 26 20:05:53 lenox gdm[1864]: gdm_slave_usr2_handler: :0 got USR2 signal
Apr 26 20:05:53 lenox gdm[1864]: gdm_slave_run: Opening display :0
Apr 26 20:05:56 lenox gdm[1864]: Sending START_NEXT_LOCAL
Apr 26 20:05:56 lenox gdm[1499]: Handeling message: 'START_NEXT_LOCAL'
Apr 26 20:05:56 lenox gdm[1864]: gdm_slave_greeter: Running greeter on :0
Apr 26 20:05:56 lenox gdm[1864]: gdm_slave_child_handler
Apr 26 20:05:56 lenox gdm[1864]: gdm_slave_greeter: Greeter on pid 1869
Apr 26 20:05:56 lenox gdm[1864]: Sending GREETPID == 1869 for slave 1864
Apr 26 20:05:56 lenox gdm[1864]: Sending GREETPID 1864 1869
Apr 26 20:05:56 lenox gdm[1499]: Handeling message: 'GREETPID 1864 1869'
Apr 26 20:05:56 lenox gdm[1499]: Got GREETPID == 1869
Apr 26 20:05:56 lenox gdm[1864]: gdm_slave_usr2_handler: :0 got USR2 signal
Apr 26 20:05:57 lenox gdm[1864]: gdm_slave_wait_for_login: In loop
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_decode: Received opcode QUERY
from client 192.168.0.10
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_handle_query: Opcode 2 from
192.168.0.10
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_send_willing: Sending WILLING
to 192.168.0.10
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_decode: Received opcode
REQUEST from client 192.168.0.10
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_handle_request: Got REQUEST
from 192.168.0.10
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_handle_request: pending=0,
MaxPending=4, sessions=0, MaxSessions=16
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_display_dispose_check
(malcolm.tower-net.all:0)
Apr 26 20:07:36 lenox gdm[1499]: gdm_auth_secure_display: Setting up
access for malcolm.tower-net.all:0
Apr 26 20:07:36 lenox gdm[1499]: gdm_auth_secure_display: Setting up
network access
Apr 26 20:07:36 lenox gdm[1499]: gdm_auth_secure_display: Setting up
access for malcolm.tower-net.all:0 - 1 entries
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_display_alloc:
display=malcolm.tower-net.all:0, session id=1019844353, pending=1
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_send_accept: Sending ACCEPT
to 192.168.0.10 with SessionID=1019844353
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_decode: Received opcode
MANAGE from client 192.168.0.10
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_handle_manage: Got MANAGE
from 192.168.0.10
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_handle_manage: Got Display=0,
SessionID=1019844353 from 192.168.0.10
Apr 26 20:07:36 lenox gdm[1499]: gdm_xdmcp_handle_manage: Looked up
malcolm.tower-net.all:0
Apr 26 20:07:36 lenox gdm[1499]: gdm_choose_indirect_lookup: Host
192.168.0.10 not found
Apr 26 20:07:36 lenox gdm[1499]: gdm_forward_query_lookup: Host
192.168.0.10 not found
Apr 26 20:07:36 lenox gdm[1499]: gdm_display_manage: Managing
malcolm.tower-net.all:0
Apr 26 20:07:36 lenox gdm[1499]: Resetting counts for loop of death
detection
Apr 26 20:07:36 lenox gdm[1499]: gdm_display_manage: Forked slave: 1898
Apr 26 20:07:36 lenox gdm[1898]: gdm_slave_start: Starting slave process
for malcolm.tower-net.all:0
Apr 26 20:07:36 lenox gdm[1898]: gdm_slave_start: Loop Thingie
Apr 26 20:07:36 lenox gdm[1898]: gdm_slave_run: Opening display
malcolm.tower-net.all:0
Apr 26 20:07:36 lenox gdm[1898]: gdm_slave_greeter: Running greeter on
malcolm.tower-net.all:0
Apr 26 20:07:36 lenox gdm[1898]: gdm_slave_child_handler
Apr 26 20:07:36 lenox gdm[1898]: gdm_slave_greeter: Greeter on pid 1900
Apr 26 20:07:36 lenox gdm[1898]: Sending GREETPID == 1900 for slave 1898
Apr 26 20:07:36 lenox gdm[1898]: Sending GREETPID 1898 1900
Apr 26 20:07:36 lenox gdm[1499]: Handeling message: 'GREETPID 1898 1900'
Apr 26 20:07:36 lenox gdm[1499]: Got GREETPID == 1900
Apr 26 20:07:36 lenox gdm[1898]: gdm_slave_usr2_handler:
malcolm.tower-net.all:0
~ got USR2 signal
Apr 26 20:07:41 lenox gdm[1898]: gdm_slave_child_handler
Apr 26 20:07:41 lenox gdm[1898]: gdm_slave_child_handler: 1900 died
Apr 26 20:07:41 lenox gdm[1898]: gdm_slave_child_handler: 1900 died of 6
Apr 26 20:07:41 lenox gdm[1499]: mainloop_sig_callback: Got signal 17
Apr 26 20:07:41 lenox gdm[1499]: gdm_cleanup_children: child 1898 returned 2
Apr 26 20:07:41 lenox gdm[1499]: gdm_child_action: Slave process returned 2
Apr 26 20:07:41 lenox gdm[1499]: gdm_display_unmanage: Stopping
malcolm.tower-net.all:0 (slave pid: 0)
Apr 26 20:07:41 lenox gdm[1499]: gdm_display_dispose: Disposing
malcolm.tower-net.all:0
Apr 26 20:07:41 lenox gdm[1499]: main: Exited main loop
In meinen Augen läuft alles richtig bis "gdm_slave_child_handler: 1900
died". Warum stirbt der handler?
Grüsse,
Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6-2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAjzJubcACgkQVai07/smEbjaegCdHOo7+93EIdRiqTHkPuQ02ezg
QrAAoIDNTSG0ptlNuPYg+EKLsf3KuDcE
=D2lP
-----END PGP SIGNATURE-----
--
Zum AUSTRAGEN schicken Sie eine Mail an debian-user-german-request@lists.debian.org
mit dem Subject "unsubscribe". Probleme? Mail an listmaster@lists.debian.org (engl)
Reply to: