IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 14 April 2010   (all times are UTC)

00:01alkisg has joined #ltsp
00:52Faithful has quit IRC
01:17Faithful has joined #ltsp
01:54gnunux has joined #ltsp
01:55
<gnunux>
hi
02:00cyberorg has quit IRC
02:17mikkel has joined #ltsp
02:49Selveste1_ has quit IRC
03:18Selveste1_ has joined #ltsp
03:19Selveste1_ has quit IRC
03:19Selveste1 has joined #ltsp
03:34Selveste1_ has joined #ltsp
03:34Selveste1 has quit IRC
04:11
<alkisg>
stgraber: cisco routers do not work with clientid='', i.e. they don't send a dhcp offer so the clients won't boot
04:11
Are you sure that's the only way to prevent dhcp3-server from needing 2 IPs per client?
04:41highvoltage has joined #ltsp
05:03highvoltage has quit IRC
05:05highvoltage has joined #ltsp
05:14
<alkisg>
stgraber: I tested here locally with dhcp3-server and *without* sending a clientid (i.e. the default udhcpc behavior) and my client used the same IP address that it had in PXE...
05:15
So I think we should ditch the clientid hack altogether...
05:17johnny has joined #ltsp
05:21klausade has joined #ltsp
05:28cyberorg has joined #ltsp
05:36gnunux has quit IRC
05:37
<alkisg>
Uhm, and maybe we can send a patch for udhcpc so that it doesn't send a clientid at all (not send an empty one)
06:03hersonls has joined #ltsp
06:24Selveste1_ has quit IRC
06:28pmatulis has joined #ltsp
06:34Barbosa has joined #ltsp
06:35ogra_cmpc has quit IRC
06:42scottmaccal has joined #ltsp
07:07gnunux has joined #ltsp
07:18Selveste1_ has joined #ltsp
07:29Selveste1_ has quit IRC
07:30Selveste1_ has joined #ltsp
07:34scottmaccal has quit IRC
07:34Selveste1__ has joined #ltsp
07:35Selveste1_ has quit IRC
07:35ogra has quit IRC
07:36Faithful has quit IRC
07:36ogra has joined #ltsp
07:37alkisg has quit IRC
07:47Barbosa has quit IRC
08:08alkisg has joined #ltsp
08:16Selveste1__ has quit IRC
08:16Selveste1__ has joined #ltsp
08:21Gadi has joined #ltsp
08:22komunista has joined #ltsp
08:23Selveste1__ has quit IRC
08:23
<komunista>
hi
08:30vbundi has quit IRC
08:36komunista has quit IRC
08:38Selveste1__ has joined #ltsp
08:39ogra_cmpc has joined #ltsp
08:45Nikratio has joined #ltsp
08:45komunista has joined #ltsp
08:48
<Nikratio>
On my Ubuntu karmic ltsp clients, the /etc/hosts file is always garbled. After the server ip, I have about 30 "-f\n" entries, before the final "-f server" line. If I restart /etc/init.d/ltsp-client-setup, the file is generated correctly. Anyone has an idea where to look for the problem?
08:51yodan has joined #ltsp
08:52
<alkisg>
Nikratio: can you try to specify SERVER=ip in lts.conf?
08:52
I think that bug was solved some months ago, but I don't remember the exact details
08:52
<Nikratio>
Which BTS was it in?
08:53
<alkisg>
BTS==??
08:53
<Nikratio>
Bug Tracking System
08:53
So I can look it up
08:53
<alkisg>
I'm not sure if it was in any BTS, but if it was, it was in launchpad
08:54Selveste1__ has quit IRC
08:54
<alkisg>
We may have fixed it without filing any bug reports, though
08:54
<Nikratio>
ah, ok. I'll try the lts.conf change then
08:56vmlintu has joined #ltsp
09:00
<Nikratio>
yes, that fixed it
09:00
Thanks!
09:01
<alkisg>
OK, don't bother with it anymore, it was fixed for Lucid (even though I don't remember the commit #)
09:03
<Nikratio>
great, thanks again
09:05Nikratio has left #ltsp
09:06pmatulis has quit IRC
09:10pmatulis has joined #ltsp
09:22Faithful has joined #ltsp
09:24alkisg has quit IRC
09:25vmlintu has quit IRC
09:26alkisg has joined #ltsp
09:30vmlintu has joined #ltsp
09:35pmatulis has quit IRC
09:36mikkel has quit IRC
09:37pmatulis has joined #ltsp
09:37mischko has joined #ltsp
09:38bobby_C has joined #ltsp
10:18lipinski has joined #ltsp
10:19
<lipinski>
How can I troubleshoot a hanging client? It starts up fine, and I can log in, start applications, but eventually it hangs and the screen is semi-frozen. Mouse still moves, but can't click on anything or do anything.
10:19
Looking for some insight on how to start troubleshooting....
10:21
<vmlintu>
Does it answer to ping?
10:24
<lipinski>
yes
10:24yodan has quit IRC
10:24
<lipinski>
I'm trying a new test where I start up firefox and just let it sit at the home page. I'm thinking maybe Facebook or some page like that is causing a problem.
10:25
I just don't know how to start troubleshooting it. Where would logs be? Do I have to add sshd to the client to be able to get in and check things out? , etc..?
10:26thunsucker has joined #ltsp
10:29
<vmlintu>
Having sshd on the client helps a lot
10:30
To get logs, you have to enable remote logging on the server. Which distro are you running?
10:33pmatulis has quit IRC
10:33pmatulis has joined #ltsp
10:36vagrantc has joined #ltsp
10:44Selveste1__ has joined #ltsp
10:45gnunux has quit IRC
10:46pmatulis has quit IRC
10:46pmatulis has joined #ltsp
11:09
<lipinski>
vmlintu: Sorry, got pulled away... I'm currently running Ubuntu 9.10. I'm going to be upgrading to 10.04 LTS in the next week or so (maybe Beta 2, maybe wait for official release)..
11:09
So, I really am trying to "band-aid" this hang problem to late me until I can get the server on 10.04
11:12
<vmlintu>
Try first installing sshd in the chroot
11:13
Once you can login to the client, try running at least top or some similar tool to see if there's something unusual when it freezes
11:14
<Gadi>
lipinski: how much memory does the client have?
11:15
<vmlintu>
I haven't run 9.10 in production so I cannot say much about its quirks
11:17
<thunsucker>
lipinski: is it all your clients or just a few? if it's more than 1 how much memory does the server have and how many clients you running
11:17
i have an issue right now at one of my installs, the server doesn't have enough memory (i'm guessing) because sound is choppy on when using the rdesktop script
11:17
i connect from a ubuntu laptop to the same terminal servers and all is well
11:18
but if less than 5 clients are on, there are no sound issues
11:19
<Gadi>
thunsucker: rdesktop from a launcher on the linux desktop or as a screen script?
11:22epaphus has joined #ltsp
11:22
<epaphus>
hello all
11:28
<komunista>
lipinski: I have one clinet with the same problem
11:29
and it seems to graphic card related
11:29
when I kill frozen GUI apps, the client works...
11:30
it has problem for example with wbar, lxsession-logout and sometime with other apps too
11:31
no messages in any log, no problem by ssh to client... only apps do not works...
11:37staffencasa has joined #ltsp
11:40emence has quit IRC
11:50
<lipinski>
The client was working fine for a long time. I had server problems, so upgraded. Server is now running an Intel i3 with a new MB and 4GB RAM. I have only 1 client.
11:51
The primary use of the client if for Firefox. If I kill Firefox process on the server, the client "unfreezes".
11:51
<alkisg>
How much ram does the client have?
11:51
<lipinski>
I think only 256MB.
11:51
<alkisg>
and, is firefox running as a localapp?
11:52
<lipinski>
no
11:52
<alkisg>
Any other localapps? 256 should be plenty for only thin client use...
11:52
<lipinski>
no localapps at all. This is a "straightforward" ltsp install.
11:52
client is a dumb as can be :)
11:52
<alkisg>
Hmmm and if you kill firefox and it unfreezes, then it shouldn't be ram related
11:53
<lipinski>
alkisg: I rebuild the image and that's how I fixed the eth problem I was having the other evening (when you were helping me)..
11:53
Now, client runs great - except for this annoying hang.
11:53mikeshultz has joined #ltsp
11:53
<lipinski>
Let me try a different app, i.e., OpenOffice or something and see if that hangs.
11:54sahil has joined #ltsp
11:54
<sahil>
After adding local firefox on ubuntu 9.10 and doing the thin-client nat setup, my clients will boot and display the login manager but I am unable to login, what gives?
11:55
<lipinski>
It's almost like it's causing the entire desktop on the client to hang. mouse still responds, but I can't click on anything.
11:56
<alkisg>
sahil: try `sudo ltsp-update-sshkeys && sudo ltsp-update-image`
11:56
<sahil>
thanks alksig
11:56Faithful has quit IRC
12:00
<lipinski>
I never looking into LTSP processes before:
12:00
7028 7027 0 08:16 pts/0 00:00:00 bash -c echo LTSPROCKS; /bin/sh -
12:00
Nice :)
12:02sahil has quit IRC
12:13Selveste1___ has joined #ltsp
12:14Selveste1__ has quit IRC
12:18GodFather has joined #ltsp
12:20
<komunista>
lipinski: I have 15 the same clients and only one go to this problem
12:21
<lipinski>
komunista: odd. I'm trying a different Application besides firefox now. Next step would be to use sshd and see if I can tell what's going on on the client itself - maybe a stray process or something...
12:22
<johnny>
alkisg, ever heard of anything like this in karmic? try to play a sound and the volume just starts lowering itself until it is completely quiet?
12:22
it happens with flash player, exaile, and mplayer
12:22
or anywhere even..
12:22
not just karmic :)
12:22
<alkisg>
nah, never
12:23
does pulseaudio auto lower the volume on overdrive?
12:23
<johnny>
i have no idea
12:23
i have yet to see an overdrive setting :)
12:24
<alkisg>
Karmic allows you to overdrive your speakers... send more than 100% to them
12:24
(in gnome-mixer how's that applet called)\
12:26
<johnny>
gnome-mixer ? or gnome-alsamixer ?
12:26
<komunista>
lipinski: I find no solution :-(
12:27
I have dropbear in client's chroot, but when it freeze, I see nothing wrong on it...
12:27
<alkisg>
johnny: gnome-volume-control
12:27ogra_cmpc has quit IRC
12:28
<johnny>
guess that doesn't work over ssh -X :)
12:28
lol
12:30
hmm.. i'm still getting freezes on my fat client setup
12:30ogra_cmpc has joined #ltsp
12:30
<johnny>
even after nbd swap seems to be on
12:30
it shows swap on the terminal
12:30
but it doesn't seem to get used
12:31
<alkisg>
swapping is broken in karmic
12:31
It was fixed 1-2 months ago
12:31
<johnny>
broken in what way
12:31
i think i had fixed it
12:31
by upgrading to stgraber-ppa
12:32
some swap shows up when i run top on the fat client terminal
12:32
<alkisg>
Is that compcache?
12:32slidesinger has quit IRC
12:33
<alkisg>
But if you upgraded AND updated the initramfs, yeah, it should be fixed
12:33
<johnny>
hmm.. not sure
12:33
updated the initramfs how?
12:33
i didn't manually update the initramfs
12:34
<alkisg>
sudo chroot /opt/ltsp/i386 update-initramfs -u && sudo ltsp-update-kernels
12:35
<johnny>
ah.. and that doesn't need the image updated.. because the kernel is already gotten
12:36
<alkisg>
right
12:36
<johnny>
i confused myself for a second
12:36
the problem with the sound just started happening
12:36
i see no reason why..
12:36
none of the sliders move
12:36
in any of the volume control apps
12:36
i think it might be the amp itself.. altho that would be weird
12:37
we have it hooked up to 1/8 inch jack => rca y cable
12:37
<alkisg>
Well you know who's the sound expert here... you should ask him :)
12:53GodFather has quit IRC
12:59highvoltage has quit IRC
13:05mischko has quit IRC
13:05GodFather has joined #ltsp
13:09jammcq has joined #ltsp
13:09
<jammcq>
hey friends
13:21GodFather has quit IRC
13:33Lns has joined #ltsp
13:34GodFather has joined #ltsp
13:35rjune has joined #ltsp
13:36C_Tek has joined #ltsp
13:37highvoltage has joined #ltsp
13:39asmok has joined #ltsp
13:39
<asmok>
goof evening
13:39
<Lns>
hi asmok
13:39
<asmok>
ltsp-cluster works just fine in karmic
13:40
but in lucid ltsp-cluster-control admin page is empty
13:40
here is bug report: https://bugs.launchpad.net/ltsp-cluster/+bug/563263
13:41
any fix, if it is php parse problem?
13:41
lns: hi!
13:41
<Lns>
Gadi: ^^^ You are being summoned ;)
13:42
err wait...hahhaa
13:42
not Gadi, but stgraber
13:42
gadi, graber, potato, ...
13:43lipinski has left #ltsp
13:44
<asmok>
I did a workshop few days ago about ltsp-cluster/karmic - sorry for finnish, once again, but pics are universal language ;-) http://blog.ubuntu-fi.org/2010/nurmon-kouluihin-ltsp-klusteri/
13:47
anyone played with ltsp-cluster in lucid?
13:47
<alkisg>
cyberorg had the same problem in 6 Oct 2009 (with the T_GOTO syntax error), maybe he found a solution for it?
13:47GodFather has quit IRC
13:48
<asmok>
alkisg: bug report about that?
13:49
<alkisg>
I don't think so... you can see the ltsp logs though (see the topic for the link)
13:49
<asmok>
I'll try to find
13:52
There is no archive for 2009 or 2008, just 2007, 2006?
13:52
http://www.nubae.com/logs/archived/
13:54
<alkisg>
asmok: http://www.nubae.com/logs/ltsp20091006_pg2.html
13:54
<asmok>
I wonder how mess it is if I just copy whole ltsp-cluster-conrol php dir from karmic to the lucid?
13:59
I wonder why this bug is back when karmic is just ok... only stephanie can handle this, i think or someone from revolution linux...
13:59GodFather has joined #ltsp
14:01
<asmok>
stephanie marco is great singer, stephane graber can handle this one :-)
14:02
let's leave that for stephane, he will read that bug report
14:14
<stgraber>
asmok: we didn't update the package in lucid at all so installing karmic's won't work
14:15
I'm guessing that the control center simply doesn't work with 5.3
14:16
<asmok>
so it's better stick with karmic?
14:17
<komunista>
vagrantc: thanks for pointing to lxsession with thin client shutdown, it is very nice function ;-)
14:17
<stgraber>
asmok: http://pastebin.com/JKRFiyW6
14:18Alex227 has joined #ltsp
14:18
<stgraber>
asmok: can you try applying that patch to /usr/share/ltsp-cluster-control/
14:18
<Alex227>
hallo
14:18
<stgraber>
asmok: if it works, I'll upload that to lucid
14:19Alex227 has left #ltsp
14:19staffencasa has quit IRC
14:20
<vagrantc>
alkisg: did ubuntu get the patch into gnome-session to support LTSP logouts?
14:20
er, LTSP shutdown/reboot
14:20
<alkisg>
vagrantc: nope :(
14:20
They thought it was too much of a hack
14:20
<asmok>
I'll try that, first I'll have to remember how to patch, it's really been some time when dealing patch file ;-) be patient, i start now ;-)
14:20
<vagrantc>
alkisg: the whole concept?
14:20
<alkisg>
We need to tell sbalneav to get it upstream to gnome :)
14:21
<johnny>
i don't think that's gonna happen until you can pass it down via dbus to the client
14:21
<alkisg>
vagrantc: I'm not sure if it was the xprop setting that bothered them or the code path where the patch was applied, the maintainer didn't have much time to talk so...
14:21
<johnny>
it always always be hacky trying to fix it in that way
14:21
<alkisg>
johnny: do you think it's easier to send upstream dbus patches than gnome-session patches?
14:21
<stgraber>
asmok: cd /usr/share/ltsp-cluster-control && sudo patch -p0 < path/to/the/patch
14:25
<asmok>
ok
14:25
<johnny>
alkisg, i don't think the solution would be acceptable upstream is all
14:26
by gnome folks
14:26
it's too specific to one situation
14:27
<atkuepker>
grr. more dbus-daemon. I'd be happier if that thing didn't lock up so frequently
14:27
<alkisg>
johnny: so then what do you propose? To maintain an ltsp-specific branch of dbus?
14:28GodFather has quit IRC
14:28
<johnny>
alkisg,
14:28
no..
14:29
it just seems more likely that a dbus proxy or router would be more generic and useful for ohter things
14:29
unlike the specific hacky way of logging out
14:30
<asmok>
stgraber: you are hero of the day ;-)
14:30
<stgraber>
asmok: it works correctly ?
14:30
<asmok>
atching file Admin/index.php
14:30
patching file Admin/util/functions.php
14:30
patching file Admin/util/setup.php
14:30
patch unexpectedly ends in middle of line
14:30
Hunk #2 succeeded at 198 with fuzz 2.
14:30
yes
14:30
<stgraber>
good, releasing a new version + uploading to lucid then
14:31
released (2.0.2)
14:31
<asmok>
great!
14:34staffencasa has joined #ltsp
14:35
<asmok>
there are still messages in apache2's error.log, but admin page works now, this kind of
14:36
<alkisg>
vagrantc: one cleaner thing to propose is to have the applet reboot/shutdown entries hidden when the CK session is not active (e.g. in ltsp and nx sessions). That wouldn't be hackish at all. We'd lose the ability to shutdown from the menus, but it'd at least make sense.
14:37
<vagrantc>
alkisg: i thought that was already implemented in older versions?
14:37
<alkisg>
vagrantc: yes there was a patch in fusa for that, but fusa got dropped and the patch wasn't transfered to the new indicator applet
14:37
<asmok>
http://ltsp.pastebin.com/ixzkUTkj
14:38
<alkisg>
vagrantc: but this wouldn't be an ltsp - specific patch; it would check CK instead
14:38
<stgraber>
asmok: uploaded to lucid
14:38
asmok: seems like php 5.3 is quite verbose ;)
14:38
I won't spend too much time making it happy as we are simply rewritting everything at the moment ...
14:39
<asmok>
good to know
14:39
i finish now my lucid setup and them boot first test tc
14:41GodFather has joined #ltsp
14:52
<asmok>
stgraber: HP Mini 2133 as a TC: http://ltsp.pastebin.com/WE1v7rHi
14:53
<stgraber>
great !
14:53
<asmok>
lucid works great now, only one app server ;-D
14:53
<stgraber>
and you got that super slick and fast flickerless boot ?
14:53
<asmok>
yes
14:54GodFather has quit IRC
14:55
<thunsucker>
stgraber: wow that sounds nice
14:55
<stgraber>
thunsucker: here it's basically the pxelinux loading sequence, then a splash for 10s without any flicker/black screen, then directly the login prompt
14:56pmatulis has quit IRC
14:57
<asmok>
i have lots of t5125/t5135, i hope i got them to work too, there is something bad after login, but now i can test them with lucid - t5125 drops after login to the login screen again, let's see if i find something. they work with hardy just fine...
14:58
i now boot t5125...
14:59
<stgraber>
the oldest HP I have here is a 5735
15:00
and I have some 5745
15:03
<vmlintu>
I noticed the same problem yesterday with lucid - after login my via based thin client just went back to login screen
15:05
After I set LDM_DIRECTX=false and X_COLOR_DEPTH=16, it started working ok, so I didn't investigate it further
15:05
<Gadi>
have you disabled compiz?
15:05
<vmlintu>
Removing compiz didn't help with my box
15:05
It's some via based box with 1GHz CPU and 512Mb of memory
15:09
<asmok>
vmlintu: i try your setup too
15:09
<vmlintu>
LDM_DIRECTX=true
15:09
sorry, my mind is mixed up
15:10
LDM_DIRECTX=Y and X_COLOR_DEPTH=16 were the working ones
15:10
<asmok>
ok
15:11C_Tek has quit IRC
15:22
<alkisg>
asmok: for some clients, disabling compiz helps:
15:22
!compiz
15:22
<ltspbot>
alkisg: "compiz" :: if compiz is giving you problems, one way to disable it for all users is: sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/session/required_components/windowmanager metacity
15:23
<asmok>
yes i did it, it is in my/stephane howto ;-) wai a minute, some good news coming ;-)
15:24
t5125 (september 2006 model) works now! http://ltsp.pastebin.com/nsRqfq8t
15:24staffencasa has quit IRC
15:26
<Gadi>
asmok: these are all via chipsets?
15:26
<asmok>
it is awful slow to boot, but then no problem. I once again own a beer to stephane and veli-matti ;-) I think we can do something for that in Tampere ;-D right ;-)
15:26
<Gadi>
(using openchrome driver)?
15:28
<vmlintu>
I was using the default driver for the box and it has been openchrome at least until now. I actually didn't even check that yesterday..
15:29
<asmok>
here is something from ltsp-cluster check: http://ltsp.pastebin.com/nNUF3ufq
15:30
<Gadi>
yeah, I find the openchrome driver to be lacking in the "sane defaults" department
15:30
:)
15:31Selveste1___ has quit IRC
15:32
<vmlintu>
The same box started using the internal speaker for audio now..
15:33
<asmok>
this is what ltsp-cluster says before loginvideo: apollo cle266 integrated castlerock graphics (rev 03)
15:33staffencasa has joined #ltsp
15:33
<asmok>
yes sound work for t5125
15:34ogra_cmpc has quit IRC
15:37
<asmok>
this was really good session, now i really can start to plan how to turn my hardy dhcp-failover setup to the ltsp-cluster setup, i got over 100 t5125/t5135 at my daughter's school. thank you everybody and good night!
15:38asmok has left #ltsp
15:46Selveste1___ has joined #ltsp
15:47ogra_cmpc has joined #ltsp
16:02hersonls has quit IRC
16:20thunsucker has left #ltsp
16:26
<vagrantc>
hrm. gpxe and recent versions of qemu don't play well together...
16:29
<Gadi>
tho, they are prolly worth a lot of points in the game of Scrabble
16:29
<vagrantc>
true enough!
16:29
<Gadi>
see, now isn't that all that matters?
16:31
<vagrantc>
hrm.
16:31
seems like ltsp-update-sshkeys is creating an empty file for me... but when i re-run it, it works fine.
16:32
<Gadi>
ssh running the first time?
16:32
<vagrantc>
running?
16:32
ah, yes. sshd is running.
16:32
<Gadi>
not with legs
16:32
odd
16:33
<vagrantc>
Gadi: when you re-wrote it, does it not use the local files at all? i.e. it always scans the network?
16:33
<Gadi>
I believe so
16:33* Gadi can be so presumptuous
16:33
<Gadi>
lets have a look-see
16:33
<vagrantc>
reading directly from the files themselves is a lot safer...
16:34
also, doesn't require the local machine to have sshd running
16:34
also got some reports that it was taking an inordinate amount of time at boot
16:34
<Gadi>
ok ok ok
16:34
geesh
16:34
:)
16:34
<vagrantc>
heh
16:35
<Gadi>
is it too late to fix? is the party over?
16:35
:)
16:35
<vagrantc>
party?
16:35* vagrantc plays a kazoo
16:35
<Gadi>
what? we're not at a party?
16:35* Gadi puts his pants back on
16:36
<Lns>
....wow.
16:40
that might be a good slogan... "SSH: Don't get caught with your pants down."
16:47
<vagrantc>
hrm.
16:48
ltspfs seems completely broken in testing :(
16:49
ah, false alarm... i haven't tested these other files yet...
16:54
<Gadi>
vagrantc: fixed, commited, pushed
16:54
please test
16:55
oh, and test while singing "pants on the ground" to Lns
16:55
<Lns>
lol
16:56
if you could guage the skills of an open source programmer to the personality quirks demonstrated on IRC...hahaha
16:56
gadi, you'd be a millionaire
16:58
<Gadi>
hehe
16:58
ciao, gang
16:58Gadi has left #ltsp
16:59
<vagrantc>
just like gadi to fix something and disappear :)
17:01
<Lns>
hehe
17:01
at least he took his pants with him.
17:02
<highvoltage>
vagrantc: are you going to debconf?
17:03
<vagrantc>
seems to work
17:03
highvoltage: yes, you?
17:03
highvoltage: we met in sevilla years back, no?
17:03
<highvoltage>
vagrantc: yep, looking forward to seeing some familiar people and meeting new debian folk
17:03
vagrantc: yes, indeed
17:04
vagrantc: you are probably more memorable than I am, I thought you were interesting :)
17:07
<vagrantc>
i'm trying to concince some LTSP folks to crash debconf to do some ltsp hacking
17:07
<vmlintu>
what's next on the line for ltsp?
17:07
<highvoltage>
that would be great. stgraber is also going
17:09komunista has quit IRC
17:09
<vagrantc>
stgraber: ah, didn't know you were going! :)
17:35Lns has quit IRC
17:36Lns has joined #ltsp
17:40Lns has quit IRC
17:43jammcq has quit IRC
17:48alkisg has quit IRC
17:59bobby_C has quit IRC
18:00mikeshultz has quit IRC
18:07mischko has joined #ltsp
18:10Faithful has joined #ltsp
18:12
<stgraber>
vagrantc: it's only 5-6 hours away from here ;)
18:14
doh, would have liked that revert two weeks before ... now I'm starting sshd in d-i just to have ssh-keyscan do its magic :)
18:14
<vagrantc>
egads
18:14
<stgraber>
will be great to drop that in Maverick
18:16
<vagrantc>
stgraber: i'm sure you'e busy as all get-out right now, but was wondering if you might get a chance to update the ltsp-trunk/fr.po soonish?
18:25
<stgraber>
vagrantc: done
18:33
<vagrantc>
stgraber: thanks :)
18:34
i know folks have tried in the past, but i wonder if we could ever get a signle .po file for each language in ldm...
18:35litlebuda has joined #ltsp
18:35mischko has quit IRC
18:38NeonLich1 has quit IRC
18:44Faithful has quit IRC
18:46staffencasa has quit IRC
18:52NeonLicht has joined #ltsp
19:01egghead has joined #ltsp
19:04
<egghead>
running ubuntu 9.10, using ltsp on a 64bit machine, tring to boot i386 clients (using usb drive) but get i think the i386 client trys to load in from /opt/ltsp/images/amd64 instead of the /opt/ltsp/images/i386 image, any one know if there is a config file to change the boot image for different clients?
19:04epaphus has quit IRC
19:14
<johnny>
egghead, do you have both kinds of clients egghead ?
19:14
or just i386?
19:16
<egghead>
johnny, yes, both
19:17
is there a config file for ltsp that points to /opt/ltsp/images?
19:18
or maybe for tfpboot?
19:18rjune has quit IRC
19:19
<egghead>
i think problem is i boot (from usb drive) i386 kernel and then it trys to load the amd64 image
19:19
but cant figure out how to change the boot image dir for i386 clients
19:23
<johnny>
first you have to install the image
19:23
ltsp-build-client --arch i386
19:23
<egghead>
i did that
19:24rjune has joined #ltsp
19:43robbie_ has joined #ltsp
19:52waldo323 has joined #ltsp
20:10Faithful has joined #ltsp
20:12slidesinger has joined #ltsp
20:20
<Ryan52>
vagrantc: the result of g_strconcat should be freed.
20:21
so do this instead:
20:21
<vagrantc>
Ryan52: and you say you don't contribute much anymore :)
20:21
<Ryan52>
gchar * foo = g_strconcat("<b>", _("Verifying password. Please wait."), "</b>", NULL);
20:21
set_message(foo)
20:21
g_free(foo);
20:21
// I missed a semi colon on the set_message line
20:22
vagrantc: hah.
20:23
<vagrantc>
Ryan52: gchar on the same line? or with the other gchar at the top of the function?
20:23
<johnny>
uggh :(
20:23
still having sound problems @ my store
20:23
<Ryan52>
no, guess not. do it like sec.
20:23
gchar * foo;
20:23
<johnny>
the volume starts at a normal level
20:24
<Ryan52>
foo = g_strconcat(.........);
20:24epaphus has joined #ltsp
20:24
<johnny>
and then just gets quieter until tis gone
20:24
<Ryan52>
s/sec/this/
20:24* Ryan52 is being rushed to leave by his dad...so cya.
20:26egghead has left #ltsp
20:51robbie_ has quit IRC
21:07epaphus has quit IRC
21:09waldo323 has quit IRC
21:11pem725 has quit IRC
21:35try2free has joined #ltsp
21:53try2free has quit IRC
21:54
<vagrantc>
hmmm... the LDM_LOGIN_TIMEOUT doesn't seem to be working...
21:58
ah, it apparently needs to work in conjunction with LDM_GUESTLOGIN
21:59* vagrantc is playing with ldm to randomly select a supported language to display and autologin/autologout
22:02
<vagrantc>
seems to be biased towards polish.
22:03
it would be tricky to implement... but would be cool if the language selection could also change the greeter language
22:08
<stgraber>
sounds tricky to implement (on the fly gettext language change)
22:09
<vagrantc>
a fairly brutal way would be to re-exec the greeter
22:10
but GDM changes the language when you select a different langauge, no?
22:13
well, ldm has decent support for 17 languages :)
22:17
i haven't done a very good job of asking folks to translate the rc.d and ltsp-cluster-info bits... the tools i use to send out the translations don't support multiple po files (as far as i know), and it would be confusing to send out multiple translation requests for a single package...
22:18
<Ryan52>
vagrantc: that sounds like a fun project.
22:19
<vagrantc>
Ryan52: oh, sparked your interest, have i? :)
22:19
Ryan52: changing the ldm UI to a new locale if the user selects a new locale?
22:21
ideally checking if it's a valid locale on the local system...
22:21
<Ryan52>
why?
22:21
doesn't hurt to try it anyway...it'll just fall back to the original string.
22:22
hm...one problem, tho. some of the text is translated on the server side by the ssh daemon.
22:23
<vagrantc>
Ryan52: none of that is translated anymore
22:23
any messages are just relayed through
22:23
<Ryan52>
exactly.
22:23
they are translated if the server's default language is a different language.
22:23
because then sshd would translate it.
22:24* vagrantc doesn't see how that matters
22:24
<vagrantc>
Ryan52: regarding the fallback, if the default locale != C and they try to switch to an unsupported locale, then it will fall back to C ...
22:25
won't it?
22:25
<Ryan52>
if the servers language is spanish, and the ldm user selects french, half the interface would be in french and half in spanish.
22:25
and if the ldm translation for french isn't complete, some of the interface may even be english.
22:26
<vagrantc>
incomplete translations aren't anything we can do anything special about
22:26
Ryan52: but the server/thin-client language differences are already handled... it sets the locale variables when logging in via ssh...
22:27
<Ryan52>
that doesn't affect the strings relayed from sshd, tho.
22:27
does it?
22:27
<vagrantc>
no worse off than it is now.
22:27
in any case :)
22:27
<Ryan52>
I guess.
22:27
<vagrantc>
i'm not sure it ignores the locale variables...
22:29
currently, we can set the locale for the LDM UI with standard environment variables LANG, LC_ALL, etc. and LDM_LANGUAGE sets the user's locale for the logged in session, or alternately by selecting the language from the menu.,
22:30
but if the menu selection could both set the LDM UI and the user's soon-to-be logged in session, that would be nice.
22:32* vagrantc wonders how GDM or KDM do it
22:33
<Ryan52>
it's really easy.
22:33
<vagrantc>
well then... :)
22:34
<Ryan52>
you just need to change the locale and set all of the strings again.
22:34
changing the locale is simple, generate_locale_list.py does it for example.
22:43try2free has joined #ltsp
22:44
<Ryan52>
hm, GDM just restarts.
22:44
well that's kind of cheating. :P
22:49Faithful has quit IRC
22:55alkisg has joined #ltsp
23:01rjune has quit IRC
23:02
<alkisg>
stgraber: turns out that we already have the latest udhcp version in Lucid, it's embedded in busybox!
23:03
So we can actually drop the udhcpc dependency, stop installing udhcpc, and just use busybox udhcpc -C
23:03rjune has joined #ltsp
23:04try2free has left #ltsp
23:07Faithful has joined #ltsp
23:09rjune has quit IRC
23:15
<alkisg>
Dah no there are 2 busybox versions, busybox-static has it, while busybox-initramfs doesn't. So maybe we should file a bug against busybox-initramfs and ask that they include udhcpc in their Makefile.
23:16epaphus has joined #ltsp
23:21rjune has joined #ltsp
23:24alkisg has quit IRC
23:53try2free has joined #ltsp
23:54vagrantc has quit IRC