Hello.

1°) Brand new fresh install of Lucid Lynx (Desktop) + LTSP 5.2 + all 
Lucid updates. Usual install procedure:
- Run ltsp-build-client
- Chroot to /opt/ltsp/i386 to set root passwd
- exit chrooted env
- ltsp-update-image
- Setup /etc/ltsp/dhcpd.conf
- NO lts.conf

Boot thin client: I tried 1 EeeBox and 1 IBM ThinkCentre. LDM shows up 
normally. Enter login+passwd. Accepted.

Then I get a full Lucid Gnome desktop... but completely inverted 
(bottom-up and right-left)!!!

I spent a couple of minutes wondering about the LTSP team sense of 
humor, but I decided they're were not this naughty :) Finally I found 
this: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/441586

Looks like proprietary Nvidia drivers on the server are messing with 
libGL and  generate havoc in thin client X config (even with Non Nvidia 
GPU).

Solutions (as stated in bug report):
- disable compiz for login accounts used on thin clients
- or uninstall Nvidia proprietary drivers on server

2°) Once initial fun solved (disabling compiz), i created the following 
lts.conf:
[default]
XSERVER="vesa"
LDM_DIRECTX=True
CONSOLE_KEYMAP="fr"

I got the following message when booting a thin client:
(process:276) : Glib-WARNING **: getpwuid_r(): failed due to unknown 
user id (0).

Thin client stopped here. I switched (CTRL+ALT+F1) to thin client 
console,  to check the local X.org log file, where I found:

(EE) VESA: kernel modesetting driver in use, refusing to load....

A local "ps aux" shows X is <defunct>. Back to the server, I tried 
different XSERVER values in lts.conf (radeon, vga) and I got the same error.

Should I conclude you can't use specific XSERVER values in lts.conf when 
Nvidia proprietary drivers are installed on the server?

Pierre.






------------------------------------------------------------------------------

_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to