Fwd: Re: Testing Gutsy amd64 and ltsp i386

Gavin McCullagh gmccullagh at gmail.com
Tue Oct 9 16:25:42 BST 2007


Hi,

On Tue, 09 Oct 2007, guillermo wrote:

> > Does the client lock up to the point that the mouse
> > doesn't move?  That must be a thin client crashing I guess.  
> 
> Not often but is does. Sometimes the only thing that
> moves is the mouse.

What I'm wondering is what's locking up.  

If, the network connection went, the mouse would keep moving but you'd get
no response to your actions (you can try pulling the network cable to see
that).  This is because the X server software on your thin client controls
the mouse, but it can't tell the application (on the server) that a button
click has happened.

If the mouse ceases to move entirely, chances are the X server (software on
the client), the mouse driver or the entire thin client has hung.

If the mouse keeps moving, it could be that somehow the network connection
died, the application died or something like that.  It would be interesting
to try:

1. set the root password on the thin clients
	https://help.ubuntu.com/community/EdubuntuFAQ#head-285f03d2d3ed2f29847c7793dbdb8f1488814c1b
2. when the crash happens, press <ctrl><alt><F1> 
3. look at the output of the command dmesg 
4. look for errors in /var/log/ldm.log /var/log/syslog,
   /var/log/xorg.0.log, etc.

If you can do the above, chances are the network is probably not gone.  You
might be enlightened by something in the logs.

> I've tested on two pcs celeron 466 , same motherboard,
> sound card es1371 and network card realtek 8139
> compatible, Ram 256 MB. 

What video card and video ram do the clients have?

> In the same server I've have installed dapper working in a real situacion
> (classroom 1 server and 8 thin clients) sometimes also freezes but not to
> the point to be a problem. I mean, if a thin client freezes the students
> just reboot it.

The server never freezes though, right?  It's just more regular with
feisty, yeah?

> I appreciate very much your help. I'm going to reinstall the server again
> and check if the problem repeats in the same way. 

If that's what you need to do fair enough.

Gavin




More information about the edubuntu-users mailing list