some issues with ltsp5 on edubuntu edgy

Gavin McCullagh gmccullagh at gmail.com
Tue Dec 26 18:53:35 UTC 2006


Hi,

I started testing the edgy ltsp stuff in the past couple of days.  The main
test machine is a P3 900MHz server with a P4 2.8GHz thin client (yes I know
that sounds backwards!).

A few other issues I've noticed:

==Sound==
The first user who logins into a thin client is generally able to use sound
on the thin client, including startup sounds, totem, rhythmbox, etc.
Greater detail on which apps work or need modification has been posted
here.
	https://launchpad.net/bugs/73346 
If that user logs out and logs in again this continues to work.  However,
if the user logs out and a different user logs in, sound fails and (in many
cases) the applications fall back to playing through the server sound card.
I'm not clear why this is as yet.

At the moment, the only way I can let a later user use the sound card is to
reboot the thin client.

==LtspFS==
When a USB key is plugged in, an icon displays on the desktop which when
double clicked shows the contents, allows transfers.  If the key is removed
the icon disappears.  Nice.  This seems to work across several users,
logins, etc.

However, if there is a local disk, icons are also created for the
partitions on that disk.  Again this allows file transfers, etc. and may be
quite useful (though I'm not sure if it might confuse users a little).
This is fine but if one uses the device, logs out and logs in a second time
(as the same user) the icon while present, no longer works.  It seems that
the device gets locked by the first access, a number of ltspfs processes
persist on the thin client after logging out and the next session cannot
access these.  If another user logs in, they don't even see the icons.

When you double click on the icon, this message appears in
~/.xsession-errors

** (nautilus:23669): CRITICAL **: nautilus_launch_show_file: assertion `!nautilus_file_needs_slow_mime_type (file)' failed

but nothing much appears in any other places I've thought to look
(eg thinclient:/var/log/{boot,ldm.log}).

It seems perhaps that the difference might be that these ATA devices do not
hotplug so they don't get regularly "reset" as USB keys do.  

It would be interesting to know can anyone reproduce these?

Gavin





More information about the edubuntu-devel mailing list