|05:39||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|05:50||ltspbot has joined IRC (email@example.com)|
|06:10||woernie has joined IRC (firstname.lastname@example.org)|
|06:45||calher has joined IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181)|
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?
If I disconnect, leave me a message with MemoServ.
Could I install the software inside a Debian container and still use it to access the Fedora host?
calher: There are a couple of persons interested in porting ltsp to fedora
I can give some advice, but I don't have time currently to help more
Let me point you to the github issue about this...
That's fine. It's actually time to sleep, but I am wide awake.
I saw. :(
Currently, it should be easy to use ltsp server in fedora, with debian chroot ltsp clients
But fedora ltsp clients will need some work
Eh, it's up to you :)
I can't do everything, whoever wants fedora etc, just do it
I don't have a lot of money, but I am willing to donate to this endeavor.
pull requests welcome :D
You can mention that in that github issue too
Right. I will.
In a month or so I'll have a bit of free time, I could do it then if the community sponsored some time
(or if someone else wants to do it, I could give some advice, etc etc)
I heard these are fat clients and not thin clients.
Thin clients do not exist anymore, there's only "remote desktop" now
And ltsp does support that
I.e. ltsp clients get netbooted with a minimal OS, and they run rdp/x2go/vnc/whatever to connect to the server
That's more or less what I wanted.
Eh just use a debian minimal chroot then, in your existing fedora server
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:48||calher has left IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181, Ping timeout: 246 seconds)|
|07:49||calher has joined IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181)|
|08:03||calher has left IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181, Quit: Ping timeout (120 seconds))|
|08:04||calher has joined IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181)|
|08:14||calher has left IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181, Ping timeout: 246 seconds)|
|08:27||calher has joined IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181)|
|08:28||calher has left IRC (calher!~calher@2605:a601:ae7b:a400:71:c60b:22c1:2181, Client Quit)|
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
fiesh: verify that /lib/modules/5.10.49-gentoo-r1 does exist in the image
the kernel is fully self-contained, the previous image didn't need modules either
maybe it's also a dracut issue, it might have been updated
dracut Warning: Coult not boot.
it says /dev/root does not exist... but it doesn't exist on the working setup either
well I'm dumbfounded.. both the working and the non-working initramfs only contain early_cpio and the amd and intel microcodes
and the kernel config is almost precisely the same, except for minor differences incurred by the newer version of the kernel
or maybe this here is messing with me: https://www.gentoo.org/support/news-items/2021-07-15-opentmpfiles-deprecation.html
but it seems unlikely, not related to devices I guess
hmm actually, it seems to be a network issue
that the client's network isn't working
omg, I think I know what it is
it's the glibc + dhcp + -O3 = bad UDP checksum bug again that I already painfully encountered on our server
now in dhclient
hurray, that was it
[ ] that was easy
|13:47||woernie has left IRC (email@example.com, Ping timeout: 256 seconds)|
|13:48||woernie has joined IRC (firstname.lastname@example.org)|
So, a recompilation without -O3 was needed?
|14:44||woernie has left IRC (email@example.com, Ping timeout: 258 seconds)|
|14:44||woernie has joined IRC (firstname.lastname@example.org)|
|15:05||woernie has left IRC (email@example.com, Remote host closed the connection)|
|15:05||woernie has joined IRC (firstname.lastname@example.org)|
|18:07||ltspnoob has joined IRC (email@example.com)|
|18:11||vagrantc has joined IRC (firstname.lastname@example.org)|
|18:12||vagrantc has left IRC (email@example.com, Client Quit)|
|18:14||ltspnoob has left IRC (firstname.lastname@example.org, Quit: Client closed)|
|18:14||ltspnoob has joined IRC (email@example.com)|
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"
Nope. Which distro/version/desktop environment?
Also try to log in in vt2 when that happens
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"
LTSP server: Ubuntu 20.04LTS, client image: custom chroot with Ubuntu 20.04LTS
vt2 login works , with the user's login & password
On the LTSP server side: in the auth.log. I do see the following logs:
Jul 20 11:20:15 ltsp-testsvr sshd: Accepted password for tester from 192.168.1.190 port 41122 ssh2
Jul 20 11:20:15 ltsp-testsvr sshd: pam_unix(sshd:session): session opened for user tester by (uid=0)
Jul 20 11:20:15 ltsp-testsvr systemd-logind: New session 273 of user tester.
Jul 20 11:20:16 ltsp-testsvr sshd: Received disconnect from 192.168.1.190 port 41122:11: disconnected by user
Jul 20 11:20:16 ltsp-testsvr sshd: Disconnected from user tester 192.168.1.190 port 41122
Jul 20 11:20:16 ltsp-testsvr sshd: pam_unix(sshd:session): session closed for user tester
Jul 20 11:20:16 ltsp-testsvr systemd-logind: Session 273 logged out. Waiting for processes to exit.
Jul 20 11:20:16 ltsp-testsvr systemd-logind: Removed session 273.
It seems that the initial 'login' after the correct password was entered, it succeeded, but then, somehow..the client disconnected...
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:39||vagrantc has joined IRC (firstname.lastname@example.org)|
ltspnoob: do you have customized pam configuration, or the stock one?
I did test gnome/gdm3 etc, but I'm not sure if I tested screen unlocking or not
stock one. I haven't changed anything in the pam config in the server or the custom chroot environment.
Can you open a question in ltsp discussions?
I do not know about 'discus', but I do know about these similar topics: 'discussions', 'ltsp-discuss'
discussions: You can also ask questions about LTSP in its github discussions: https://github.com/ltsp/ltsp/discussions
ah ic. thanks. will do!
|18:45||vagrantc has left IRC (email@example.com, Ping timeout: 252 seconds)|
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
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...)
LTSP now doesn't handle sessions, they're handled normally by DMs
So if it's installed in the chroot, it should show up
Like it does in local installations...
ok. thanks for the info! I guess Ubuntu disabled the choice with the ubuntu-desktop package...
I think you first select the user and then a gear shows up
Not using gnome though..
|19:07||mistik1 has joined IRC (firstname.lastname@example.org)|
What DM/WM do you use or recommend (ie. light weight and works in LTSP clients)?
I've been using mate for years, now I'm planning to switch to kde
As recent kde is actually lighter than mate
|19:09||* muhwalt 's ears perk up|
Oh?! I see. good to know.. I will try KDE on this chroot image in a bit...
KDE... light... up is down, down is up... ;)
Question: How do I specify an extra NFS mount point for the clients after boot up? in LTSP server's /etc/ltsp/ltsp.conf ?
lol @muhwalt maybe the new version really 'lightens up'...
To be fair, I haven't tried KDE for years... probably 2016ish.
I've mostly been using i3... which is about as light as it gets ;)
I see. I don't know about/never used i3...
for me personally. I wouldn't dare try to make our employees use it. It's a tiling window manager using mostly keyboard shortcuts
lots of kde apps using things like qtquick, to make the apps mobile capable
cant have chunky on mobile
agreed - no chunky on mobile
Question: after updating /etc/ltsp/ltsp.conf .. do I need to run some command to make the changes active?
for client images
`ltsp initrd` I think
ah ok. thank you!
|19:30||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|19:35||vagrantc has joined IRC (email@example.com)|
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:40||lucascastro has left IRC (firstname.lastname@example.org, Ping timeout: 265 seconds)|
and update: Metacity's lock screen login still doesn't work after the full installation of ubuntu-desktop pacakge
Try to see its logs
Maybe in .xsession-errors
E.g. maybe you're missing something in the chroot
ah, thanks for the hint! ... noob question.. where is the .xsession-errors? '=D in the server or the client side?
Both server and client should have it
|19:49||vagrantc has left IRC (email@example.com, Ping timeout: 268 seconds)|
|19:49||vagrantc has joined IRC (firstname.lastname@example.org)|
hmm.. /home/tester/.xsession-errors is 0 byte... I tried rebooting the client and did the lock-unlock process again.. no log..
You could override metacity with a shell script that redirects its stderr to a file, but it's a bit harder
hmm.. like this?
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:29||vagrantc has left IRC (email@example.com, Ping timeout: 255 seconds)|
|20:29||vagrantc has joined IRC (firstname.lastname@example.org)|
Yup. Although, also check with `ps` (from vt2) if lockscreen is a separate executable
I have checked from vt2, and there is no separate process/executable for the lockscreen.. :(
I have submitted a discussion on github re. this issue.
ltspnoob: also try it in a normal installation
If it's not an ltsp issue, there's no point in trying to solve it in ltsp
|21:14||vagrantc has left IRC (email@example.com, Ping timeout: 255 seconds)|
|21:16||vagrantc has joined IRC (firstname.lastname@example.org)|
ltspnoob: actually, just add a new local user while the client is running, and test with that one
I think even just running `passwd` would disable pamltsp and it would use local shadow authentication
ok. let me try that
|21:42||vagrantc has left IRC (email@example.com, Quit: leaving)|
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:13||mistik1 has left IRC (firstname.lastname@example.org, Ping timeout: 268 seconds)|
Questin: what is the proper way for syncing the LTSP server's /etc/passwd, /etc/group files to the chroot client image?
|22:28||lucascastro has joined IRC (email@example.com)|