LTSP 5 is in minimal maintenance mode
The new LTSP is hosted at https://ltsp.github.io

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


Channel log from 31 October 2019   (all times are UTC)

00:21Leolo_2 has left IRC (Leolo_2!~fil@184-75-132-167.dr.cgocable.ca, Ping timeout: 240 seconds)
01:33dgroos has joined IRC (dgroos!~dagro001@63.225.132.145)
01:38dgroos_ has joined IRC (dgroos_!~dagro001@vpn.mpls.k12.mn.us)
01:39dgroos has left IRC (dgroos!~dagro001@63.225.132.145, Ping timeout: 276 seconds)
01:39dgroos_ is now known as dgroos
02:34dgroos has left IRC (dgroos!~dagro001@vpn.mpls.k12.mn.us, Quit: dgroos)
03:44vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
05:10os_a has joined IRC (os_a!~Thunderbi@195.112.116.22)
05:41kjackal has joined IRC (kjackal!~quassel@athedsl-4546118.home.otenet.gr)
06:01statler has joined IRC (statler!~Georg@p5B30EE2F.dip0.t-ipconnect.de)
06:19woernie has joined IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de)
06:50kjackal has left IRC (kjackal!~quassel@athedsl-4546118.home.otenet.gr, Ping timeout: 268 seconds)
07:24ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:26alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
07:26alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
07:32alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
07:32alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
07:42alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
07:42alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
07:45alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Client Quit)
07:45alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
07:46kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:c585:f21c:70ac:1f71)
07:53Ark74 has left IRC (Ark74!~Luis@177.238.145.140, Quit: Leaving)
07:59Ark74 has joined IRC (Ark74!~Luis@177.238.145.140)
08:02alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
08:02alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
08:43meo has left IRC (meo!~systemdju@unaffiliated/mikeseth, Ping timeout: 265 seconds)
09:13statler_ has joined IRC (statler_!~Georg@gwrz3.lohn24.de)
11:45os_a has left IRC (os_a!~Thunderbi@195.112.116.22, Quit: os_a)
12:03Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:07section1 has joined IRC (section1!~section1@178.33.109.106)
12:28statler has left IRC (statler!~Georg@p5B30EE2F.dip0.t-ipconnect.de, Remote host closed the connection)
12:46woernie has left IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de, Remote host closed the connection)
12:46os_a has joined IRC (os_a!~Thunderbi@195.112.116.22)
12:46woernie has joined IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de)
13:41gp has joined IRC (gp!~gp@96.71.93.13)
13:49gp has left IRC (gp!~gp@96.71.93.13, Remote host closed the connection)
13:50gp has joined IRC (gp!~gp@96.71.93.13)
14:00gp has left IRC (gp!~gp@96.71.93.13, Quit: Leaving)
14:54dgroos has joined IRC (dgroos!~dagro001@205.215.175.117)
14:56
<dgroos>
Hey! I'm in class using ltsp19 and clients can't access the internet. alkisg helped figure out my NAT issue in the ltsp.conf, but this is different.
14:57
When a client tries to go to network manager and enable the wired connection it says:
14:58
<alkisg>
Clients don't have access to network manager except for vpn
14:58
!vnc-edide
14:58
<ltsp>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
14:58
<dgroos>
"System policy prevents modifcaion of network for all users" and asks for my authentication.
15:01
<alkisg>
dgroos: it's nat again; did you disable the ltsp service?
15:02
<dgroos>
not that I know...
15:02
<alkisg>
It didn't run at system stratup
15:02
You have uptime=50 minutes
15:02
and ltsp last ran yesterday
15:02
and just now that i restarted it, and it says disabled
15:03
<dgroos>
yes, I did all 4 steps of the install again, then rebooted the server
15:03
<alkisg>
Let me enable it and see... I wonder if it's related to vagrant's changes
15:03
Yeah maybe that's what it is
15:03
The service is there, but not the activation link
15:04
I fixed it for your setup; I need to check if it affects all, and send a fix
15:04
All ok, closing VNC...
15:04
<dgroos>
OK thanks!
15:04
<alkisg>
np
15:05
<dgroos>
Q, do I need to tell students to restart?
15:05
<alkisg>
No
15:05
<dgroos>
Thanks again :-D
15:05
<alkisg>
:)
15:59Leolo_2 has joined IRC (Leolo_2!~fil@184-75-132-167.dr.cgocable.ca)
16:01
<alkisg>
vagrantc: somehow the ltsp service doesn't start anymore... package contents before: https://termbin.com/vkdu - package contents after: https://termbin.com/zjt6t - I'll have a look but if I can't solve it via debhelper I'll revert it to what we had before
16:02
I.e. /lib/systemd/system/multi-user.target.wants/ltsp.service is now missing
16:14kjackal has left IRC (kjackal!~quassel@2a02:587:3107:2e00:c585:f21c:70ac:1f71, Remote host closed the connection)
16:34kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:a81f:510a:ba0a:2e70)
16:36kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:a81f:510a:ba0a:2e70)
17:25
<dgroos>
alkisg: Not sure if this is related, but I updated the login policy w/these directions: https://help.gnome.org/admin/system-admin-guide/stable/login-userlist-disable.html.en
17:27
I think the internet worked before I did this though not positive.
17:43statler_ has left IRC (statler_!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
17:49woernie has left IRC (woernie!~werner@p57A0E783.dip0.t-ipconnect.de, Remote host closed the connection)
18:01douglas_br has joined IRC (douglas_br!bb5f6554@187.95.101.84)
18:02
<douglas_br>
hello
18:02
i have problems
18:02
<alkisg>
dgroos: nah, I sent an update to ppa, which included vagrant's packaging changes, which I think were what stopped the service
18:03
douglas_br: hi, hwat problems?
18:04
<douglas_br>
I did install education package and update system and ltsp image. After this ltsp "lost" dnsmasq
18:04
<alkisg>
I'm not sure what "lost dnsmasq" means
18:06
<douglas_br>
I have 2 Nics. so: ltsp -o dnsmasq -d1 -p0 --dns-server=200. nice, after status it show the IP dns. But, I start on client does not show more
18:06
<alkisg>
Try this on the server: sudo systemctl restart ltsp
18:06
Does this fix internet connectivity for the clients?
18:07
<douglas_br>
wait
18:09
alkisg Does this fix internet connectivity for the clients?
18:09
yes
18:09
only this?
18:09
<alkisg>
OK so it was caused by an ltsp update; wait for another one that will fix it
18:09
In the mean time yeah just run this after server reboots
18:11
<douglas_br>
ohhhh right
18:12
thanks so much alkis
18:19gvy has left IRC (gvy!~mike@altlinux/developer/mike, Quit: Leaving)
18:19gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
18:21vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:22
<alkisg>
vagrantc: somehow the ltsp service doesn't start anymore... package contents before: https://termbin.com/vkdu - package contents after: https://termbin.com/zjt6t - I'll have a look but if I can't solve it via debhelper I'll revert it to what we had before
18:22
(06:02:02 PM) alkisg: I.e. /lib/systemd/system/multi-user.target.wants/ltsp.service is now missing
18:31
<vagrantc>
alkisg: huh. worked for me...
18:32
alkisg: maybe it's build-release specific ... e.g. bugs that were fixed in newer versions of debhelper
18:32
i think i've only tested building on sid, running on buster
18:33
alkisg: you could also file issues, as i appear to get all of them :)
18:34
<alkisg>
Hehe
18:34
Sure; I was looking for a quick fix though as users lost internet connectivity with yesterday's ppa update
18:34
I'll send one, and file a bug, and we can solve it properly later on
18:34
<vagrantc>
fair enough
18:35
<alkisg>
The problem was reported on 18.04
18:35* vagrantc doesn't look forward to maintaining a debian-specific packaging fork...
18:35
<alkisg>
Eh of *course* not :)
18:36mwalters has left IRC (mwalters!~ubox@c-73-152-61-86.hsd1.va.comcast.net)
18:36mwalters has joined IRC (mwalters!~ubox@c-73-152-61-86.hsd1.va.comcast.net)
18:36
<vagrantc>
until resolving the binary download verification issue, going to be stuck in experimental anyways
18:37
<alkisg>
I'll have time for that in August, but until then, I'm afraid I won't...
18:38
<vagrantc>
i hear you
18:38
i'll try and fix it :)
18:38
<alkisg>
ty :)
18:38
<vagrantc>
i guess i can assign myself the bug
18:38
<alkisg>
(it involves reading a bit, as I'm not very up to date with all the certification mechanisms; you'll surely do a better job, faster)
18:39
<vagrantc>
it's a bit ugly, but i can actually probably come up with something fairly quick
19:05
<alkisg>
vagrantc: https://packages.debian.org/experimental/all/ltsp/filelist also doesn't contain the "wants" target
19:05
Is it possible that ltsp.service file is copied in debian/ after dh_installsystemd has already ran?
19:07statler has joined IRC (statler!~Georg@p5B30EE2F.dip0.t-ipconnect.de)
19:17kjackal has left IRC (kjackal!~quassel@2a02:587:3107:2e00:a81f:510a:ba0a:2e70, Ping timeout: 276 seconds)
19:18
<vagrantc>
alkisg: not sure how it's "supposed" to work with systemd, honestly
19:19
alkisg: the way i'm using it might depend on a newer debhelper compat level
19:21
<alkisg>
Newer than experimental?
19:21
vagrantc: it doesn't work in experimental
19:21
<vagrantc>
oh
19:22
well, you're telling it "behave as if you're debhelper 9"
19:22
so it doesn't matter how new it is
19:22
<alkisg>
We can do debhelper 10
19:22
I backported it to the xenial ppa
19:22
Don't know if it'll help
19:22
<vagrantc>
maybe "dh --with systemd" will work
19:22
10 might help, yes
19:23
10 brings: The systemd sequence is now enabled by default. Please pass --without systemd to dh if this is not desirable for a given package.
19:23
though we might be able to use debhelper 9 and "dh --with systemd"
19:23
i'd prefer to upgrade to 10, of course :)
19:24
11 has even better systemd support
19:25
<alkisg>
In my tests, debhelper 10 didn't install in jessie then
19:25
oh no, it installed, but failed to work properly, like now
19:25
....something like that
19:25
That's why I had that weird code there, for compatibility in all supported versions
19:25
OK I'll run some tests tomorrow
19:25
<vagrantc>
dh_installinit --no-scripts might also be something to explore
19:26
or rather, removing it
19:26* vagrantc would really like to avoid handling it by hand
19:26
<vagrantc>
though it obviously also needs to work :)
19:26robert45 has joined IRC (robert45!~robert45@r186-54-48-111.dialup.adsl.anteldata.net.uy)
19:27
<alkisg>
I think my initial idea was "this works everywhere; and let's wait until jessie is unsupported to do it with just debhelper"
19:27
I"ll record my findings now
19:27
<robert45>
hey guys, Im trying to boot from a ltsp thin client but Im presented with all this errors, any ideas how to solve it? https://imgur.com/a/51k3IVe
19:27
<vagrantc>
alkisg: you mean jessie-lts ?
19:28
alkisg: or stretch ?
19:28
<alkisg>
No I'm sure I meant jessie, although I odn't remember if it was lts or not
19:28
<vagrantc>
i guess i must not have been using any features that required the ltsp service
19:29
jessie's been out of normal support for at least a couple years
19:29
<alkisg>
I had checked the supported dates, so I guess I was looking at the lts one
19:30
from 17th June 2018 to June 30, 2020 ==> yeah that's what I remembered, a year more
19:32
!netplan | echo robert45
19:32
<ltsp>
robert45 netplan: To work around https://bugs.launchpad.net/netplan/+bug/1763608/comments/47, either update to a new LTSP version, or put this in lts.conf: INIT_COMMAND_RM_NETPLAN="rm -rf /lib/systemd/system-generators/netplan /run/netplan"
19:32
<alkisg>
!greek-schools-ppa
19:32
<ltsp>
greek-schools-ppa: https://launchpad.net/~ts.sch.gr/+archive/ppa/ supports LTS Ubuntu releases with newer LTSP versions, bug fixes etc
19:32
<vagrantc>
are there installs actually using ltsp 19.x and needing jessie?
19:33
<robert45>
alkisg thanks, trying this now
19:33
<vagrantc>
alkisg: or does that just align well with ubuntu's oldish lts release?
19:34
alkisg: in any case, i think we might just be able to make the symlink in debian/ltsp.links appropriately and otherwise leave things as they are
19:35
alkisg: that would emulate what you had before, i think...
19:35
<robert45>
alkisg you mean in /etc/dnsmasq.d/ltsp.conf right? Its throwing an error when I add it at the end of the config file: bad option at line 63 of /etc/dnsmasq.d/ltsp.conf
19:43
ah nevermind, my bad
19:56
<alkisg>
(09:32:25 PM) vagrantc: are there installs actually using ltsp 19.x and needing jessie? => eh in my mind it was just "let's support the officially supported releases"; it also happened that all of them are the ones that shipped with systemd;
19:56
and finally, I'd like to be able to boot older systems as ltsp clients, it's convenient for testing with e.g. kernel 3.18 that didn't have some bugs or for running java in a browser that's no longer supported etc
19:56
So I spend a couple of days in making sure it runs in jessie; I wouldn't want to throw that away just because of a couple of lines..
19:57
<robert45>
alkisg I have rebooted using your workaround but its still throwing errors and not booting, any advice is very appreciated: https://imgur.com/a/GZj25Me
19:57
<alkisg>
robert45: run either of those:
19:57
!vnc-edide
19:57
<ltsp>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
19:58
<alkisg>
!vnc-dide
19:58
<ltsp>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
19:58
<robert45>
alkisg this thin client is on a lan without internet, that is why Im showing photos and not copy/pasting
19:58
<alkisg>
robert45: I want to see the server not the client
19:59
Or pastebin your lts.conf
19:59
Remove LDM_PASSWORD if you have that
19:59section1 has left IRC (section1!~section1@178.33.109.106, Quit: Leaving)
19:59douglas_br has left IRC (douglas_br!bb5f6554@187.95.101.84, Remote host closed the connection)
20:01
<robert45>
alkisg same with the server. As for the lts.conf its almost empty except for the line you said to add, here is the lts.conf https://pastebin.ubuntu.com/p/Ct9c5kV5J7/
20:02
<alkisg>
robert45: you need this: [Default] instead of [example]
20:02
Change line 1 there, then reboot client
20:02
<robert45>
alkisg Thanks, trying now
20:12
<alkisg>
So I think the trend is to use epoptes.org instead of www.epoptes.org, right? E.g. googling about "gitlab" or "github" show gitlab.com etc...
20:13
We pointed the epoptes.org domain to epoptes.github.io, it works great, it even has https now :D
20:13
I'm waiting from Jim and Ron to see if they want that for ltsp.org too, or if we'll just let it expire
20:14
(or if they'll keep it for emails etc...)
20:17
<vagrantc>
alkisg: it might also be possible to backport newer debhelper to jessie ...
20:17
<alkisg>
vagrantc: initial test with compat=10 => works
20:18
Give me a moment to take a second look
20:18
Built on bionic, installed on jessie
20:18
<vagrantc>
oh, that's not too bad
20:19
*might* even get away with compat=10 on debhelper 9 ... but that's a bit ugly
20:20
<alkisg>
OK everything seems fine; jessie users may use the xenial PPA, which has debhelper=10 after I enabled backports
20:20
<vagrantc>
yay!
20:20
that seems like a much cleaner option :)
20:20
<alkisg>
Commiting + sending a build. Yay true! :)
20:21
dpkg -L ltsp => doesn't show the wants file, but I guess that's how debhelper prefers it
20:21
I was just shipping the symlink in the .deb before
20:21
debhelper does that on postinst
20:22
On the plus side, it starts the service on postinst, so it will enable nat too :D
20:22
(if ip=192.168.67.1 etc)
20:23statler has left IRC (statler!~Georg@p5B30EE2F.dip0.t-ipconnect.de, Remote host closed the connection)
20:30
<vagrantc>
yeah.
20:31* vagrantc is kinda weirded out by fiddling with firewall out-of-the-box but will just accept it
20:31
<alkisg>
Firewall?
20:31
<vagrantc>
enabling NAT requires changes to firewall rules
20:31
<alkisg>
You mean masquerade?
20:32
iptables?
20:32
<vagrantc>
whatever you call it, it's implemented in the firewalling rules
20:32
or nftables on newer installs
20:32
<alkisg>
I'm not sure if it's about terminology, but I'm not touching any firewalls; I'm not even using one in my installations...
20:32
I think firewall can be implemented on top of iptables etc
20:33
<vagrantc>
iptables is firewalling
20:33
<alkisg>
But that's an add-on...
20:33
<vagrantc>
nat is implemented via firewall rules
20:33
<alkisg>
iptables can route traffic, change ports etc
20:33
firewall is just a tiny subset of what iptables can do
20:33
<vagrantc>
sounds like we're in a terminology debate :P
20:33
<alkisg>
...or my terminology is completely wrong :)
20:33
:)
20:34
<vagrantc>
touching iptables/nftables rules weirds me out
20:34
<alkisg>
apt install ufw or other firewalls etc does that though
20:34
In our case, NAT=1 means "yeah I want to do that"
20:35
(in ltsp.conf)
20:35
<vagrantc>
sure... it's just those things are more specifically targetted at that domain ... like i said, i'll accept it
20:36
that it's only enabled when the magic LTSP network is present makes it kinda ok
20:43dgroos has left IRC (dgroos!~dagro001@205.215.175.117, Quit: dgroos)
20:47
<robert45>
alkisg Looks its booting now, some progress at last, thank you! However, it seems to get stuck after I finish the basic setup. Any ideas? https://imgur.com/a/mbWnfjn
20:48
sorry for the bad quality of the photos
20:51Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:53
<robert45>
nevermind, it shutdown and now its on another screen, still testing
20:57
alkisg ok so its a bit buggy right now, for example I cant login. syslog shows this: https://paste.ubuntu.com/p/8N4rbmxWdq/
20:57
could it be related?
21:01ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:08
<robert45>
ok so I rebooted and its fine now!
21:46kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:ddb1:8d31:3263:a00e)
22:20kjackal has left IRC (kjackal!~quassel@2a02:587:3107:2e00:ddb1:8d31:3263:a00e, Ping timeout: 276 seconds)
23:06
<robert45>
hey guys, so I finally got my ltsp thin client working, but its actually asking me to re-setup the machine everytime I reboot the client, is there anyway the changes to persists? See here: https://imgur.com/a/z4GV7z0
23:43vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)