ltsp ldm does not start properly

[Roland Ronquist]

Binary package hint: ltsp-client

this may be related to #138089

when I first updated to Gutsy a few days back the ldm did not
manage to go from text mode to graphical mode on any of our
clients. Since I did not get many messages out of the process
of starting ldm I chose the xdmcp way instead.

But when I tried ldm again yesterday, it was much more
in a talkative mode, so I figured that somebody might be
interested and up to the task of grok the messages:

---8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----
W: module-detect.c: failed to detect any sound hardware
E: module.c: failed to load module "module-detect" (argument: "") : initialization failed.
E: main.c: Module load failed.
E: main.c: failed to initialize daemon.
---8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----

Unfortunately nothing ended up in my server log files as I look things
over now. If that is because the client is not logging as it should or
because the server refuses to listen is not known to me. Though
it usually did listen when I was running feisty, but now I just recently
upgraded and things are still to be all clean and nice.

[Oliver Grawert (ogra)]

did you just apt-get update/upgrade your cleint chroot for upgrading ?
thats unlikely to bring you all features, we switched to a completely new underlying arcjhitecture for ltsp (no nfs anymore for example)
https://help.ubuntu.com/community/UbuntuLTSP/LTSPWithoutNFS has some info
if you just upgraded, i would really recommend to move your old /opt/ltsp/i386 to /opt/ltsp/i386-bak and re-run ltsp-build-client from the gutsy ltsp-server package to create a chroot from scratch and also get the benefit of the significant squashfs/unionfs speedup.

[Roland Ronquist (roland-ronquist)]

As you might have already seen from my eager writings on defect #138089,
I do use "ltsp-build-client" from a clean startingpoint.

The interesting thing is that since I now use the CONFIGURE_X=True configuration
as you kindly suggested for #138089, I am not getting the error messages stated
above any more.

Thanks for mentioning the documentation for ltsp without nfs.

So I have 4 question:

1. will it help you in any way if I use the CONFIGURE_X=False and send you
the messages from running that?

2. is there anything that I did not mention in my latest postings on #138089
that could help you figuring out what is going wrong.

3. could this be something hardware related? I am doing most of my testing
on an Hp 5x00 something with a Crusoe inside, but we have other thin machines
as well. As far as I can understand this particular Hp is very popular/common
both among professional users and on the hobbyist scene.

4. is there anything I can do to increase debug output from ldm? or anything
that you need to better understand what is going bad.