IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 31 January 2023 (all times are UTC)
| 00:19 | sugarbeet is back | |
| 00:19 | sugarbeet is now away: [tmux detached] | |
| 00:29 | sugarbeet is back | |
| 00:30 | sugarbeet is now away: [tmux detached] | |
| 00:35 | sugarbeet is back | |
| 00:35 | sugarbeet is now away: [tmux detached] | |
| 01:27 | wyre is now away: Auto away at Tue Jan 31 01:26:00 2023 UTC | |
| 01:46 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40) | |
| 01:51 | sugarbeet is back | |
| 01:51 | sugarbeet is now away: [tmux detached] | |
| 04:48 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40, Quit: leaving) | |
| 06:39 | wyre is back | |
| 07:01 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:16 | wyre is now away: Auto away at Tue Jan 31 07:14:50 2023 UTC | |
| 07:41 | wyre is back | |
| 07:48 | alkisg_irc has left IRC (alkisg_irc!~Thunderbi@srv1-dide.ioa.sch.gr, Remote host closed the connection) | |
| 07:48 | alkisg_irc has joined IRC (alkisg_irc!~Thunderbi@srv1-dide.ioa.sch.gr) | |
| 09:21 | demetrio21r[m] has joined IRC (demetrio21r[m]!~demetrio2@2001:470:69fc:105::3:a7) | |
| 09:28 | <demetrio21r[m]> <alkisg> "While if they don't log out..." <- hello my clients connect and disconnect constantly from epoptes
| |
| 09:28 | <alkisg> demetrio21r: how is that related to your quote?
| |
| 09:32 | demetrio21r: I cannot receive PMs, I'm on matrix, type here in the channel if you want
| |
| 09:33 | !greek
| |
| 09:33 | <ltspbot> greek: Στο παρόν κανάλι μιλάνε μόνο Αγγλικά, για υποστήριξη στα Ελληνικά από την υπηρεσία Τεχνικής Στήριξης ΣΕΠΕΗΥ διαβάστε το http://ts.sch.gr/wiki/IRC και στη συνέχεια πληκτρολογήστε /j #ts.sch.gr
| |
| 09:39 | woernie has joined IRC (woernie!~werner@62.27.249.38) | |
| 12:17 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 14:54 | woernie has left IRC (woernie!~werner@62.27.249.38, Remote host closed the connection) | |
| 15:26 | ricotz is now away: I'm busy | |
| 15:31 | <tru_tru> what is the terminal/CLI version of "epoptes" open remote terminal as root locally?
| |
| 15:33 | I have a booted ubuntu focal client but the GUI fails to start (xfce4 and gdm3), switching to the text console alt-f2, I can login as the regular user and $HOME is not mounted.
| |
| 15:35 | <alkisg> tru_tru: I didn't understand the question. There's a menu in epoptes to open a remote terminal locally, what's your question about that?
| |
| 15:36 | <tru_tru> I would like to have the same remote access through the terminal, without a GUI
| |
| 15:37 | epoptes is an X11 app. I would like the backup solution is case I have to work from remote without X
| |
| 15:37 | s/is case/in case
| |
| 15:38 | <alkisg> You mean that you want to learn the command to share a terminal, without epoptes and without x?
| |
| 15:39 | The menu you mention works even when the remote PC has no xorg running
| |
| 15:39 | While if you want to share a terminal with no xorg, the command is /usr/share/epoptes-client/receive-terminals
| |
| 15:39 | * tru_tru reading | |
| 15:39 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 15:40 | <tru_tru> \o/ that is is
| |
| 15:40 | \o/ that is it
| |
| 15:43 | * tru_tru confused: | |
| 15:44 | <tru_tru> from the ltsp server, how to I start the remote /usr/share/epoptes-client/share-terminal to display on the server using /usr/share/epoptes-client/receive-terminals ?
| |
| 15:45 | <alkisg> You can't run these automatically. You ask the remote person to run share-terminal
| |
| 15:45 | If you want to run these automatically, you use epoptes > right click > open terminal
| |
| 15:45 | If you don't have xorg on the server and you can't use epoptes, then use ssh
| |
| 15:46 | <tru_tru> then I am back to last week answer :P
| |
| 15:46 | [X] remote access to client
| |
| 15:47 | how do you share $HOME for the end users?
| |
| 15:47 | <alkisg> It's automatically shared over sshfs
| |
| 15:48 | Why don't you run epoptes somewhere where you have xorg ?
| |
| 15:48 | E.g. in your own pc, or in ltsp-client-01?
| |
| 15:50 | <tru_tru> I have a client running, but only root is able to start the session locally. A local user don't have /home/user mounted and can not start the xfce session
| |
| 15:51 | when going on the text console on the client, the credentials are ok, but no $HOME, so the local user ends in /
| |
| 15:51 | that was my second question of the day.
| |
| 15:52 | <alkisg> Are you using a normal ltsp installation, or are you e.g. using ldap or something else that's non-standard?
| |
| 15:53 | <tru_tru> plain ltsp
| |
| 15:53 | <alkisg> Can you describe your setup? Which installation CD you used (e.g. ubuntu server 22.04), if you're using a chroot or chrootless, etc?
| |
| 15:54 | <tru_tru> I have installed a fresh lts 20.04 server + gnome-desktop, then followed the ltsp for ubuntu
| |
| 15:54 | the image is chrooted from debootstrap in /srv/ltsp/focal
| |
| 15:55 | <alkisg> OK, and why don't you use ubuntu-desktop.iso with chrootless?
| |
| 15:55 | Because now you'll spend hours just fixing the broken setup and chroot...
| |
| 15:55 | <tru_tru> ubuntu-desktop.iso can not be automated
| |
| 15:55 | <alkisg> Why do you need to automate the server?
| |
| 15:56 | <tru_tru> I have a cloud-init to install the lts20.04 machine and try to automate everything
| |
| 15:57 | <alkisg> I mean, canonical doesn't recommend server + apt install ubuntu-desktop, so you're starting from the "wrong" method
| |
| 15:57 | So you should expect broken stuff, not related to ltsp
| |
| 15:58 | So I think you need to take a step back, explain who is going to use that automation, and see if there's a more recommended method for it
| |
| 15:58 | An ubuntu desktop installation is created from "seeds". It's not the same as server + apt install ubuntu-desktop.
| |
| 15:58 | So if you do that, you're missing stuff
| |
| 15:58 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 255 seconds) | |
| 15:59 | <tru_tru> I also tried with debian/bullseye from preseed, and it is failing at the same stage for ltsp with a chroot based bullseye image
| |
| 15:59 | <alkisg> Why do you want to use a chroot instead of chrootless, what's the use case?
| |
| 15:59 | Your users will run terminals only, no gui?
| |
| 15:59 | <tru_tru> I want to provide both
| |
| 15:59 | <alkisg> Then don't use a chroot
| |
| 16:00 | Otherwise it'll be like maintaining your own distribution
| |
| 16:00 | You'll put the same effort like a "-desktop" package maintainer; you'll need to check that you put everything in the chroot
| |
| 16:00 | wyre is now away: Auto away at Tue Jan 31 15:59:21 2023 UTC | |
| 16:01 | <alkisg> And in every new releases, when new package dependencies arise, you'll need to debug everything from scratch again
| |
| 16:02 | Where are you providing the automation, who are the end users?
| |
| 16:02 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 16:04 | <tru_tru> whoaww, I was not aware that -desktop and -server for ubuntu where so different... I had hoped to use ltsp to provide a choice of lts/debian/rhel clone to boot diskless
| |
| 16:06 | I don't want to be stuck with the ltsp server version for the clients, but maybe a ltsp server for each clients OS is the proper way to go
| |
| 16:07 | <alkisg> You can use any number of VMs. You install the OS graphically in the VM, and you publish it to the network with LTSP
| |
| 16:08 | Note that LTSP only supports .deb distributions at this point
| |
| 16:08 | <tru_tru> If I understand you, the bullet proof poc is lts-desktop and chrootless image for the client, and systemctl isolate multi-user|graphical to go GUI/console ?
| |
| 16:08 | <alkisg> Sure. But that's not a limitation of ltsp. It's a packaging issue in most distributions.
| |
| 16:09 | <tru_tru> ok thanks for your patience
| |
| 16:09 | <alkisg> 👍️
| |
| 16:10 | Now to the particular issue that you mentioned, maybe you're missing the ltsp and sshfs packages inside the chroot
| |
| 16:10 | But even if you do get HOME to mount, you'll find other missing bits later, e.g. dbus, policykit, sound etc being misconfigured due to the chroot
| |
| 16:12 | <tru_tru> ltsp is installed, but sshfs was not
| |
| 16:13 | <alkisg> ltsp recommends sshfs, so you probably used --no-recommends
| |
| 16:13 | <tru_tru> https://ltsp.org/docs/installation/#maintaining-a-client-image -> maybe adding "sshfs" to "apt install --install-recommends ltsp epoptes-client" ?
| |
| 16:13 | <alkisg> No, recommended packages are installed by default
| |
| 16:14 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 16:14 | <alkisg> Your setup is broken for some reason. E.g. LinuxMint defies Debian policy and doesn't install recommends
| |
| 16:14 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 16:14 | <alkisg> Hmm, maybe you don't have "universe" in your apt sources
| |
| 16:15 | Ubuntu gnome ships without "universe", that could be it
| |
| 16:15 | Can you install sshfs now, or does it say package not found?
| |
| 16:16 | <tru_tru> /etc/apt/sources.list: deb http://archive.ubuntu.com/ubuntu focal main universe
| |
| 16:16 | dpkg -l sshfs -> not installed, and "apt install --install-recommends ltsp epoptes-client" is not pulling it
| |
| 16:17 | <alkisg> But they are already installed
| |
| 16:17 | You need to uninstall them first, to see
| |
| 16:19 | <tru_tru> apt remove ltsp epoptes-client <-running in the chroot
| |
| 16:19 | dpkg -l ltsp epoptes-client sshfs
| |
| 16:20 | -> ^rc for epoptes-client and ltsp and ^un for sshfs
| |
| 16:21 | now I see sshfs being pulled... I am wondering what I missed
| |
| 16:21 | rebuilding the image and rebooting the ltsp client
| |
| 16:22 | maybe as you said the "universe" was not in the apt source list
| |
| 16:32 | ltsp client did not like the 'ltsp image focal' replacing the loop mounted image
| |
| 16:34 | <alkisg> Well unmount it before trying to write to it...
| |
| 16:37 | <tru_tru> how is the client supposed to behave when the image is modified on the server?
| |
| 16:38 | anyway, even with sshfs added, I still have my user not having /home/user mounted on the ltsp client
| |
| 16:40 | <alkisg> And you're saying you don't have a working epoptes, to take a look, right?
| |
| 16:46 | <tru_tru> epoptes works for the root user only
| |
| 16:46 | is open terminal root,locally
| |
| 16:46 | but not for user,locally
| |
| 16:48 | I can login as "user" on the local text console (where is complains that HOME=/ instead of /home/user)
| |
| 16:48 | <alkisg> tru_tru: do you want to share your server screen with me, so that I check the clients via epoptes, to see why it's not working?
| |
| 16:48 | (i.e. which other packages are missing ... :D)
| |
| 16:49 | <tru_tru> I will restart the lstp server from scratch with a ltsp-desktop version
| |
| 16:50 | and go the small steps before trying anything else, with ltsp-server or debian
| |
| 16:50 | <alkisg> ok
| |
| 16:50 | <tru_tru> alkisg sure, it is a toy system
| |
| 17:55 | Vercas9 has joined IRC (Vercas9!~Vercas@gateway/tor-sasl/vercas) | |
| 17:55 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 255 seconds) | |
| 17:55 | Vercas9 is now known as Vercas | |
| 18:47 | wyre is back | |
| 19:07 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 255 seconds) | |
| 19:53 | wyre is now away: Auto away at Tue Jan 31 19:51:33 2023 UTC | |
| 19:53 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 21:54 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 22:00 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 22:15 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |