startx in lts.conf causes X in middle of screen

[Gary Taylor]

Thanks Oli for the information.

>>  X_MODE_0  = 1024x768
>> and maybe change
>>  XSERVER = ati
>the X_MODE variable is not supported yet in ubuntu ltsp, add
>the
>correct
>values for X_HORZSYNC and X_VERTREFRESH to get the
>resolution you want,

With my lts.conf like this:

[Default]
        SERVER             = 192.168.1.3
#        XSERVER            = auto
        XSERVER            = ati
        X_MOUSE_PROTOCOL   = "PS/2"
        X_MOUSE_DEVICE     = "/dev/psaux"
        X_MOUSE_RESOLUTION = 400
        X_MOUSE_BUTTONS    = 3
        USE_XFS            = N
        X_HORZSYNC          = 1024
        X_VERTREFRESH      = 768
#        SCREEN_01          = startx

using either XSERVER auto or ati

I get a terminal login like 

Ubuntu 5.10 "Breezy Badger"
ltsp tty1
ltsp login:

but when I attempt to login it dislays "Login incorrect".  ctrl-alt-f1 through
ctrl-alt-f6 give me a different vt.  ctrl-alt-f7 gives me a
black screen with a cursor blinking in the upper left.

With my lts.conf like this:
[Default]
        SERVER             = 192.168.1.3
        XSERVER            = auto
        X_MOUSE_PROTOCOL   = "PS/2"
        X_MOUSE_DEVICE     = "/dev/psaux"
        X_MOUSE_RESOLUTION = 400
        X_MOUSE_BUTTONS    = 3
        USE_XFS            = N
        X_HORZSYNC          = 1024
        X_VERTREFRESH      = 768
        SCREEN_01          = startx

I get xserver failed, press <enter> to continue. So I press
enter and am presented with the login prompt again but
attempting to login gives the same as above.  ctrl-alt-f1
through ctrl-alt-f6 give me a different vt.  ctrl-alt-f7
doesn't work.

With this setting:
[Default]
        SERVER             = 192.168.1.3
#        XSERVER            = auto
        XSERVER            = ati
        X_MOUSE_PROTOCOL   = "PS/2"
        X_MOUSE_DEVICE     = "/dev/psaux"
        X_MOUSE_RESOLUTION = 400
        X_MOUSE_BUTTONS    = 3
        USE_XFS            = N
       X_HORZSYNC          = 1024
        X_VERTREFRESH      = 768
        SCREEN_01          = startx

I get the busybox prompt with this error:
/bin/sh: can't access tty: job control turned off 
#


After testing a few changes and the necessary reboots my
client gets to an inconsistent state where it might only
display the busybox prompt and nothing else or have some
other problem.  In order for changes to get read from
lts.conf I have to reboot the server.  In fact it seems like
in order to get reliable testing resutls I need to reboot
the server after every change of lts.conf.  Looking in
/etc/init.d/ I can't see a service that I could restart
instead of rebooting.  Is there a service I should be
restarting instead?  

It seems like I can't find a reliable starting point from
which to make changes.

My installation is default where I've updated the system
per the update manager, enabled dhcp per the server setup
instructions.  
-- 
squeaky at sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org