|09:02||ltsp has joined IRC (email@example.com)|
|09:06||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|09:11||kjackal_v2 has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|09:18||kjackal has joined IRC (kjackal!~quassel@2a02:587:3107:2e00:456:a28d:6293:36fe)|
|09:25||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
The ltsp.org server had 0% free space and didn't work anymore; I freed up some space and put a banner mentioning the new ltsp and site
Ugly banner, I didn't want to brain-switch to HTML again :P
no that works just fine
dnsmasq fails on ubuntu 18.04 because of systemd-resolved occupying the port, should I just disable the latter?
oh never mind it just does that during package installation
|12:03||section1 has joined IRC (email@example.com)|
well then, let's try and boot a ws
|12:17||Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)|
alright, hyperv uefi boot worked
ipxe hangs on an old lenovo desktop but that's probably because the undi firmware hasnt been updated for 10 years
|12:30||Renato has joined IRC (Renatofirstname.lastname@example.org)|
|12:32||Renato has left IRC (Renatoemail@example.com, Remote host closed the connection)|
welp, a dell booted just fine
sounds works, youtube works, all great
|13:38||gdi2k_ has joined IRC (firstname.lastname@example.org)|
|13:40||gdi2k has left IRC (email@example.com, Ping timeout: 264 seconds)|
meo: download boot.ipxe.org/ipxe.pxe OVER undionly.ipxe
alkisg: I'll try to patch the box first
I mean it's literally more than a decade old
and technically isn't my target platform
meo, sure, btw explanation in https://github.com/ltsp/ltsp/issues/29
i have a physical Dell box booted and working nicely, so now I need to figure out the customisations I'll need in production
|14:01||lucascastro has joined IRC (firstname.lastname@example.org)|
|14:13||tbayen has joined IRC (email@example.com)|
Hi Folks! I think I found a bug (and a solution). What is the best way to draw attention of a developer who can check what I think?
tbayen: shoot, which one?
send beer to alkisg ... with a letter ;)
Ah. Beer is my very specialty.
After upgrading an some years old system (debian squeezy) to debian buster my browser did not have sound any more. I started chromium as a localapp. It seems that the actual ltsp scripts do not give the sound environment to localapps.
I now use the debian package ltsp-client 5.18.12-3
tbayen: ah, the old ltsp isn't really actively maintained anymore
try the new one
install: To install LTSP19+: https://github.com/ltsp/ltsp/wiki/installation. To install LTSP5: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
My solution is to chnange two lines that do the actual call of the app and add $MY_SOUND to both of them.
tbayen: so, you could report the issue to the old ltsp5 bug tracker, but noone would really work on it, or you could use the new ltsp :)
Hm. ok. That is like a fork, isn't it? And you are not able to announce that on the original site?
tbayen: nope, I'm the main developer, this is the new ltsp, the old one will be removed from debian/ubuntu and the new one will be uploaded, and see the big banner in ltsp.org about it
(also, around 50 messages in the ltsp mailing list about it :))
It just wasn't ready in time for buster, it will be for bullseye
OK. I am working on that for some hours. And I really opened this page lie ten times to look for something. The banner is yellow and red. - I f* did not see it. Hahahaha! Thanks
yeah the ltsp5 vs ltsp 19 really needs to be like in channel /notice or something
tbayen: the banner's only been up for a couple of hours
To be honest, I uploaded the banner 4-5 hours ago :D
After meo pointed it out
At the moment I like to stay with the stable buster system. We are doing business with the system and do not like experiments. But good to know. :-) I like to change to the new one with our next internal upgrade cycle.
Thanks for doing this work! :-) Especially if you have been also a developer at the old version. LTSP is a great tool and works flawless most of the time.
Sure. It's not an experiment though, it's already more stable; but less mature (i.e. more frequent changes)
Yes, I've been the main developer for a lot of years now, in the old one too; when the other major developers like ogra left the boat for other places :D
i'm still a passenger (kind of) i never really left the boat !
(but yeah, i stopped working in the engine room a long time ago :)
|14:33||uk has joined IRC (firstname.lastname@example.org)|
Thanks to explain that.
I read your announcement. It answers some of my first questions.
Why do you call localapps "deprecated"?
Because we only use localapps now
It's called "fat clients"
(like live cds do, only with remote home and root)
OK. Thanks. Sounds like more expensive client devices. I will think about what that means for our company's setup.
Yes, note that ltsp5 has also been recommending that for 10+ years now
as xorg, opengl etc etc don't really focus on the "remote part" anymore, so it's causing a lot of issues that ltsp can't overcome
So "fat clients" have the same requirements as "normal clients", except for the disk
|15:00||tbayen has left IRC (email@example.com, Remote host closed the connection)|
|15:01||tbayen has joined IRC (firstname.lastname@example.org)|
|15:02||shored has left IRC (email@example.com, Read error: Connection reset by peer)|
|15:02||shored has joined IRC (firstname.lastname@example.org)|
|15:10||woernie has left IRC (email@example.com, Remote host closed the connection)|
|15:52||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|15:52||shored has left IRC (firstname.lastname@example.org, Read error: Connection reset by peer)|
|15:52||shored has joined IRC (email@example.com)|
|16:33||josefig has left IRC (firstname.lastname@example.org, Quit: The Lounge - https://thelounge.chat)|
|18:28||lucascastro has left IRC (email@example.com, Remote host closed the connection)|
alkisg: I gotta say, your bash code is art
meo: thanks! :)
I loved the "re" trick, it halts execution and tells you which exact command failed
Troubleshooting ltsp5 => 1 hour, ltsp19 => 1 minute :)
this should be like a standard framework for complex shell interfaces
|19:22||yanu has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|19:23||yanu has joined IRC (email@example.com)|
|19:53||Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)|
|20:01||section1 has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|20:19||tbayen has left IRC (email@example.com, Remote host closed the connection)|
|20:27||statler has left IRC (statler!~Georg@p54897245.dip0.t-ipconnect.de, Remote host closed the connection)|
|21:17||lucascastro has joined IRC (firstname.lastname@example.org)|
|21:53||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|23:41||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|23:45||dsjii has joined IRC (dsjii!~david@2600:380:9f3c:f08d:68db:caff:fe86:8f41)|
Is Jim around?