On Tue, Sep 04, 2007 at 03:05:09PM -0600, Bryan Sutula wrote:
> After apt-get install ltsp-server, I try to execute ltsp-build-client. It
> completes, but the created chroot is missing some of config settings. The
> most important is the keyboard layout. Without this, the clients fail to
> boot into X. dexconf returns an error saying that the keyboard layout is
> missing.
>
> I've worked around this by adding the layout option to lts.conf:
>
> XKBLAYOUT = us
this should not be necessary, no...
> While trying to understand this behavior, I noticed that the chroot doesn't
> have the correct timezone (fixed this with "dpkg-reconfigure tzdata" in the
> chroot). I suspect that any other settings that were to be copied from the
> server are missing as well.
quite possible many missing values, yes. pulled in a patch from ubuntu
which should configure the timezone, which i hope to include in a new
upload soon. please report bugs as you find them.
> Just a shot in the dark, but could this be for the same reason as bug
> #440854? Could ltsp-build-client be executing code that tries to preseed
> debconf values without the "-e" option?
i can't imagine so, the only place ltsp-build-client uses debconf
preseeding is in /usr/share/ltsp/plugins/ltsp-build-client/Debian/
025-locales and 010-debconf-seeds.
looks like there's a significant bug in 025-locales ...
=== modified file 'server/plugins/ltsp-build-client/Debian/025-locales'
--- server/plugins/ltsp-build-client/Debian/025-locales 2007-06-01 15:40:37
+0000
+++ server/plugins/ltsp-build-client/Debian/025-locales 2007-09-05 03:36:34
+0000
@@ -33,7 +33,7 @@
fi
# set debian-installer/keymap question in the chroot if present on the
server
- debian_installer_keymap="$(debconf-get-selections
debian-installer/keymap)"
+ debian_installer_keymap="$(debconf-get-selections | grep
debian-installer/keymap)"
if [ -n "$debian_installer_keymap" ]; then
echo "$debian_installer_keymap" | chroot $ROOT
debconf-set-selections
fi
i've seen several installations running 5.0.8debian3 and not encountered
the problem you'r e having... so i wonder what's different about your
particular setup that causes X to fail...
thanks for reporting this issue...
live well,
vagrant
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
