[08:31] <helpjeff_> hello
[08:31] <helpjeff_> i find driver for lexmark z735
[08:31] <helpjeff_> penpriniting write z730 work properly with generic postscript
[08:31] <helpjeff_> but not z735
[08:38] <helpjeff_> thank you
[10:09] <patxi> Hi all,
[10:10] <patxi> which file should I configure to use LDM by clients?
[10:10] <patxi> Right now, it shows GDM, but ldm is installed on /opt/ltsp/i286 chroot
[03:12] <sbalneav> Morning all
[03:13] <sbalneav> ogra: Hey, I added some options handling to ltsp-upate-kernels, ltsp-update-sshkeys and ltsp-update-image
[03:28] <stgraber> hi sbalneav
[03:28] <sbalneav> Hey stgraber
[03:29] <stgraber> sbalneav: while you are at it, I noticed that ltsp-build-client does't copy /etc/apt/apt.conf to the chroot
[03:29] <stgraber> sbalneav: and then doesn't work with http proxy
[03:29] <stgraber> sbalneav: can you quickly fix that as well ?
[03:29] <stgraber> sbalneav: I solved it by adding the cp before doing the apt-get update
[03:30] <sbalneav> Well, that one I'd want to check out with ogra before making the change.
[03:30] <sbalneav> I'm unsure he'd even like what I've done so far :)
[03:31] <sbalneav> Let me have a look in my tree here.  You say if you pass a proxy in the command line it doesn't put that in the chroot?
[03:31] <stgraber> sbalneav: yep
[03:31] <stgraber> sbalneav: I tried doing HTTP_PROXY="http://...." ltsp-build-client
[03:32] <stgraber> but didn't work (as apt doesn't care of the HTTP_PROXY IIRC, it needs a /etc/apt/apt.conf file)
[03:33] <sbalneav> Did you use the --mirror command line option?
[03:33] <stgraber> no
[03:34] <sbalneav> Try it with that, see if it copies that into the chroot.
[03:34] <stgraber> It was : ltsp-build-client --prompt-rootpass --dist gutsy
[03:34] <stgraber> (as I'm running a gutsy ltsp chroot on feisty edubuntu server)
[03:54] <bddebian> Heya
[04:12] <sbalneav> heading up for breakfast
[05:13] <EXP3> has anyone used edubuntu with LTSP?
[11:07] <JonNoob> Please help.. My ltsp clients won't login. The loginscreen disapers for a few seconds and goes to black and the returns. Auth.log shows the user being authorized, and a session is being started.