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


Channel log from 16 January 2016   (all times are UTC)

01:02lbssousa has left IRC (lbssousa!~hermes@177.79.10.175, Ping timeout: 276 seconds)
01:29gp has joined IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net)
04:04
<gbaman>
Am I missing something? Does LTSP interfere with udev in some way? Am having weird issues where an LTSP fat client is ignoring my rules...
04:19vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
04:27
<gbaman>
vagrantc: Does LTSP mess around with udev rules by any chance? Having weird issues with a rule not firing..
04:28
<vagrantc>
gbaman: ltspfs uses udev to trigger it
04:28
<gbaman>
But that shouldn't interfere with any other udev rules, right?
04:30
The new Pi kernels come with a new module, bcm2835_gpiomem, which creates /dev/gpiomem. Permissions need to be set for it using a udev rule (owner group needs to be gpio), but with LTSP, it seems to ignore it? Only correctly applies the permissions when the module is completely unloaded then reloaded
04:32
Has had me head scratching for a number of hours (and forced me to learn about udev), so am open to any suggestions vagrantc
04:46gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Remote host closed the connection)
04:56TheProf has joined IRC (TheProf!~TheProf@cmr-208-124-154-250.cr.net.cable.rogers.com)
04:59
<vagrantc>
well, i'd respond... if you were still here
05:01
<TheProf>
Hello. I am running LTSP (edubuntu 12.04) and my thin clients have started to not work correctly. They PXE boot into a BusyBox prompt. How could I solve this please?
05:05vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
05:25adrianorg has left IRC (adrianorg!~adrianorg@177.204.159.28.dynamic.adsl.gvt.net.br, Ping timeout: 256 seconds)
05:26adrianorg has joined IRC (adrianorg!~adrianorg@177.18.171.181)
05:30TheProf has left IRC (TheProf!~TheProf@cmr-208-124-154-250.cr.net.cable.rogers.com, Ping timeout: 256 seconds)
05:33TheProf has joined IRC (TheProf!~TheProf@cmr-208-124-154-250.cr.net.cable.rogers.com)
05:34vmlintu has joined IRC (vmlintu!~vmlintu@a88-112-3-40.elisa-laajakaista.fi)
05:35TheProf has left IRC (TheProf!~TheProf@cmr-208-124-154-250.cr.net.cable.rogers.com, Client Quit)
05:47gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
05:59gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Ping timeout: 255 seconds)
06:44Fenuks has joined IRC (Fenuks!~Fenuks@95.191.140.87)
06:56gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
07:01gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Ping timeout: 264 seconds)
07:38work_alkisg is now known as alkisg
07:43ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
08:58gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
09:02gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Ping timeout: 255 seconds)
09:16Fenuks has left IRC (Fenuks!~Fenuks@95.191.140.87, Ping timeout: 245 seconds)
09:42NeonLicht has joined IRC (NeonLicht!~NeonLicht@darwin.ugr.es)
10:34quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: :wq)
10:35quinox has joined IRC (quinox!~quinox@2a01:1b0:7998:416:1337:1337:1337:1337)
10:54robb_nl has joined IRC (robb_nl!~robb_nl@ip-213-49-83-170.dsl.scarlet.be)
11:00gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
11:06gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Ping timeout: 255 seconds)
11:33uXus has left IRC (uXus!~uXus@217.77.222.72, Remote host closed the connection)
11:48uXus has joined IRC (uXus!~uXus@217.77.222.72)
11:54robb_nl has left IRC (robb_nl!~robb_nl@ip-213-49-83-170.dsl.scarlet.be, Ping timeout: 240 seconds)
12:43robb_nl has joined IRC (robb_nl!~robb_nl@ip-213-49-83-170.dsl.scarlet.be)
12:59Hec-Thor has joined IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206)
13:00
<Hec-Thor>
hi i have never used IRC but lets give it a try
13:02
i hope you can help me, the thing is, i mounted a lubuntu desktop and installed ltsp, but i happen to have the same problem one person faced about year and a half ago, i found a conversation between
13:03
jujube and hyperbyte, link here: http://irclogs.ltsp.org/?d=2014-09-04 but it never got fixed
13:03gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
13:04
<Hec-Thor>
so while i try to log it wont enter, like the wheel keeps spinning and thats it
13:04
have tried to build the image again, i installed the DE to see if that did the work, but it didnt
13:08gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Ping timeout: 245 seconds)
13:19
<lee>
Hec-Thor: if you have never used irc before then the most important thing I can tell you is: wait for an answer (likely hours 'til someone who knows about it sees the question)
13:26
<Hec-Thor>
lee: thank u, i suspected that. Well i update my problem by saying that i reviewed the entire conversation and found that Jujubee fixed his problem by making a installation from scratch in ubuntu 14.04, however thats the same thing i did {this has happened to me twice} so im gonna check the docs he was provided, hoping somewhere there is a thing i missed the first time.
13:27
btw, does someone knows if i made an image for thin client and i make one for a fat client, may i have some diferent reaction? maybe i can make it log in?
13:28
will try right now
13:57
<Hyperbyte>
Hec-Thor, hi!
13:57
:-)
13:58
<Hec-Thor>
hi!
13:58
<Hyperbyte>
Hec-Thor, what happens exactly? The client boots normally, then your enter username and password and see a spinning wheel and nothing happens?
13:59
(I haven't fully read the irc logs you linked to)
13:59
<Hec-Thor>
exactly that way
14:02
<Hyperbyte>
How did you install LTSP?
14:04
<Hec-Thor>
well i installed lubuntu, then lstp-sever-standalone
14:04
configured the dhcp server, configured my network card as static
14:05
then create the image
14:05
a thin client
14:05
and, since that point, it cant log on
14:06
havent tried much since im a windows user actually
14:07
well there was not much to do i mean it didnt throw back a error number or anything
14:08
right now im trying to create a fat client instead since i read it boots kind of diferently
14:24Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
14:51
<Hyperbyte>
Hec-Thor, first of - if something doesn't work, you debug it. You don't just try something else randomly. This isn't Windows, with Linux you can debug and solve your problems.
14:52
Why I'm saying that, is because there is some reason why your first setup doesn't work. There's either something wrong with the code, the hardware, or you're doing something wrong. If you don't find out what it is, there's no guarantee you won't run into problems again, maybe even at a later stage.
14:52
Secondly, thin clients and fat clients are two entirely different things. You have to choose what is most appropriate for your setup.
14:53
Thin clients are great, because they enable you to utilize powerful server hardware, while having slow client hardware.
14:54
For example, I maintain LTSP for one company that has a server with dual Opteron processors and 64 GB RAM. I bought small computers without any fans or moving parts, and installed them as thin clients so they're still incredibly fast and powerful.
14:54
While not having noise/heat generated at the individual workplaces.
14:55
On the other hand, if your clients have about the same hardware specs as the server, you're better off with fat clients.
14:56
Both thin & fat clients boot all their software from the network, can be managed/updated centrally. But thin clients start a small login manager after booting, which lets a user log in to the server, and then starts the entire desktop on the server. So it doesn't use the client hardware.
14:57
Fat clients boot similarly from network, show the same login prompt, but rather start the entire desktop and all programs on the client (like any 'normal' computer does)
14:58gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
14:58
<Hyperbyte>
So you need to choose what is most appropriate for your use case. Let me know what that is, and then let's talk about how to best go about installing it.
15:07
<Hec-Thor>
thank you, im not sure how i could debug it. However, since i read the diference between fat and thin, i thought maybe i could switch to fat [wich im doing ] and make it log in since like you said, it starts the so on the client
15:07
i wanted thin but since its not much diference between host and client, i can use fat
15:08
if as a fat client it doesnt log in either then i would believe the problem is in the log part, and in that case i would know what to do
15:11Hec-Thor_ has joined IRC (Hec-Thor_!bdd478ce@gateway/web/freenode/ip.189.212.120.206)
15:12
<Hec-Thor_>
im back
15:13Hec-Thor has left IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206, Ping timeout: 252 seconds)
15:13gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, )
15:15
<Hec-Thor_>
so, i made it a fat client, didn't work, however now it takes me back to the log in instead of just spin the mouse wheel
15:17
i mean it looks like is going to log but then the screen goes black and returns to log in
15:18
it appeared a prompt for like 2 secs
15:23gbaman has joined IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
15:26Fenuks has joined IRC (Fenuks!~Fenuks@95.191.140.87)
15:30Hec-Thor has joined IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206)
15:31Hec-Thor_ has left IRC (Hec-Thor_!bdd478ce@gateway/web/freenode/ip.189.212.120.206, Ping timeout: 252 seconds)
15:35
<Hec-Thor>
ok so it throws this back: starting ntp server ntpd samed diabled; edit /etc/default/samed restoring resolver state... and then goes back to log in screen
15:40Hec-Thor_ has joined IRC (Hec-Thor_!bdd478ce@gateway/web/freenode/ip.189.212.120.206)
15:42Hec-Thor has left IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206, Ping timeout: 252 seconds)
15:51
<Hec-Thor_>
im not sure how to enable it in the client, either if enabling it will result in something good
16:15
<Hyperbyte>
Hec-Thor_, so now you have two issues, one with thin clients and one with fat.
16:15
Which one should we debug?
16:15
<Hec-Thor_>
lol really? thought it was an improvement
16:15
im gonna stick with fat
16:15
<Hyperbyte>
If there's not much difference between server and client, then I'd suggest you go the fat client way, because if you go thin, -all- software from -all- clients will run on -one- pc, the server.
16:16
So tell me more about your environment
16:16
How many clients, what purpose
16:16
Also, will the server be used for other things besides server LTSP, or is that a dedicated machine for LTSP?
16:19
<Hec-Thor_>
yes exactly :) im trying to install ltsp so i can use rdesktop and connect to the server wich will have virtualbox with windows, so i can serve 3 old pcs
16:20
wich my family could use instead of one
16:20
<Hyperbyte>
Okay
16:20
Then you want thin clients, not fat.
16:20
And you want
16:20
!screen_rdesktop
16:20
<ltsp`>
Error: "screen_rdesktop" is not a valid command.
16:20
<Hyperbyte>
!rdesktop
16:20
<ltsp`>
Error: "rdesktop" is not a valid command.
16:20
<Hyperbyte>
...
16:20
!rdp
16:20
<ltsp`>
I do not know about 'rdp', but I do know about these similar topics: 'RDP-localdev', 'freerdp', 'win8-rdp'
16:20
<Hyperbyte>
!freedrp
16:20
<ltsp`>
I do not know about 'freedrp', but I do know about these similar topics: 'freerdp'
16:20
<Hyperbyte>
!freerdp
16:20
<ltsp`>
freerdp: http://www.freerdp.com/ is a new RDP implementation which is more actively maintained than rdesktop. Newer LTSP versions support SCREEN_07=xfreerdp <params>.
16:20
<Hyperbyte>
Something like that.
16:21
If your thin clients hang during login process, doesn't matter. You don't need to log in to Linux, you just need to start xfreerdp instead of the LTSP login prompt.
16:21
Then you're done.
16:22
This is kind of the reason why I said, always debug before just doing something random. If you'd sticked with the broken thin client setup, we'd have it working probably by changing one config file. :-)
16:23
So remove /opt/ltsp, build a new thin client, then we probably need to install xfreerdp into the client chroot and edit lts.conf
16:23lbssousa has joined IRC (lbssousa!~hermes@177.79.23.2)
16:24
<Hyperbyte>
You can install software in the client chroot by running: ltsp-chroot -p in a root terminal. It'll open a prompt "inside" the chroot. You can then apt-get update && apt-get install xfreerdp && apt-get clean
16:24
Then if that worked you can rebuild the chroot using ltsp-update-image
16:24
And then finally you need to edit /var/lib/tftpboot/ltsp/i386/lts.conf with SCREEN_07=xfreerdp <servername> and you're done.
16:28
<Hec-Thor_>
that's amazing ! i didn't even imagined i could just skip log in. thank you very much, will let you know what happen
16:28
serioursly, thanks.
16:34Hec-Thor has joined IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206)
16:36lbssousa has left IRC (lbssousa!~hermes@177.79.23.2, Ping timeout: 250 seconds)
16:37Hec-Thor_ has left IRC (Hec-Thor_!bdd478ce@gateway/web/freenode/ip.189.212.120.206, Ping timeout: 252 seconds)
16:53
<Hyperbyte>
Hec-Thor, you're welcome. :-)
17:15
<alkisg>
Can't decide between Hercules and Thor? :)
17:25
<Hyperbyte>
alkisg, or his first name is Hector. ;-)
17:30Fenuks has left IRC (Fenuks!~Fenuks@95.191.140.87, Ping timeout: 255 seconds)
17:32Hec-Thor has left IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206, Ping timeout: 252 seconds)
17:54donjon has joined IRC (donjon!c820ec0a@gateway/web/freenode/ip.200.32.236.10)
18:37Hec-Thor has joined IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206)
18:37
<Hec-Thor>
!lst.conf
18:37
<ltsp`>
I do not know about 'lst.conf', but I do know about these similar topics: 'lts.conf'
18:37
<Hec-Thor>
!lst
18:37
<ltsp`>
I do not know about 'lst', but I do know about these similar topics: 'ldm', 'leet', 'ltsp'
18:38
<Hec-Thor>
!lts.conf
18:38
<ltsp`>
lts.conf: (#1) http://manpages.ubuntu.com/lts.conf, or (#2) lts.conf manpage is available in the ltsp-docs package
18:45Hec-Thor has left IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206, Quit: Page closed)
19:31cor_geeks has joined IRC (cor_geeks!~cor@cpe-76-92-215-174.kc.res.rr.com)
19:44Phantomas has left IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
20:24Hec-Thor has joined IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206)
20:25cor_geeks has left IRC (cor_geeks!~cor@cpe-76-92-215-174.kc.res.rr.com, Remote host closed the connection)
20:26cor_geeks has joined IRC (cor_geeks!~cor@cpe-76-92-215-174.kc.res.rr.com)
20:26
<Hec-Thor>
hi, finally i got the freerdp running, however it stays in a black screen, so i would like to know if there is a way to see what is happening in the background? like a log that throws back the errors behind freerdp?
20:28
i configured it like this: [192.168.0.182] SCREEN_07=xfreerdp RDP_OPTIONS="/v:192.168.0.184 /port:3389 /cert-ignore"
20:29
hope someone knows :)
20:41
<alkisg>
Hec-Thor: put SCREEN_07=xterm
20:41
reboot the client, you'll get an xterm instead of xfreerdp
20:42
From there, run the xfreerdp command that you want
20:42vmlintu has left IRC (vmlintu!~vmlintu@a88-112-3-40.elisa-laajakaista.fi, Ping timeout: 260 seconds)
20:42
<alkisg>
Once you have the correct xfreerdp command, then put SCREEN_07="the whole command"
20:42
No RDP_OPTIONS involved
20:48robb_nl has left IRC (robb_nl!~robb_nl@ip-213-49-83-170.dsl.scarlet.be, Ping timeout: 246 seconds)
20:57Hec-Thor has left IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206, Quit: Page closed)
20:58
<Hyperbyte>
Another satisfied customer.
21:18robb_nl has joined IRC (robb_nl!~robb_nl@ip-213-49-83-170.dsl.scarlet.be)
21:20vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
22:10robb_nl has left IRC (robb_nl!~robb_nl@ip-213-49-83-170.dsl.scarlet.be, Quit: I'm gone, bye bye)
22:15Hec-Thor has joined IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206)
22:17
<Hec-Thor>
lol satisfied indeed, although i can't run freerdp even with the right command (or wich i think it is)
22:17
<donjon>
!fuse
22:17
<ltsp`>
I do not know about 'fuse', but I do know about these similar topics: 'flash', 'future'
22:18
<Hec-Thor>
i can run freerdp from this linux, connect to another windows computer (not vm)
22:18
<donjon>
!usb
22:18
<ltsp`>
usb: LTSP only supports usb filesystem devices, for other projects like http://usbip.sourceforge.net/ probably this isn't the correct channel to ask, not many people have mentioned it
22:19
<Hec-Thor>
so i paste the same command in the lts.conf, but still, black screen with mouse pointer
22:21
is there a way to access the terminal skiping the log in like we did before? so i can see what the problem is?
22:21
<donjon>
vagrant
22:22
i figured out the network printer problem
22:22ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:22
<donjon>
in cups the printer needs to be set to shared....
22:22
<maldridge>
that would do it
22:23
<donjon>
;)
22:23
however... the usb problem is still dogging me...
22:24
the usb drives load in the client but nothing can be written to the drive
22:24
i was wondering if its a change in /etc/fuse.conf....
22:25
<maldridge>
so you can read but not write?
22:25
<vagrantc>
filesystem permissions, more likely.
22:25
<donjon>
correct...
22:25
<vagrantc>
is it even using ltspfs?
22:26
"mount | grep ltsp" from a client
22:26
<donjon>
but ubuntu builds the mounts under /media/username/drivename... when mounted... and the perms are correct
22:27
i don't think it even uses ltspfs... i will check on mount stats when i get access to lab again
22:27
really think its a fuse thing....
22:27
<vagrantc>
if it's not using ltspfs, then you'll want to debug it like any other ubuntu machine... nothing ltsp-specific about it
22:28
<donjon>
yes, that could be... ;)
22:28
<vagrantc>
for the most part, i don't think ubuntu will use fuse... unless you're mounting ntfs or something like that
22:28
mount | grep /media
22:28
<donjon>
actually ubuntu uses fuse for most user mounts... they didn't used to but now they do
22:28
<vagrantc>
that will tell what filesystem it's using
22:29
<donjon>
yes.
22:29
<vagrantc>
can't keep up with what ubuntu' doing these days, sure.
22:29
<donjon>
yeah... and they've been going through some pretty serious change ups lately
22:30
anyway the printer sharing worked in cups
22:30
silly me... now it makes sense ;)
22:31
sort of... there are still apps that dumped out to the printer when the sharing wasn't there... weird
22:31
<vagrantc>
if we ever get the ball rollng again, LTSP fatclients will be even more just like any other system
22:31
for LTSP6
22:31
but that's... taking time
22:31
<donjon>
cool
22:38
<vagrantc>
donjon: well, sounds like you're making some progress! good luck with figuring out the rest!
22:38* vagrantc waves
22:39vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
22:47gbaman has left IRC (gbaman!~gbaman@host81-142-46-233.in-addr.btopenworld.com, Read error: Connection reset by peer)
22:47gbaman_ has joined IRC (gbaman_!~gbaman@host81-142-46-233.in-addr.btopenworld.com)
23:04alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 246 seconds)
23:10
<Hyperbyte>
Hec-Thor, still there?
23:12
You can use SCREEN_02=xterm and SCREEN_07=xfreerdp at the same time
23:12
And use ctrl+alt+f2 and ctrl+alt+f7 to switch between them.
23:13
You could also try some things like pinging the server, to test network
23:13
<Hec-Thor>
sure, i did that on the thin and tried to start freerdp from there, the error was: xf_pre_connect: failed to open display:
23:14
<Hyperbyte>
That's because it needs a graphical session to run
23:14
I'm not too knowledged about starting a graphical session along with it unfortunately.
23:15
Try two things
23:15
Run getltscfg -a in SCREEN_02
23:15
See if the SCREEN_* options are loaded correctly like you would expect
23:15
And tell me, what is your SCREEN_07 line -exactly-?
23:23
<Hec-Thor>
it says
23:23
syntax error in /etc/lts.conf line 8
23:24
SCREEN_02="shell" SCREEN_07="xfreerdp --ignore-certificate --no auth --sec rdp 192.168.0.103"
23:24
screen_02 export
23:24
screen_07 export
23:24
that's all
23:25
and actually line 8 in my lts is an ip for another client
23:26
this: [192.168.0.185]
23:26cor_geeks has left IRC (cor_geeks!~cor@cpe-76-92-215-174.kc.res.rr.com, Ping timeout: 256 seconds)
23:28
<Hec-Thor>
my configuration matches what the client says
23:29
hey, i was reading that in order to fix the display error i should enable X11Forwarding
23:29
many users report that it worked, you think i should try?
23:51Hec-Thor_ has joined IRC (Hec-Thor_!bdd478ce@gateway/web/freenode/ip.189.212.120.206)
23:51Hec-Thor has left IRC (Hec-Thor!bdd478ce@gateway/web/freenode/ip.189.212.120.206, Ping timeout: 252 seconds)