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 30 April 2019   (all times are UTC)

02:32fnurl has left IRC (fnurl!~url@host81-154-10-106.range81-154.btcentralplus.com, Ping timeout: 246 seconds)
02:38fnurl has joined IRC (fnurl!~url@host81-154-10-106.range81-154.btcentralplus.com)
02:43alex^alex-XPS-13 has joined IRC (alex^alex-XPS-13!ac3823ee@172.56.35.238)
02:44fnurl has left IRC (fnurl!~url@host81-154-10-106.range81-154.btcentralplus.com)
02:48alex^alex-XPS-13 has left IRC (alex^alex-XPS-13!ac3823ee@172.56.35.238, Remote host closed the connection)
02:54fnurl has joined IRC (fnurl!~url@host81-154-10-106.range81-154.btcentralplus.com)
03:00fnurl has left IRC (fnurl!~url@host81-154-10-106.range81-154.btcentralplus.com, )
03:12vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
05:33ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:24SYS64738 has joined IRC (SYS64738!~jhonny5@159.213.93.166)
06:36book`_ has left IRC (book`_!~book`@68.ip-149-56-14.net, Quit: Leaving)
06:39book` has joined IRC (book`!~book`@68.ip-149-56-14.net)
06:58kjackal has joined IRC (kjackal!~quassel@adsl-172.46.190.127.tellas.gr)
07:21woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de)
08:01SYS64738 has left IRC (SYS64738!~jhonny5@159.213.93.166, Ping timeout: 246 seconds)
08:04bengoa has left IRC (bengoa!~alberto@194.50.55.200, Remote host closed the connection)
08:21bengoa has joined IRC (bengoa!~alberto@194.50.55.200)
08:27statler has joined IRC (statler!~Georg@gwrz3.lohn24.de)
08:43SYS64738 has joined IRC (SYS64738!~jhonny5@159.213.93.166)
09:05SYS64738 has left IRC (SYS64738!~jhonny5@159.213.93.166, Ping timeout: 246 seconds)
09:06GodFather has left IRC (GodFather!~rcc@143.59.184.72, Ping timeout: 258 seconds)
09:50kjackal has left IRC (kjackal!~quassel@adsl-172.46.190.127.tellas.gr, Ping timeout: 246 seconds)
10:21kjackal has joined IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899)
10:36SYS64738 has joined IRC (SYS64738!~jhonny5@159.213.93.166)
10:51ZAJDAN has joined IRC (ZAJDAN!~zdenek@77.48.149.75)
11:14GodFather has joined IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net)
11:52kjackal has left IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899, Remote host closed the connection)
11:54kjackal has joined IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899)
12:06SYS64738 has left IRC (SYS64738!~jhonny5@159.213.93.166, Ping timeout: 246 seconds)
12:16Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:21kjackal has left IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899, Ping timeout: 240 seconds)
12:21kjackal has joined IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899)
12:23bcg has left IRC (bcg!~b@2001:2003:54f9:42f6::1, Quit: bcg)
12:58josefig has left IRC (josefig!~josefig@unaffiliated/josefig, Ping timeout: 258 seconds)
13:08kjackal has left IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899, Remote host closed the connection)
13:09kjackal has joined IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899)
13:20SYS64738 has joined IRC (SYS64738!~jhonny5@159.213.93.166)
13:22adrianor1 has joined IRC (adrianor1!~adrianorg@177.204.159.129.dynamic.adsl.gvt.net.br)
13:25adrianorg has left IRC (adrianorg!~adrianorg@177.204.150.74.dynamic.adsl.gvt.net.br, Ping timeout: 250 seconds)
13:38fnurl has joined IRC (fnurl!~url@host81-154-10-106.range81-154.btcentralplus.com)
13:42fnurl has left IRC (fnurl!~url@host81-154-10-106.range81-154.btcentralplus.com, Client Quit)
14:01GodFather has left IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net, Ping timeout: 246 seconds)
14:01bcg has joined IRC (bcg!~b@82-128-232-145.bb.dnainternet.fi)
14:09spaced0ut_ has joined IRC (spaced0ut_!~spaced0ut@198.211.112.88)
14:11spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 268 seconds)
14:39josefig has joined IRC (josefig!~josefig@unaffiliated/josefig)
14:43kjackal has left IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899, Ping timeout: 250 seconds)
14:44kjackal has joined IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899)
14:56woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Remote host closed the connection)
15:15kjackal has left IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899, Ping timeout: 250 seconds)
15:16kjackal has joined IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899)
15:19bcg has left IRC (bcg!~b@82-128-232-145.bb.dnainternet.fi, Quit: bcg)
15:25kjackal has left IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899, Ping timeout: 240 seconds)
15:25kjackal has joined IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899)
15:35SYS64738 has left IRC (SYS64738!~jhonny5@159.213.93.166, Ping timeout: 246 seconds)
15:48bcg has joined IRC (bcg!~b@82-128-243-39.bb.dnainternet.fi)
16:15kjackal has left IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899, Ping timeout: 264 seconds)
16:15kjackal has joined IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899)
16:43vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:00kjackal has left IRC (kjackal!~quassel@2a02:587:793e:5d00:cd36:ac7a:accf:1899, Remote host closed the connection)
17:03kjackal has joined IRC (kjackal!~quassel@ppp-2-84-244-151.home.otenet.gr)
17:38woernie_ has joined IRC (woernie_!~werner@x4db411d6.dyn.telefonica.de)
18:06statler has left IRC (statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
18:16bcg has left IRC (bcg!~b@82-128-243-39.bb.dnainternet.fi, Ping timeout: 246 seconds)
18:18bcg has joined IRC (bcg!~b@82-128-233-166.bb.dnainternet.fi)
18:57
<quinox>
!LDM_PASSWORD_HASH
18:57
<ltsp`>
LDM_PASSWORD_HASH: LDM_PASSWORD_HASH=True in lts.conf saves the password hash to /etc/shadow on login, so that the users can unlock the screensaver etc. If they happen to change their password though, that only takes effect until logout.
18:57
<Sleaker>
hmm, so I can get my thinclient to boot the image just fine, but it's not getting into a graphical login.
18:58
what's the best place to start troubleshooting which area is the problem
18:59
<quinox>
does control+alt+f1 / control+alt+f2 work?
18:59
<Sleaker>
yup
18:59
<quinox>
if so you can poke around in the logs
18:59
<Sleaker>
I have syslog forwarding working too
18:59
<quinox>
smart
18:59
<Sleaker>
and ssh directly into the box
18:59bcg has left IRC (bcg!~b@82-128-233-166.bb.dnainternet.fi, Quit: bcg)
19:00bcg has joined IRC (bcg!~b@82-128-233-166.bb.dnainternet.fi)
19:00
<Sleaker>
not sure if it's problematic but I am getting a pam issue with dbus-org.freedesktop.login1.service not found.
19:01
oh also looks like the nbd client is getting disconnected after the system boots.
19:01
that's odd
19:02
https://pastebin.com/51Vv8ppg
19:09
<vagrantc>
that's normal
19:09
<Sleaker>
mkay. it looks like it gets remounted later on.\
19:09
<vagrantc>
the nbd disconnect ... it's just a check to compare if the image you're running is different than the available image
19:10
to prevent people from running outdated images
19:10
<Sleaker>
makes sense. should there be 2 client processes still running nbd-client though? 2 of them look hung
19:10
3*
19:11spaced0ut_ has left IRC (spaced0ut_!~spaced0ut@198.211.112.88, Quit: Leaving)
19:11spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
19:13
<vagrantc>
haven't looked at that aspect closely ... i would think they would close on disconnect, but maybe run for a bit...
19:14
<Sleaker>
hmm. probably not related at all to my issue anyway
19:14
<vagrantc>
yeah, the dbus stuff might be a bigger problem
19:15
<Sleaker>
mhmm
19:15
<vagrantc>
LDM_SMART_COLOR_DEPTH=false ?
19:15
<Sleaker>
not set
19:15
<vagrantc>
try it
19:16
<Sleaker>
had XSERVER=vesa, but just commented that out.
19:16
<vagrantc>
let me check to make sure i've got it right
19:16
!smart
19:16
<ltsp`>
I do not know about 'smart', but I do know about these similar topics: 'socat', 'story', 'sugar'
19:16
<vagrantc>
X_SMART_COLOR_DEPTH=False
19:16
sorry
19:17
<mwalters>
!story
19:17
<ltsp`>
story: see: !worldmap
19:17
<mwalters>
!sugar
19:17
<ltsp`>
sugar: for anyone curious, this is how to get sugar, ejabberd and collaboration working perfectly on LTSP: http://www.nubae.com/sugar-on-ltsp-ubuntu-intrepid-ibex
19:17
<mwalters>
intrepid...
19:17
:D
19:17
<vagrantc>
heh
19:18
<mwalters>
I ran intrepid on... a Dell X1!
19:18
<vagrantc>
much of LTSP is quite dated :)
19:18
<mwalters>
maybe it was 9.04
19:18
<vagrantc>
on the one hand, it largely continues to work ... though mostly thanks to alkisg
19:18
<mwalters>
:D
19:18
<Sleaker>
yah, I was pretty happy that the ltsp4.2 stuff we have 'just works' still
19:19
<vagrantc>
before my time :)
19:19
<Sleaker>
all I had to do was update the dhcpd conf and move some config files into new locations.
19:19
I mean.. all of this was before my time too
19:19
<vagrantc>
Sleaker: i think that project was the most i'd ever worked with ltsp generations before ltsp 5 :)
19:20
<Sleaker>
yay legacy base :D
19:20
oh really?
19:20
<vagrantc>
yeah, i pretty much got involved with LTSP once they went to what essentially became LTSP 5
19:20
<Sleaker>
i ran my own pxe boot server at home for a long time, so it was really easy to figure the 4.2 stuff out.
19:20
<vagrantc>
before that i had my own network booted system project
19:20
<Sleaker>
pretty straightforward.
19:46
vagrantc: not sure if it changes much, but the server is running lightdm and I'm trying to get clients working over xdmcp
19:49
<vagrantc>
i don't know that lightdm existed last time i tried xdmcp...
19:50
<Sleaker>
it's what we had on our previous setup
19:50
<vagrantc>
oh, it's been a while :)
19:50
<Sleaker>
haha yah.
19:51
<vagrantc>
xdmcp has grown increasingly neglected over the years ... ltsp 5 only had basic support for it
19:51
<alkisg>
Sleaker: what's the output of sudo ltsp-info | nc termbin.com 9999 ?
19:51
<Sleaker>
alkisg: from a client?
19:52
<alkisg>
No, the server
19:53
<Sleaker>
http://termbin.com/qw3z
19:53
also I find it interesting that it pulls the wrong lts.conf
19:53
<alkisg>
Where are the chroots?
19:54
<Sleaker>
that is definitely not the one that is getting downloaded by the client since they are amd64 and it's getting served from /srv/tftp
19:54
/opt/isi/ltsp5/images/isi-amd64.img
19:54
the i386 dir is the ltsp42 setup
19:55
<vagrantc>
Sleaker: isi-amd64.img is built and packaged, if i remember?
19:55
<alkisg>
The image you're trying to boot, is it stretch? And, thin or fat?
19:55
<Sleaker>
vagrantc: I rebuilt it.
19:55
<vagrantc>
so, on the live server, there's no chroot?
19:55
<Sleaker>
correct.
19:55
I'm rebuilding an image on a separate build server and then installing it on the box.
19:56
alkisg: thin.
19:56
<alkisg>
stretch thin?
19:56
<Sleaker>
correct
19:56
I could probably try dumping the old image on there and see if it has the same thing actually
19:56
<alkisg>
And you did try the X_SMART_COLOR_DEPTH=False directive?
19:56
<Sleaker>
trying it now
19:57
<vagrantc>
Sleaker: you had variety of clients that all had some interesting quirks ... trying to update to support newer clients, or just a general refresh?
19:57
<Sleaker>
the newer TCs we have are all zbox 320/323 nanos
19:58
all the old TCs boot using the old 42 method
20:01
welp we got there
20:01
login screen :D
20:01
<alkisg>
Heh, vagrant proposed that 40 mins ago :D (10:16:49 PM) vagrantc: X_SMART_COLOR_DEPTH=False
20:02woernie_ has left IRC (woernie_!~werner@x4db411d6.dyn.telefonica.de, Remote host closed the connection)
20:02
<Sleaker>
alkisg: yah wanted to bake it into a deb package along with me turning off a read-edid script he had written for us too. wanted to pair down anything running in between when it was laucnhing stuff.
20:02
cool
20:03
seems pretty slow though. might need to turn vesa back on haha
20:03
<alkisg>
So your thin clients have a couple of GB RAM, and an atom processor, yet you're working them as thin, not fats?
20:03
How so?
20:04
<Sleaker>
alkisg: we don't get them with HDs built internally.
20:04
<alkisg>
No, ltsp fat clients are diskless
20:04
!fatclients
20:04
<ltsp`>
fatclients: Nowadays LTSP supports thin and fat clients. They are both diskless and netbooted from the same LTSP chroot, but while thin clients run the session on the server and transfer the screen, fat clients run the session locally with their own CPU/RAM, thus performing amazingly better. See also !ltsp-pnp and https://help.ubuntu.com/community/UbuntuLTSP/FatClients
20:04
<Sleaker>
ah, I probably need to swap to fat client then
20:04
or look at it.
20:04
<alkisg>
What are the exact cpu/ram specs?
20:05
<Sleaker>
alkisg: our software stack need to run off the server though.
20:05
<alkisg>
You can use remoteapps for a few apps if you want
20:05
<Sleaker>
not like a few..
20:05
<alkisg>
If you do want the session on the server, then go for thins
20:05
<Sleaker>
might be more problematic, but I can try it out.
20:06
but yah, we have a bunch of apps that require talking to a flatfile database on the local server.
20:06
so thin client was always just architecturally where we went.
20:06
<alkisg>
If it's already multiuser enabled, they could also access it via sshfs
20:06
<Sleaker>
it's not.
20:06
well...
20:07
it's complicated :P
20:07
<alkisg>
How does it run with multiple thin client users then?
20:07
Haha
20:07
OK
20:07
<Sleaker>
I could probably write a wrapper app that sshd into the box and displayed the application, but that would only get like partway there.
20:07
and wouldn't work for where we are going in the future.
20:08
<alkisg>
Fat clients are already using ssh and sshfs
20:08
<Sleaker>
yup
20:08
<alkisg>
Usually wrapper apps are not needed
20:08
<Sleaker>
app constraints.
20:08
I'll look into it, but probably will cause problems.
20:08
<alkisg>
Just LOCALAPPS_EXTRAMOUNTS=/srv/the-required-dir, to forward the database dir
20:08
np; sounds like your setup is complicated, so you know better :)
20:09
<Sleaker>
https://www.zotac.com/dk/product/mini_pcs/zbox-ci323-nano#spec
20:09
but yah the TCs are powerful enough to be fats.
20:09
our support department replaced all the tech computers with them :P
20:09
<alkisg>
up to 8GB RAM => doesn't say
20:10
<Sleaker>
oh I think we ship them with 2gb
20:10
<alkisg>
Good enough for fats, yeah
20:11
<mwalters>
I still think 4-8 is best for chrome/chromium :P
20:11
<Sleaker>
accurate
20:11
we played around with local apps.
20:11
2gb was fine for chromium.
20:12
<mwalters>
our agency document management is a webapp... but we're also a gSuite shop... we have a few tabs open on each box, usually ;)
20:12
<Sleaker>
but then we're comparing a server system with only 8GB of ram running 2-4 TCs to running the browser on the TC via local app.
20:12
alkisg: on the slowness thing, it was rendering white boxes on the screen all over and not refreshing it quickly.
20:12
like X was only updating part of the screen at a time and slowly.
20:13
<alkisg>
Eh, thin clients have a lot of issues nowadays
20:13
Xorg doesn't care much for its remote implementation
20:13
<Sleaker>
host system is an i7-6700 w/ 16GB
20:29
<vagrantc>
Sleaker: i seem to recall issues where the app you needed to run also called other apps, and basically everything ended up running on the server
20:29
<Sleaker>
vagrantc: yup
20:29
<vagrantc>
so even if you did remote apps for that one thing, it would end up running everything remotely...
20:30
<Sleaker>
yup
20:30
<vagrantc>
everything except the window manager, anyways... which maybe that would still take some load off the server
20:38
<Sleaker>
on the bright side, I got the ltsp boot image generation all automated in our build process now. which makes it a lot easier to deal with
20:38
<vagrantc>
nice
20:39
<Sleaker>
oh hmm, something changed, rebooted and no just at a blank screen lol.
20:41
<vagrantc>
is it maybe not actually reading the lts.conf ?
20:42
<Sleaker>
nah /etc/lts.conf on the TC matches the one on the server
20:42
and it changes if I reboot the TC after changing the server one.
20:43
that was the first thing I started with. cause I wasn't 100% on where it was supposed to go
20:43
<vagrantc>
right
20:45
Sleaker: i just realized from your paste, you're working on a stretch/9 system ... i don't know what your timeline is, but buster/10 is likely to release in a few months
20:45
<Sleaker>
yup
20:45
<vagrantc>
would give you a longer support cycle ... if it works
20:45
<Sleaker>
I think I have everything to a point where I can just download all the packages and have it just work.
20:46
took a lot of time removing all of the os-specific stuff we have and making it detect the os name automatically so I can just build a buster image when ready
20:46
<vagrantc>
cool
20:46
<Sleaker>
we still had code referencing valhalla.
20:47
old-school redhat codename :P
20:47
<vagrantc>
heh
20:47
even older school norse mythology!
20:58GodFather has joined IRC (GodFather!~rcc@143.59.184.72)
21:05kjackal has left IRC (kjackal!~quassel@ppp-2-84-244-151.home.otenet.gr, Ping timeout: 245 seconds)
21:19
<Sleaker>
also, yah switched over to debian on this next go around. I've not been a huge fan of ubuntu while we've been using it.
22:08ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
23:14Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
23:56
<Sleaker>
mkay we working again. now time to see if a reboot breaks it lol
23:57
had to modprobe i2c-dev for get-edid to work.
23:59
hmm so after rebooting the TC it doesn't appear to be able to get back to the login screen