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


Channel log from 11 June 2011   (all times are UTC)

00:01alexqwesa (~alex@alexo-veto.broker.freenet6.net) joined #ltsp.
00:32Gnoze5 (~Gnoze5@190.115.103.87.rev.vodafone.pt) left irc: Read error: Connection reset by peer
00:33Gnoze5 (~Gnoze5@190.115.103.87.rev.vodafone.pt) joined #ltsp.
01:09bobby_C (~bobby@188.20.161.210) joined #ltsp.
01:15loathing (~khudson@internal-nat.djnetworks.net) left irc: Ping timeout: 260 seconds
01:16loathing (~khudson@internal-nat.djnetworks.net) joined #ltsp.
01:29bobby_C (~bobby@188.20.161.210) left irc: Ping timeout: 252 seconds
03:01
<Gnoze5>
cant get pt_PT working on ldm
03:03
hm
03:03
afterall its just the login screen
03:03
annoying
03:48
<alkisg>
Gnoze5: did you install the langpack in the chroot?
03:55
<Gnoze5>
yep
03:55
its working now
03:55
well
03:55
working everything
03:55
except the login screen
03:56
alkisg still wondering how to use acl for the context
04:10
now im trying to figure out how to share a printer tha is connected locally to a client
04:13
<alkisg>
For the login screen, try setting LANG in lts.conf
04:13
<Gnoze5>
okidoki
04:13
alkisg is it easy to get a local printer shared to other clients?
04:13
<alkisg>
For the printer, man lts.conf => PRINTER_0_DEVICE etc
04:13
For the acl, ...what? :)
04:13
<Gnoze5>
the acl its solved :P
04:14
does the user have to be logged in for the printer to still be shared or does the client just to be turned on?
04:14
<alkisg>
Just turned on (afaik)
04:30
<Gnoze5>
well it was hard but its working well now
04:31
and we havent done any optimization
04:34
<alkisg>
LDM_DIRECTX=True is the most vital one, if your security allows it
04:34
The network module problem was solved in more recent initramfs-tools versions so it shouldn't trouble us in the future
04:35
And I hope something can be done with that silly compiz problem...
04:39
<Gnoze5>
i had 2 clients having bad boots every so often
04:39
disabling the ndb proxy seemed to do the trick
04:39
in this case i do have ldm_directx true
04:43alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
05:13
<Gnoze5>
argh
05:13
anyone around to help me with a local usb printer?
05:16
<muppis>
Gnoze5, I can't rely my memory, but I can try. What's the deal?
05:19
<Gnoze5>
im trying to get a printer connected to a client via usb
05:19
to work on that client
05:20
and to be shared
05:20
<muppis>
Do you have root access to client?
05:20
<Gnoze5>
i havent set it already
05:20
but i can
05:20
<muppis>
(I'm lazy to read backlog with N900 right now)
05:21
Get it and ook do have jetpipe running
05:21
*look
05:22
<Gnoze5>
rebuilding the img
05:23
<muppis>
At same time command getltscfg -a and check does it give same as set.
05:24
My commands can be mistyped because I don't now have access any client to check proper syntax.
05:24
<Gnoze5>
yep
05:25
jetpipe is running
05:25
and
05:25
<muppis>
Looks good. Then which port it is listening? Should be 9100.
05:25
<Gnoze5>
its on 9600
05:26
and the getltscfg does have what i set
05:26
device_0_printer dev/lp0
05:26
<muppis>
usb printer?
05:26
<Gnoze5>
yep
05:27
<muppis>
Then it should be /dev/usblp0 or /dev/usb/lp0
05:27
What you have set in lts.conf?
05:28
<Gnoze5>
just that
05:28
localdev true
05:28
do i need to force the port?
05:28
i have a printer_0_device under the mac address of the client where the printer is
05:28
<muppis>
No need to.
05:28
<Gnoze5>
and localdev true for default
05:29
<muppis>
Hold a sec..
05:30
<Gnoze5>
oki
05:32
<muppis>
Put printer_0_type = u in lts.conf
05:33
<Gnoze5>
ok
05:33
btw
05:33
its on 9100
05:33
now
05:35
<muppis>
Then it can be found.
05:35
<Gnoze5>
ok
05:35
by who?
05:35
the client
05:35
or any of the clients?
05:35
<muppis>
You should someway get fixed address for that client to ease printer usage afterwards.
05:36
<Gnoze5>
hm I see
05:36
so i should set it as a newtork printer?
05:38
<muppis>
Yes.
05:42
<Gnoze5>
ok its working
05:42
awesome
05:42
thank you
05:43
whats the smartest way to set it up to all user accounts as default?
05:45Trixboxer (~Trixboxer@office.supportdepartment.net) joined #ltsp.
05:51
<Gnoze5>
ok
05:52
i answered myself
05:52
muppis thanks for the help :P
05:52
bbs
05:52Gnoze5 (~Gnoze5@190.115.103.87.rev.vodafone.pt) left irc:
06:22mikkel (~mikkel@80-71-132-15.u.parknet.dk) joined #ltsp.
06:49alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
07:29katan (71acf095@gateway/web/freenode/ip.113.172.240.149) joined #ltsp.
07:36katan (71acf095@gateway/web/freenode/ip.113.172.240.149) left irc: Ping timeout: 252 seconds
07:41bobby_C (~bobby@188.20.161.210) joined #ltsp.
07:52chokesmaster (~chokesmas@bas7-sherbrooke40-2925312439.dsl.bell.ca) joined #ltsp.
07:52Chokesmaster_ (~chokesmas@bas7-sherbrooke40-2925312304.dsl.bell.ca) left irc: Read error: Operation timed out
08:23alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
08:39drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) joined #ltsp.
08:51drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) left irc: Ping timeout: 255 seconds
08:53drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) joined #ltsp.
09:07drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) left irc: Ping timeout: 255 seconds
09:11MorningSon (~MorningSo@cpe-70-117-27-48.satx.res.rr.com) left irc: Quit: WeeChat 0.3.0
09:23JonathasHortense (~jonathas@201-74-206-102-am.cpe.vivax.com.br) joined #ltsp.
09:54JonathasHortense (~jonathas@201-74-206-102-am.cpe.vivax.com.br) left irc: Quit: leaving
10:14NeonLicht (~NeonLicht@darwin.ugr.es) left irc: Ping timeout: 240 seconds
11:35[GuS] (~MysT@unaffiliated/gus/x-663402) joined #ltsp.
12:17sunscreen (~sunscreen@unaffiliated/factor45) joined #ltsp.
12:17
<sunscreen>
helloo
12:21
hey i have a 64bit debian sqeeze (6.0) machine, with ltsp from packages .. i setup with lts-build-client -arch i386, and set lts.conf so its SCREEN_01 = rdesktop -f -a 16 <ip of server>, but i just get a black screen for that tty and mouse icon. ..
12:23
i had this issue with my home test setup .. but i made it go away ..some how ..i am wondering if you know what the "some how" was
12:23
i can rdesktop from gnome desktop that works fine
12:23
but over the land/lts/pxe i get those symptoms
12:25
LDM also works and logs in ok .. so my wild guess this a windows term server issue.. but what could it be
12:26
how can i find out what version of ltsp i am using
12:39
http://www.mail-archive.com/ltsp-discuss@lists.sourceforge.net/msg39217.htm
12:39
http://www.petri.co.il/forums/showthread.php?t=13740 .
12:39
.. http://support.microsoft.com/kb/555840
12:41
http://ask.metafilter.com/69316/Why-do-I-get-a-black-screen-when-using-Remote-Desktop-Connection
12:43
Bitmap caching - or MTU .. I just cant see it with out of the box network settings
12:44
Bitmap caching or resolution/bit depth not high enough on the client [yes/no]
12:48alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
12:52
<alkisg>
sunscreen: remove all SCREENs from lts.conf and logon to gnome normally on the thin client. Then run: ltsp-localapps xterm. And then try the rdesktop command from that local terminal.
12:52
<sunscreen>
aaah!
12:52
<alkisg>
(for troubleshooting)
12:52
<sunscreen>
see i was trying to doing SCREEN_01=xterm
12:52
hehe
12:52
<alkisg>
Don't use SCREEN_01 on debian/ubuntu, it's reserved for the boot messages
12:53
Use >= screen_02
12:53
<sunscreen>
double doh!
12:54
<alkisg>
There's no xterm screen script. Hmm it would be handy to have one, though :)
12:55
<sunscreen>
yup... tnx for the enlightenment on that tho :)
12:55Nick change: LoveStor- -> LoveStorm
13:00
<sunscreen>
i have to wait till tomorrow now to progress
13:02
another thing is
13:02
can you turn off fb console on the bootup
13:03
its kinda outputs slightly corrupted
13:03
<alkisg>
Not sure what debian uses for thin client boot screen, wait for someone else
13:04
<sunscreen>
k
13:04
i think i saw some where you can pass the kernel boot options
13:06
<alkisg>
/var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
13:07
<sunscreen>
so it was a case of pebkac
13:08
lots of the lts blackscreen rdesktop threads all have a re-occurring theme
13:08
SCREEN_01
13:08
and debian/ubuntu
13:11vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) joined #ltsp.
13:27Trixboxer (~Trixboxer@office.supportdepartment.net) left irc: Quit: "Achievement is not the end, its the beginning of new journey !!!"
13:38alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
14:02
<sunscreen>
http://ubuntuforums.org/showthread.php?t=935416 kinda neat but primitive method to load balance
14:04
also opens the door for a more sophisticated approach as lykwydchykyn mentions
14:18
i also feeling to try and setup samba on the client to share its local cdrom back to the virtual machine the they end up with rdesktop
14:18
that would be kinda cool lol
14:18
has any one got sound working btw and how do you do it?
14:20
heheh in the windows machine you would end up having cd drive shares for every client i wonder if you could make them visible only per user in windows some how
14:21
<muppis>
sunscreen, IIRC there is an option in rdesktop to connect local dvices to remote.
14:23drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) joined #ltsp.
14:24
<sunscreen>
ok great ;)
14:37
so in theory: rdesktop -a 32 -f -x lan -r sound:local 192.168.1.20 is my ideal command then
14:37
er
14:38
rdesktop -a 32 -f -x lan -r sound:local -r disk:cdrom=/mnt/cdrom 192.168.1.20
14:41
sorry i am so full of questions today ;) .. but i am now wondering how rdesktop is handling multicore cpu's
14:41
<muppis>
Locally?
14:43
<sunscreen>
well i don't see any mention in the options of rdesktop but it would be kinda cool to devide the screen by the number of cores and have each core drawing a different area of the display
14:45
<muppis>
I think GPU usage could be better.
14:47
Because singlecore machine can have good gpu.
14:47
<sunscreen>
well with gpu's blowing away cpu's these days your right... i dont thing the dc gpu things is still in full swing any more seems like they gave up may be they just don't need with the present line ups
14:53
welp
14:53
i going to try and trigger the blackscreen of death on my system
15:19sarthor (~sarthor@unaffiliated/sarthor) joined #ltsp.
15:20
<sarthor>
Hi, i isntalled Ltsp server, and my laptop booted from that server, Now my laptop is asking for username and password, how to add user name and password in ltsp server machine for the client
15:24
<sunscreen>
adduser
15:27
ltsp-update-image runs like shit of a shovel on our raid1 array
15:29
<muppis>
sarthor, client usess same account as server does.
15:29
You're logging into server, not in client. It is just screen, mouse and kb.
15:30
<sarthor>
muppis, i added adduser toshiba and then gave password 123456, but i am not able to login from the client, Even i restarted the client machine too
15:31
<muppis>
Can you log with those to server with ssh?
15:31
<sarthor>
let me check muppis a minute please
15:33
muppis, yes i can ssh using that user
15:33
but cant login from client laptop as a thin client to my ltsp server
15:38
<sunscreen>
sarthor, sounds kinda screwy even to me, I would try and rebuild the client image
15:40
<sarthor>
sunscreen, I am very much new to this stuff, that was my 1st try, i really don't go back, how to rebuild client image,
15:40
sunscreen, sudo ltsp-build-client
15:40
NOTE: Root directory /opt/ltsp/i386 already exists, this will lead to problems, please remove it before trying again. Exiting.
15:40
error: LTSP client installation ended abnormally
15:41
<sunscreen>
no, try: ltsp-update-sshkeys ; ltsp-update-kernel; ltsp-update-image
15:41
<sarthor>
Ahh. i started ltsp-update-image, is it ok? or i have to go with your sequence?
15:43
sunscreen, after updating these, how to restart ltsp ? or i will need to restart the machine?
15:44
<sunscreen>
no you dont need to restart anything
15:44
you can do them in what ever order really i think
15:44
but sshkeys might be the important one did you do it previously?
15:45
<sarthor>
yes
15:45
done all, booting again client
15:45
sunscreen, still i can not login, the login screen came back.
15:46
<sunscreen>
pastebin your lts.conf
15:46
<sarthor>
ok
15:50
sunscreen, i can not find lts.conf, where is that file,
15:50
i using ubuntu natty 11.04 desktop
15:51
<sunscreen>
/opt/ltsp/i386
15:53
<sarthor>
sunscreen, in /opt/ltsp/i386/etc there is lts.conf i pasted http://pastebin.com/m5WB3d5q
15:54
<sunscreen>
uh oh
15:55
<sarthor>
sunscreen, forgave me, just started today with this stuff.
15:55
<sunscreen>
don't worry this is the blind leading the blind :)
15:56
<sarthor>
no problem, we are not going to destroy anything, all going just for learning
15:56
<sunscreen>
well you have what i would deem to be an abnormal lts.conf
15:57
<sarthor>
hmm, i followed this http://amazai.net/forum/viewtopic.php?f=5&t=22 and all came into existance
16:00
<sunscreen>
http://pastebin.com/tdw7isUQ
16:01japerry (~japerry@drupal.org/user/45640/view) joined #ltsp.
16:01
<sunscreen>
something thing that i was reading earlier in relation to the keyboard map, just had me thinking does the password have any special characters?
16:02
<sarthor>
there are tow mac addresses? should i paste lts.conf as mine??
16:02
no special ccharacter in password
16:02
<sunscreen>
yeah those are the mac's of your thin clients
16:03
or you can just do sections like [192.168.1.123]
16:04
<sarthor>
I copied / pasted, same result
16:05
<sunscreen>
can you authenticate via ssh from localhost on the server?
16:06
<sarthor>
yes
16:07
i did toshiba@localhost and that asked for passwords, i gave password, and logged in
16:08
<sunscreen>
ok
16:08
do this then
16:09
<sarthor>
yes?
16:09
<sunscreen>
ltsp-chroot
16:09
passwd root
16:09
enter passwds
16:09
exit
16:09
then login as root on the ltsclient
16:09
then perform the ssh session
16:09
see what it has to say for itself
16:10
you need lts-update-image after that too
16:13
may be watch the sshd logs
16:15
<sarthor>
said. a new version of the iamge is available.. rebooting..
16:15
now rebooting
16:16
rebooted. but still i am no table to login, with toshiba user as well as root.
16:16
<sunscreen>
strange should be able to login as root
16:17
oh
16:17
switch to real console
16:17
on the client
16:17
<sarthor>
how??
16:17
<sunscreen>
ctrl-alt-f1
16:18
<sarthor>
ok. the bad FN key
16:18
now?
16:18
<sunscreen>
ctrl-alt-f2
16:18
<sarthor>
i am in real consol now
16:18
<sunscreen>
now you can login as root
16:18
<sarthor>
yes
16:18
i am logged in
16:20
how to login in GUI
16:20
<sunscreen>
now do the ssh session
16:21
<sarthor>
ssh to whom ? localhost?
16:21
<sunscreen>
to the server
16:21mikkel (~mikkel@80-71-132-15.u.parknet.dk) left irc: Quit: Leaving
16:22
<sarthor>
yes. i logged in to server via ssh thru the toshiba user
16:24
<sunscreen>
hmmz
16:27
<sarthor>
is there somthing next?
16:27
Coz i am not logged in to GUI
16:27
<sunscreen>
"run sudo ltsp-update-sshkeys and sudo ltsp-update-image (in this order) it should be gone then" some other guys words regarding similar problem .
16:29
not sure if it mater either i dont think it should if you just got a pure 32 bit server/clients but you could pass lts-update-image -a i386
16:30
but i am kind sure if you can login via ssh then you should be able to login into ldm
16:30
<sarthor>
Ahh. it said toshiba is not in the sudoers
16:30
when i did sudo ltsp-update-sshkeys
16:31
<sunscreen>
su root
16:32
you may do a war cry after that command
16:32
<sarthor>
su root , su - sudo none of them working
16:32
athentication failure
16:33
<sunscreen>
if you cant su root.. then well problem+problems
16:34
<sarthor>
yea i m root now
16:34
let me do that now
16:37
no brother,
16:37
restarted but still not working
16:38
again it says after ltsp-update-image that new image found
16:38
and restarted.
16:40
<sunscreen>
puzzling
16:40
i think i will go think on it in the tub for half and hour
16:42
<sarthor>
no problem. I am also reading. Thanks for the time.
16:46bobby_C (~bobby@188.20.161.210) left irc: Ping timeout: 246 seconds
16:46
<sunscreen>
just one more thing that it might be .. doubtful but could be worth a shot try: xhost +remote.machine
16:54sarthor (~sarthor@unaffiliated/sarthor) left irc: Remote host closed the connection
17:28otavio (~otavio@debian/developer/otavio) left irc: Quit: reboot into new kernel
17:42otavio (~otavio@debian/developer/otavio) joined #ltsp.
17:46leio_ (~leio@gentoo/developer/leio) joined #ltsp.
17:48leio (~leio@gentoo/developer/leio) left irc: Ping timeout: 246 seconds
18:03Guerdal82|atWork (~Guerdal82@LLagny-156-35-33-131.w193-251.abo.wanadoo.fr) left irc: Ping timeout: 268 seconds
18:22leio_ (~leio@gentoo/developer/leio) left irc: Remote host closed the connection
18:22leio (~leio@gentoo/developer/leio) joined #ltsp.
18:57[GuS] (~MysT@unaffiliated/gus/x-663402) left irc: Remote host closed the connection
19:50
<sunscreen>
is this worth doing ??
19:50
http://bootpolish.net/home_ltsp_ltspclientupgrade
19:58vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) left irc: Ping timeout: 240 seconds
20:10Guerdal82|atWork (~Guerdal82@LLagny-156-35-33-131.w193-251.abo.wanadoo.fr) joined #ltsp.
21:45chupacabra (~chupacabr@cpe-70-112-10-45.austin.res.rr.com) left irc: Ping timeout: 255 seconds
21:47chupacabra (~chupacabr@cpe-70-112-10-45.austin.res.rr.com) joined #ltsp.
21:55drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) left irc: Read error: Connection reset by peer
21:56cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Remote host closed the connection
22:22mistik1 (mistik1@unaffiliated/mistik1) left irc: Read error: Connection reset by peer
22:23mistik1 (mistik1@unaffiliated/mistik1) joined #ltsp.
23:02cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
23:56drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) joined #ltsp.
00:00--- Sun Jun 12 2011