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


Channel log from 20 July 2021   (all times are UTC)

05:39ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
05:50ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr)
06:10woernie has joined IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de)
06:45calher has joined IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181)
06:47
<calher>
Hi. I am looking to have thin clients for my Fedora system, but I see you only support Ubuntu. Is there anything I can do to get it running on Fedora?
06:48
If I disconnect, leave me a message with MemoServ.
06:53
Could I install the software inside a Debian container and still use it to access the Fedora host?
06:53
<alkisg>
Hello
06:53
calher: There are a couple of persons interested in porting ltsp to fedora
06:53
I can give some advice, but I don't have time currently to help more
06:54
Let me point you to the github issue about this...
06:54
<calher>
That's fine. It's actually time to sleep, but I am wide awake.
06:54
<alkisg>
https://github.com/ltsp/ltsp/discussions/197
06:54
<calher>
I saw. :(
06:55
<alkisg>
Currently, it should be easy to use ltsp server in fedora, with debian chroot ltsp clients
06:55
But fedora ltsp clients will need some work
06:56
<calher>
Sad.
06:56
<alkisg>
Eh, it's up to you :)
06:56
I can't do everything, whoever wants fedora etc, just do it
06:56
<calher>
I don't have a lot of money, but I am willing to donate to this endeavor.
06:57
<alkisg>
pull requests welcome :D
06:57
You can mention that in that github issue too
06:57
<calher>
Right. I will.
06:57
<alkisg>
In a month or so I'll have a bit of free time, I could do it then if the community sponsored some time
06:58
(or if someone else wants to do it, I could give some advice, etc etc)
06:58
<calher>
I heard these are fat clients and not thin clients.
06:59
<alkisg>
Thin clients do not exist anymore, there's only "remote desktop" now
06:59
And ltsp does support that
07:00
I.e. ltsp clients get netbooted with a minimal OS, and they run rdp/x2go/vnc/whatever to connect to the server
07:00
<calher>
That's more or less what I wanted.
07:00
Cool.
07:00
<alkisg>
Eh just use a debian minimal chroot then, in your existing fedora server
07:03
<calher>
The only good machine that runs Libreboot is a very expensive and powerful computer, so this will help a lot. Thank you. (I'll try the Debian thing.)
07:48calher has left IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181, Ping timeout: 246 seconds)
07:49calher has joined IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181)
08:03calher has left IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181, Quit: Ping timeout (120 seconds))
08:04calher has joined IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181)
08:14calher has left IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181, Ping timeout: 246 seconds)
08:27calher has joined IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181)
08:28calher has left IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181, Client Quit)
08:46
<fiesh>
hmm updating from 5.10.27-gentoo to 5.10.49-gentoo-r1 makes our clients not boot since they can't find the (nbd) root any more... gotta investigate, seems odd that this would happen with such a minor update
09:44
<alkisg>
fiesh: verify that /lib/modules/5.10.49-gentoo-r1 does exist in the image
09:46
<fiesh>
the kernel is fully self-contained, the previous image didn't need modules either
09:46
maybe it's also a dracut issue, it might have been updated
09:47
dracut Warning: Coult not boot.
09:47
Could
09:47
hmm
09:55
it says /dev/root does not exist... but it doesn't exist on the working setup either
09:56
well I'm dumbfounded.. both the working and the non-working initramfs only contain early_cpio and the amd and intel microcodes
09:57
and the kernel config is almost precisely the same, except for minor differences incurred by the newer version of the kernel
10:13
or maybe this here is messing with me: https://www.gentoo.org/support/news-items/2021-07-15-opentmpfiles-deprecation.html
10:13
but it seems unlikely, not related to devices I guess
10:21
hmm actually, it seems to be a network issue
10:21
that the client's network isn't working
11:56
omg, I think I know what it is
11:57
it's the glibc + dhcp + -O3 = bad UDP checksum bug again that I already painfully encountered on our server
11:57
now in dhclient
12:12
hurray, that was it
12:12
[ ] that was easy
13:47woernie has left IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de, Ping timeout: 256 seconds)
13:48woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de)
14:17
<alkisg>
So, a recompilation without -O3 was needed?
14:44woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 258 seconds)
14:44woernie has joined IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de)
15:05woernie has left IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de, Remote host closed the connection)
15:05woernie has joined IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de)
18:07ltspnoob has joined IRC (ltspnoob!~ltspnoob@riddle.wizard.ca)
18:10
<ltspnoob>
hello everyone
18:11vagrantc has joined IRC (vagrantc!~vagrant@170.173.8.12)
18:12vagrantc has left IRC (vagrantc!~vagrant@170.173.8.12, Client Quit)
18:14ltspnoob has left IRC (ltspnoob!~ltspnoob@riddle.wizard.ca, Quit: Client closed)
18:14ltspnoob has joined IRC (ltspnoob!~ltspnoob@riddle.wizard.ca)
18:18
<ltspnoob>
has anyone had problems with the client's screen going into locked mode and then password entered doesn't unlock? (and the error message only shows "Sorry, that didn't work. Please try again"
18:18
<alkisg>
Nope. Which distro/version/desktop environment?
18:19
Also try to log in in vt2 when that happens
18:19
<ltspnoob>
If one enters the wrong password on purpose at the unlock screen, it would show ".Login incorrect." and then "Sorry, that didn't work.Please try again"
18:19
LTSP server: Ubuntu 20.04LTS, client image: custom chroot with Ubuntu 20.04LTS
18:20
vt2 login works , with the user's login & password
18:21
On the LTSP server side: in the auth.log. I do see the following logs:
18:21
Jul 20 11:20:15 ltsp-testsvr sshd[64719]: Accepted password for tester from 192.168.1.190 port 41122 ssh2
18:21
Jul 20 11:20:15 ltsp-testsvr sshd[64719]: pam_unix(sshd:session): session opened for user tester by (uid=0)
18:21
Jul 20 11:20:15 ltsp-testsvr systemd-logind[471]: New session 273 of user tester.
18:21
Jul 20 11:20:16 ltsp-testsvr sshd[64784]: Received disconnect from 192.168.1.190 port 41122:11: disconnected by user
18:21
Jul 20 11:20:16 ltsp-testsvr sshd[64784]: Disconnected from user tester 192.168.1.190 port 41122
18:21
Jul 20 11:20:16 ltsp-testsvr sshd[64719]: pam_unix(sshd:session): session closed for user tester
18:21
Jul 20 11:20:16 ltsp-testsvr systemd-logind[471]: Session 273 logged out. Waiting for processes to exit.
18:21
Jul 20 11:20:16 ltsp-testsvr systemd-logind[471]: Removed session 273.
18:23
It seems that the initial 'login' after the correct password was entered, it succeeded, but then, somehow..the client disconnected...
18:28
client desktop: gdm3 with Metacity ... LTSP version ..exactly which version I don't know.. I guess ...whatever version from the PPA repo as instructed on the ltsp.org's Installation pages
18:39vagrantc has joined IRC (vagrantc!~vagrant@cascadia.aikidev.net)
18:41
<alkisg>
ltspnoob: do you have customized pam configuration, or the stock one?
18:42
I did test gnome/gdm3 etc, but I'm not sure if I tested screen unlocking or not
18:42
<ltspnoob>
stock one. I haven't changed anything in the pam config in the server or the custom chroot environment.
18:42
<alkisg>
Can you open a question in ltsp discussions?
18:42
!discus
18:42
<ltspbot>
I do not know about 'discus', but I do know about these similar topics: 'discussions', 'ltsp-discuss'
18:42
<alkisg>
!discussions
18:42
<ltspbot>
discussions: You can also ask questions about LTSP in its github discussions: https://github.com/ltsp/ltsp/discussions
18:42
<ltspnoob>
ah ic. thanks. will do!
18:45vagrantc has left IRC (vagrantc!~vagrant@cascadia.aikidev.net, Ping timeout: 252 seconds)
18:48
<ltspnoob>
oh.. some updates: I decided to try installing the full "ubuntu-desktop" package in the client chroot image.. screen lock's unlocking works with this different gui interface
18:50
question: how come there is no option to select "Metacity" on the initial login page even though I still have Metacity installed? (I remember in the old LTSP5.. you get to choose a different desktop manager at the bottom right corner...)
18:56
<alkisg>
LTSP now doesn't handle sessions, they're handled normally by DMs
18:56
So if it's installed in the chroot, it should show up
18:56
Like it does in local installations...
19:01
<ltspnoob>
ok. thanks for the info! I guess Ubuntu disabled the choice with the ubuntu-desktop package...
19:07
<alkisg>
I think you first select the user and then a gear shows up
19:07
Not using gnome though..
19:07mistik1 has joined IRC (mistik1!~mistik1@96.43.180.110)
19:09
<ltspnoob>
What DM/WM do you use or recommend (ie. light weight and works in LTSP clients)?
19:09
<alkisg>
I've been using mate for years, now I'm planning to switch to kde
19:09
As recent kde is actually lighter than mate
19:09* muhwalt 's ears perk up
19:10
<ltspnoob>
Oh?! I see. good to know.. I will try KDE on this chroot image in a bit...
19:10
<muhwalt>
KDE... light... up is down, down is up... ;)
19:11
<ltspnoob>
Question: How do I specify an extra NFS mount point for the clients after boot up? in LTSP server's /etc/ltsp/ltsp.conf ?
19:12
lol @muhwalt maybe the new version really 'lightens up'...
19:12
<muhwalt>
To be fair, I haven't tried KDE for years... probably 2016ish.
19:12
I've mostly been using i3... which is about as light as it gets ;)
19:14
<ltspnoob>
I see. I don't know about/never used i3...
19:15
<muhwalt>
for me personally. I wouldn't dare try to make our employees use it. It's a tiling window manager using mostly keyboard shortcuts
19:17
<mistik1>
lots of kde apps using things like qtquick, to make the apps mobile capable
19:17
cant have chunky on mobile
19:25
<ltspnoob>
agreed - no chunky on mobile
19:26
Question: after updating /etc/ltsp/ltsp.conf .. do I need to run some command to make the changes active?
19:26
for client images
19:26
<muhwalt>
`ltsp initrd` I think
19:26
<ltspnoob>
ah ok. thank you!
19:30ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
19:35vagrantc has joined IRC (vagrantc!~vagrant@cascadia.aikidev.net)
19:36
<ltspnoob>
FYI/Update! I found the little gear icon for changing the WM .. on the main login page: normally , it does not show up; the small gear icon at the bottom right corner only shows up when you click on a user to login with!
19:37
thanks @alkisg
19:40
<alkisg>
:)
19:40lucascastro has left IRC (lucascastro!~lucascast@177-185-133-236.dynamic.isotelco.net.br, Ping timeout: 265 seconds)
19:40
<ltspnoob>
and update: Metacity's lock screen login still doesn't work after the full installation of ubuntu-desktop pacakge
19:40
<alkisg>
Try to see its logs
19:40
Maybe in .xsession-errors
19:40
E.g. maybe you're missing something in the chroot
19:42
<ltspnoob>
ah, thanks for the hint! ... noob question.. where is the .xsession-errors? '=D in the server or the client side?
19:43
<alkisg>
In /home/user/.xsession-errors
19:43
Both server and client should have it
19:49vagrantc has left IRC (vagrantc!~vagrant@cascadia.aikidev.net, Ping timeout: 268 seconds)
19:49vagrantc has joined IRC (vagrantc!~vagrant@170.173.8.12)
19:56
<ltspnoob>
hmm.. /home/tester/.xsession-errors is 0 byte... I tried rebooting the client and did the lock-unlock process again.. no log..
20:02
<alkisg>
You could override metacity with a shell script that redirects its stderr to a file, but it's a bit harder
20:06
<ltspnoob>
hmm.. like this?
20:08
mv /usr/bin/metacity /usr/bin/metacity.bin ; echo "/usr/bin/metacity.bin $@ 2>&1 >/tmp/metacity.log " > /usr/bin/metacity ; chmod +x /usr/bin/metacity
20:29vagrantc has left IRC (vagrantc!~vagrant@170.173.8.12, Ping timeout: 255 seconds)
20:29vagrantc has joined IRC (vagrantc!~vagrant@cascadia.aikidev.net)
20:31
<alkisg>
Yup. Although, also check with `ps` (from vt2) if lockscreen is a separate executable
20:36
<ltspnoob>
I have checked from vt2, and there is no separate process/executable for the lockscreen.. :(
20:45
I have submitted a discussion on github re. this issue.
20:54
<alkisg>
ltspnoob: also try it in a normal installation
20:54
If it's not an ltsp issue, there's no point in trying to solve it in ltsp
21:14vagrantc has left IRC (vagrantc!~vagrant@cascadia.aikidev.net, Ping timeout: 255 seconds)
21:16vagrantc has joined IRC (vagrantc!~vagrant@170.173.8.12)
21:21
<alkisg>
ltspnoob: actually, just add a new local user while the client is running, and test with that one
21:22
I think even just running `passwd` would disable pamltsp and it would use local shadow authentication
21:23
<ltspnoob>
ok. let me try that
21:42vagrantc has left IRC (vagrantc!~vagrant@170.173.8.12, Quit: leaving)
22:08
<ltspnoob>
adding a local user in the client machine for testing, with the local user's password updated locally with passwd as well (confirmed with checking /etc/shadow) , and then, the newly created local user can't be used to login with Metacity. It screen goes blank and after while.. goes back to the users listing login screen
22:13mistik1 has left IRC (mistik1!~mistik1@96.43.180.110, Ping timeout: 268 seconds)
22:20
<ltspnoob>
Questin: what is the proper way for syncing the LTSP server's /etc/passwd, /etc/group files to the chroot client image?
22:28lucascastro has joined IRC (lucascastro!~lucascast@189.90.44.253.jupiter.com.br)