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


Channel log from 27 October 2017   (all times are UTC)

01:05ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 248 seconds)
01:38adrianor1 has joined IRC (adrianor1!~adrianorg@177.132.217.98)
01:41adrianorg has left IRC (adrianorg!~adrianorg@186.213.155.204, Ping timeout: 240 seconds)
02:27adrianor1 is now known as adrianorg
05:29Statler has joined IRC (Statler!~Georg@p579FE139.dip0.t-ipconnect.de)
06:21ricotz has joined IRC (ricotz!~ricotz@p5B2A8E77.dip0.t-ipconnect.de)
06:21ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:37mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:38Statler has left IRC (Statler!~Georg@p579FE139.dip0.t-ipconnect.de, Remote host closed the connection)
07:47
<Hyperbyte>
Is there any reason for not setting SCREEN_01=ldm?
07:47
Currently SCREEN_07=ldm and in kernel options there's the vt.handoff=7 in my setup but it's having some issues.
07:50
<alkisg>
Hyperbyte: in vt1 there are the startup messages and a vt for root login
07:51
So setting screen_01=ldm on top of a getty may cause input issues
07:51
vt.handoff is for grub, not using in pxelinux
07:51
I removed it from the ltsp code a few years ago
07:51
*not used
08:14Statler has joined IRC (Statler!~Georg@gwrz3.lohn24.de)
08:22lucjayjay has joined IRC (lucjayjay!c32570e2@gateway/web/freenode/ip.195.37.112.226)
08:23ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
08:25lucjayjay has left IRC (lucjayjay!c32570e2@gateway/web/freenode/ip.195.37.112.226, Client Quit)
10:00alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Ping timeout: 252 seconds)
10:29gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
10:30vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
10:54alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
11:08gchaos has joined IRC (gchaos!~marcelo@2001:1284:f01c:7c6d:9a83:89ff:fe72:5db7)
11:12gchaos has left IRC (gchaos!~marcelo@2001:1284:f01c:7c6d:9a83:89ff:fe72:5db7, Ping timeout: 255 seconds)
11:22highvoltage has left IRC (highvoltage!~highvolta@ubuntu/member/highvoltage, Ping timeout: 264 seconds)
11:22highvoltage has joined IRC (highvoltage!~highvolta@ubuntu/member/highvoltage)
11:34
<Hyperbyte>
alkisg, so what do I do if users have to press ctrl+alt+f7 on startup?
11:34
I added vt.handoff but that doesn't seem to work
11:35
<vagrantc>
might be a sign that somehow the filesystem isn't writeable
11:35* vagrantc has seen that before
11:35
<Hyperbyte>
I do think these problems started only when I added 'quiet splash' to the kernel startup line
11:35
<alkisg>
(02:34:51 μμ) Hyperbyte: I added vt.handoff but that doesn't seem to work ==> didn't I say that this doesn't work and we completely removed it from the code?
11:36
Hyperbyte: paste the output of `getltscfg -a` on the client
11:36
In general, the highest vt gets to be the default,unless you use LDM_DEFAULT=07 etc
11:36
or default_screen however we call that one
11:39
<Hyperbyte>
alkisg, you said that after I tried it. Obviously I tried fixing this myself before contact the Oracle.
11:39* vagrantc thinks SCREEN_DEFAULT
11:40
<Hyperbyte>
Interestingly, I can't reliably reproduce it. It seems to happen with some clients, but not all. I can't reproduce it on a VM PXE client for example.
11:43
http://razor.middelkoop.cc/~dj/ltsconf.png
11:46
<alkisg>
Hyperbyte: and that's in 16.04?
11:46
Try with SCREEN_DEFAULT=07, although it sounds like a race condition
11:47
You can also stop using SCREEN_02 completely, and use something like this:
11:47
!ROOT_PASSWORD_HASH
11:47
<ltsp>
ROOT_PASSWORD_HASH: to be able to login as root in vt1, with password "qwer1234", put this in lts.conf: INIT_COMMAND_01="sed 's!^root:[^:]*:!root:$6$p2LdWE6j$PDd1TUzGvvIkj9SE8wbw1gA/MD66tHHlStqi1.qyv860oK47UnKcafSKqGp7cbgZUPlgyPv6giCVyCSCdJt1b0:!' -i /etc/shadow"
11:47
<alkisg>
This saves a bit RAM and is a bit more secure than SCREEN_02=shell, as it requires a login
11:50
<Hyperbyte>
That's 16.04
11:51
But user doesn't end up at screen_02
11:51
They stay at screen 01
11:51
<alkisg>
LTSP hasn't caught up with the systemd way of starting services yet
11:51
<Hyperbyte>
I can remove screen_02 completely, I added it for getltscfg
11:51
<alkisg>
So you normally don't specify any screens at all, yet you get this issue?
11:52
<Hyperbyte>
I specify SCREEN_07=ldm
11:52
I could remove that as well though.
11:53
Shall I remove the vt.handoff=7 as well?
11:53
<alkisg>
Yes that's not supposed to be there at all
11:53
You probably have an older version of update-kernels.conf
11:53
Btw note that you shouldn't be using LDM_XSESSION
11:54
<Hyperbyte>
LDM_SESSION="mate-session"?
11:56* vagrantc is really tempted to replace LDM_XSESION with a hard-coded value, as it's so consistantly being abused
11:57
<vagrantc>
except, ugh... don't really want to work on LDM
11:57
<alkisg>
+1 :D
11:58
Hyperbyte: normally, no other sessions are there, so why specify it..
11:58
Let it pick up the default, which should be that one
11:58Eric4 has left IRC (Eric4!~eric@sdi.iut-valence.fr, Ping timeout: 246 seconds)
12:00
<vagrantc>
it arguably saves a tiny number of filesystem calls to explicitly set SCREEN_07=ldm
12:02Eric4 has joined IRC (Eric4!~eric@sdi.iut-valence.fr)
12:03
<alkisg>
0.0001 msec is a good price to pay to avoid 1 line of configuration
12:14gdi2k has left IRC (gdi2k!~gdi2k@49.151.45.100, Ping timeout: 240 seconds)
12:29robi has joined IRC (robi!bb11aeb4@gateway/web/freenode/ip.187.17.174.180)
12:29
<robi>
lts.conf
12:29robi is now known as Guest62742
12:29
<Guest62742>
configurar servidor para acessar plataforma windows
12:30
<alkisg>
English
12:31
<vagrantc>
Guest62742: usa protocol "RDP" ?
12:41
<ogra_>
as opposed to the european RDP protocol ?
12:41
:)
12:42
<vagrantc>
hah
12:44
Guest62742: pienso xfreerdp o rdesktop, pero no estoy seguro que tu necesitas exactamente
12:44
Guest62742: posible xrdp
12:47Guest62742 has left IRC (Guest62742!bb11aeb4@gateway/web/freenode/ip.187.17.174.180, Ping timeout: 260 seconds)
13:55ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
14:09vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
14:24mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
14:34lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
14:43Eric4 has left IRC (Eric4!~eric@sdi.iut-valence.fr, Ping timeout: 246 seconds)
15:35kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:bd40:964e:d99f:3d3, Ping timeout: 264 seconds)
15:39gdi2k has joined IRC (gdi2k!~gdi2k@49.151.45.100)
15:44Royale_AJS has joined IRC (Royale_AJS!~Royale_AJ@75-129-94-78.static.aldl.mi.charter.com)
16:02gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
16:31Eric4 has joined IRC (Eric4!~eric@sdi.iut-valence.fr)
16:32Statler has left IRC (Statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
16:35kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:311f:4500:818d:2ad9:70ef:feaa)
16:57Eric4 has left IRC (Eric4!~eric@sdi.iut-valence.fr, Ping timeout: 248 seconds)
17:09kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:818d:2ad9:70ef:feaa, Ping timeout: 264 seconds)
17:18lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Ping timeout: 248 seconds)
17:24kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:311f:4500:818d:2ad9:70ef:feaa)
17:30kjackal_ has left IRC (kjackal_!~quassel@2a02:587:311f:4500:818d:2ad9:70ef:feaa, Quit: No Ping reply in 180 seconds.)
17:32lucascastro has joined IRC (lucascastro!~lucas@189.90.38.210.jupiter.com.br)
17:33kjackal_ has joined IRC (kjackal_!~quassel@athedsl-165820.home.otenet.gr)
17:49kjackal_ has left IRC (kjackal_!~quassel@athedsl-165820.home.otenet.gr, Ping timeout: 255 seconds)
17:58bitchecker has left IRC (bitchecker!~bitchecke@31.131.20.132, Ping timeout: 252 seconds)
18:03bitchecker has joined IRC (bitchecker!~bitchecke@31.131.20.132)
18:18vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:28marcelo_ has joined IRC (marcelo_!~marcelo@2001:1284:f01c:7c6d:9a83:89ff:fe72:5db7)
18:28marcelo_ is now known as gchaos
18:54lucascastro has left IRC (lucascastro!~lucas@189.90.38.210.jupiter.com.br, Ping timeout: 240 seconds)
19:01fzimper has joined IRC (fzimper!4e2b136d@gateway/web/freenode/ip.78.43.19.109)
19:23vagrantc_ has joined IRC (vagrantc_!~vagrant@unaffiliated/vagrantc)
19:25vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 246 seconds)
19:25vagrantc_ is now known as vagrantc
19:37vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 255 seconds)
19:39vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
20:31gchaos has left IRC (gchaos!~marcelo@2001:1284:f01c:7c6d:9a83:89ff:fe72:5db7, Ping timeout: 255 seconds)
20:34kjackal_ has joined IRC (kjackal_!~quassel@2a02:587:3119:d100:8017:195f:729d:d975)
21:04alazyworkaholic has joined IRC (alazyworkaholic!~alan@191.54.140.181)
21:06
<alazyworkaholic>
I ran ltsp-build-client --purge-chroot. It ran for quite a while, and then ended with "No LTSP chroots found, please run ltsp-build-client.
21:14
error: LTSP client installation ended abnormally". Yet i still have a full /opt/ltsp/amd64. Isn't that where the chroot env is, and shouldn't it then be empty?
21:17ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:18
<vagrantc>
using --purge-chroot will purge the existing chroot before creating it, and then create a new one
21:24ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
21:31vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
21:35
<alazyworkaholic>
vagrantc: thank you.
21:51Royale_AJS has left IRC (Royale_AJS!~Royale_AJ@75-129-94-78.static.aldl.mi.charter.com, Quit: Royale is leaving)
22:46fzimper has left IRC (fzimper!4e2b136d@gateway/web/freenode/ip.78.43.19.109, Ping timeout: 260 seconds)