Created attachment 154037 [details]
The xinetd config file for Xvnc

I know this may be an exotic bug, but I don't really know where else to file it.

I've configured this system to accept local connections from xvncviewer to the local port 5900 using xinetd with the attached file in the /etc/xinetd.d/ directory:

service Xvnc
{
        type = UNLISTED
        disable = no
        socket_type = stream
        protocol = tcp
        wait = no
        user = nobody
        only_from = localhost
        server = /usr/bin/Xvnc
        server_args = -inetd -query 127.0.0.1 -geometry 1024x768  -depth 16 -cc 3 -once -SecurityTypes None -extension XFIXES
        port = 5900
}

I've also configured gdm to listen for XDMCP (/etc/gdm/custom.conf):

# GDM configuration storage

[xdmcp]
Enable=true

[chooser]

[security]
DisallowTCP=false

[debug]

[daemon]
TimedLoginEnable=true
AutomaticLoginEnable=false
TimedLogin=guest
AutomaticLogin=guest
TimedLoginDelay=120
RemoteGreeter=/usr/lib/gdm/gdm-simple-greeter

If I run xvncviewer once, Xvnc queries gdm which successfully produces a login window in the xvncviewer session.

The problem comes when I try to run a second session after having logged out or while the first session is still in progress.  Theoretically, running multiple sessions would be ideal in case more than one user wants to login at the same time.  Again, I'm not sure it's a gdm bug, but if gdm is restarted after a logout, a new login is possible.  I thought that maybe someone knowledgeable could look into it in case it's easy to fix.