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

Request log from specific day:

Channel log from 26 June 2023 (all times are UTC)

02:18	vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50, Quit: leaving)
05:30	ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:02	woernie has joined IRC (woernie!~werner@pd9e8b418.dip0.t-ipconnect.de)
06:17	woernie has left IRC (woernie!~werner@pd9e8b418.dip0.t-ipconnect.de, Ping timeout: 260 seconds)
06:51	woernie has joined IRC (woernie!~werner@pd9e8b418.dip0.t-ipconnect.de)
07:06	alkisg_irc1 has joined IRC (alkisg_irc1!~Thunderbi@srv1-dide.ioa.sch.gr)
07:08	alkisg_irc has left IRC (alkisg_irc!~Thunderbi@2a02:587:745c:3500:9ea2:f4ff:feb9:a8b0, Ping timeout: 240 seconds)
07:09	alkisg_irc1 is now known as alkisg_irc
13:28	torototo has joined IRC (torototo!~torototo@185.116.131.155)
13:31	<torototo> hello
13:31	why the thin client is not kept in latest ltsp version?
13:32	<alkisg> Hi torototo
13:32	!thin
13:32	<ltspbot> I do not know about 'thin', but I do know about these similar topics: 'thin-client-deprecation'
13:32	<alkisg> !thin-client-deprecation
13:32	<ltspbot> thin-client-deprecation: The new LTSP doesn't support thin clients (remote Xorg), but it does support low-spec netbooted clients with remote desktop (xfreerdp, x2go etc). Read more in https://github.com/ltsp/ltsp/discussions/243
13:33	<alkisg> torototo so essentialy "remote xorg" isn't supported by the xorg developers anymore, it's not an ltsp issue
13:33	But you can still use remote desktop instead of remote xorg, it's very similar
13:35	<torototo> I tried xrdp and x2go but got a lot of problem like hardware accelerator on thin clients, the old ltsp was really good on it
13:35	so i'm searching an alternate solution... :(
13:36	<alkisg> Eh, the old ltsp didn't support hardware acceleration unless you used localapps, which wasn't thin clients anymore, it was fat, like now
13:36	So if you think you had hardware acceleration you probably misunderstood something, or are mis-reporting something...
13:37	What are your client specs anyway, why do you need thin clients? Are you still using 20 year old 32bit clients with 512 MB RAM?
13:38	<torototo> actually on the old ltsp, in thin mode, when browsing a website or something else, you do not have a slow response, but with x2go or xrdp, it's very slow
13:38	though it was some missing hardware acceleration
13:38	<alkisg> This means you were using localapps, i.e. fat client mode, not thin client mode
13:39	And if you were running the browser locally, it means your clients had 2GB RAM or more...
13:39	If you still have your old ltsp around, I can take a look and tell you if you're running fat clients or thin, if you wish
13:41	<torototo> no i'm sure it's thin mode only
13:41	my clients are only 1Gb or 2Gb
13:41	<alkisg> I'm sure it's not :)
13:41	<torototo> my LTSP conf is configured to allow fat only if 4GB+ memory
13:41	so i'm sure it is :)
13:41	<alkisg> Firefox on thin clients was extremely slow
13:41	x2go firefox on thin clients is faster
13:42	And localapps firefox uses local acceleration
13:42	Check for REMOTEAPPS in your lts.conf
13:42	eeeh sorry LOCALAPPS
13:43	<torototo> I don't have localapps variable in the lts.conf
13:45	<alkisg> Well, something else is going on there then
13:45	Which distro/version are you using currently?
13:46	<torototo> it's an old ubuntu 18.04 :p
13:46	<alkisg> 32bit or 64bit?
13:46	<torototo> huh correction, 16.04
13:46	32bits
13:47	with ltsp 5.5
13:47	<alkisg> Which CPU do the clients have? grep model /proc/cpuinfo
13:47	<torototo> so 'im searching to replace it with a solution allowing thin clients
13:48	atom N280, or some have old amd G-T56N
13:48	<alkisg> You can still install the ltsp5 packages on ubuntu 22.04
13:48	But you'll see that remote xorg has so many bugs that it's unusable
13:48	<torototo> i did tried x2go on the past, but where really bad working on some interfaces (like mate)
13:48	<alkisg> People have switched to remote desktop
13:48	<torototo> I will check the x2go tce
13:49	<alkisg> xrdp mostly; while x2go is also ok
13:49	<torototo> remote desktop with what techno? xrdp ?
13:49	xrdp I tried it, the browsing is unusable
13:49	<alkisg> https://ark.intel.com/content/www/us/en/ark/products/41411/intel-atom-processor-n280-512k-cache-1-66-ghz-667-mhz-fsb.html
13:49	64 bit => no
13:49	So you won't be able to install ubuntu 22.04 there anyway
13:50	As it's 64bit only
13:50	<torototo> yes I know :/
13:50	<alkisg> You really need to upgrade your clients :)
13:50	<torototo> I was thinking to use debian 9 32bits waiting to replace the clients
13:50	<alkisg> If you can, just keep using ubuntu 18.04 with esm enabled
13:51	<torototo> yes but I get other problems (browser outdated etc...)
13:51	<alkisg> Yeah you can't magically solve these issues
13:51	Even if you were to install e..g. debian bookworm 64bit, they'd need 5 minutes to boot...
13:51	<torototo> yes :D
13:51	<alkisg> You need to accept that your hardware is old, and can't run new stuff :)
13:52	<torototo> I will try the TCE x2go
13:52	yes I know
13:52	need to find some fanless clients
13:52	<alkisg> !cheap-client
13:52	<ltspbot> Error: "cheap-client" is not a valid command.
13:53	<alkisg> firefox \| 113.0.2+build1-0ubuntu0.18.04.1 \| bionic-updates \| source, amd64, arm64, armhf, i386, ppc64el, s390x
13:53	Eh ok firefox isn't that old in 18.04
13:53	And if you're running thin clients, you can have an 22.04 server with 18.04 clients
13:53	firefox \| 77.0.1+build1-0ubuntu0.16.04.1 \| xenial-security \| s390x
13:54	You're running 16.04, that's why it's old; you can upgrade to 18.04 though
13:54	firefox \| 88.0+build2-0ubuntu0.16.04.1 \| xenial-updates \| source, amd64, arm64, armhf, i386, ppc64el
13:54	https://www.aliexpress.com/w/wholesale-mini-pc.html?tracelog=msite2pc
13:55	Many mini-pcs there, choose one and forget about old software
13:56	<torototo> yep, but not only my choice ;) but I agree
14:22	torototo has left IRC (torototo!~torototo@185.116.131.155, Quit: Client closed)
14:51	sunweaver is back
15:10	sunweaver is now away: not here ...
16:25	vaab has joined IRC (vaab!~vaab@82-64-236-101.subs.proxad.net)
16:30	<vaab> Hi everyone, I'm considering building a LTSP solution for around 12ish Thin Client and I was looking for some recent example of server hardware specs currently running so-as to be able to have an idea how to dimension the server. I'm happy with links sharing these information, but didn't found some yet on the official web site (still looking for
16:30	that). Hint: I've already built LTSP solution in production for several years 10-12years ago, so I'm not exactly a newbie ;-). Many thanks for any pointer with any info related to hardware specs and matching LTSP setup.
16:33	(PS: I've seen https://ltsp.org/guides/specs/ but needed more, and it is not clear if this example is actually a real working setup, and how well it fares)
16:37	<alkisg> vaab: what are your client specs?
16:42	vaab: in any case, make sure your clients have 4GB or better yet 8GB RAM, and 5000+ cpubenchmark score, so that they run your distribution of choice properly
16:43	Then the server can just be one of them, no special specs necessary. Maybe two gigabit NICs, to make things a bit faster.
17:00	vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50)
18:33	woernie has left IRC (woernie!~werner@pd9e8b418.dip0.t-ipconnect.de, Quit: http://quassel-irc.org - Chat comfortably. Anywhere.)
18:35	woernie has joined IRC (woernie!~werner@pd9e8b418.dip0.t-ipconnect.de)
20:38	sunweaver is back
20:41	sunweaver is now away: not here ...
21:20	ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:40	woernie has left IRC (woernie!~werner@pd9e8b418.dip0.t-ipconnect.de, Remote host closed the connection)
22:52	LucasCastro[m] has left IRC (LucasCastro[m]!~lucascast@2001:470:69fc:105::1:59f2, Ping timeout: 255 seconds)
22:53	alexxtasi[m] has left IRC (alexxtasi[m]!~alexxtasi@2001:470:69fc:105::168d, Ping timeout: 255 seconds)
22:54	capscience[m] has left IRC (capscience[m]!~capscienc@2001:470:69fc:105::3:72ec, Ping timeout: 255 seconds)