since I got the message of using CONFIGURE_X=True I finally to the plunge and went looking for some problems again.
So I did the following steps: 1. removed my /opt/ltsp/i386 tree 2. ran ltsp-build-client (which of course had a few things to complain about already having nbdroot configured in inetd.conf) 3. removed the offending line from inetd.conf 4. ran ltsp-update-image and ltsp-update-kernels (better safe than sorry) 5. /etc/init.d/openbsd-inetd restart 6. connect with thin client using startx, and, yes, IT WORKS! but only because I am evil/curious I also tried using ldm once, since Oliver kindly shared a few grains of wisdom regarding the inner workings of the CONFIGURE_X option above and I had a slight feeling that since nothing graphical had ever appeared so far when using ldm and gutsy on any of our thinner machines here, that using said option would make ldm happier. Even if ldm did not produce any errors, as far as I could find, it still did not start X. For those of you lacking better reading material, I enclose the dmesg output from my thin client of choice, while running ldm. ** Attachment added: "dmesg output from may failed ldm startup" http://launchpadlibrarian.net/9208115/dmesg-ldm.txt -- ltsp startx option does not work since X.org is not configured https://bugs.launchpad.net/bugs/138089 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
