IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 19 November 2021 (all times are UTC)
| 01:41 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving) | |
| 03:20 | adrianorg has left IRC (adrianorg!~adrianorg@debian/adrianorg, Ping timeout: 268 seconds) | |
| 03:52 | adrianorg has joined IRC (adrianorg!~adrianorg@debian/adrianorg) | |
| 06:40 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 06:58 | hakan^chatos has joined IRC (hakan^chatos!~hakan^cha@95.70.147.189) | |
| 07:22 | hakan^chatos has left IRC (hakan^chatos!~hakan^cha@95.70.147.189, Quit: Client closed) | |
| 07:48 | woernie has joined IRC (woernie!~werner@p508678d0.dip0.t-ipconnect.de) | |
| 09:29 | woernie has left IRC (woernie!~werner@p508678d0.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
| 09:29 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 10:03 | woernie_ has joined IRC (woernie_!~werner@p508678d0.dip0.t-ipconnect.de) | |
| 10:03 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 268 seconds) | |
| 11:36 | lucascastro has left IRC (lucascastro!~lucascast@177-185-133-154.dynamic.isotelco.net.br, Ping timeout: 256 seconds) | |
| 11:58 | lucascastro has joined IRC (lucascastro!~lucascast@45-167-143-6.netfacil.inf.br) | |
| 12:30 | woernie_ has left IRC (woernie_!~werner@p508678d0.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 13:18 | woernie has joined IRC (woernie!~werner@p5b296c2c.dip0.t-ipconnect.de) | |
| 14:46 | danboid has joined IRC (danboid!~danboid@146.87.136.65) | |
| 14:49 | <danboid> Virtualbox has stopped running under LTSP5. I think its because its chrootless and the kernel running on the server doesn't match the kernel running on the clients. I thought the kernels would be in sync but apparently not. How do I get the kernel versions to match?
| |
| 14:50 | BTW, we've FINALLY got a new LTSP server, I've just not had time to set it up yet
| |
| 14:51 | I'm going to use chroot on the new LTSP server
| |
| 14:54 | alkisg has joined IRC (alkisg!~alkisg@2001:470:69fc:105::2d3) | |
| 14:54 | <alkisg> danboid: the kernels should be in sync, yeah. Just fully update the server and run ltsp-update-image, which will also run ltsp-update-kernels automatically
| |
| 14:57 | lucascastro has left IRC (lucascastro!~lucascast@45-167-143-6.netfacil.inf.br, Ping timeout: 268 seconds) | |
| 14:57 | <danboid> alkisg: Already done that a few times. Maybe I should downgrade the server to use the same kernel version?
| |
| 14:57 | <alkisg> danboid: what's the output of `uname -a` on the server, and what on the clients?
| |
| 15:01 | <danboid> Where did my response go?
| |
| 15:02 | <alkisg> No idea, in another channel? :D
| |
| 15:02 | <danboid> 4.15.0-142 on the server, 4.4.0-131 on the clients
| |
| 15:03 | I had tried installing the hwe kernel to try to get the latest NV driver to work without any luck
| |
| 15:03 | <alkisg> And what's the output of this? 'dpkg -l | grep linux'
| |
| 15:04 | It's possible that you have an ancient ltsp, i.e. not the latest ltsp5 version, that wrongly sorts the kernels alphabetically instead of "by version". To remedy that, you can uninstall the old 4.4 kernels and run ltsp-update-image once more
| |
| 15:04 | Or, that your /boot/vmlinuz symlink points to 4.4 instead of 4.15
| |
| 15:04 | Or your /vmlinuz symlink...
| |
| 15:06 | <danboid> Hmm yeah 4.4.0-131 isn't installed on the server
| |
| 15:06 | not any more
| |
| 15:07 | <alkisg> danboid: do you want me to take a look? x11vnc -connect alkisg.ltsp.org
| |
| 16:00 | <danboid> alkisg: OK, we can try that becauseI can't see any 4.4.x kernels installed on out LTSP server. Not sure VNC wil work tho
| |
| 16:10 | Ah! I have4.4.x kernel packages in an rc dpkg state. Purging them now
| |
| 16:14 | danboid has left IRC (danboid!~danboid@146.87.136.65, Quit: Client closed) | |
| 18:26 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b) | |
| 20:30 | <Hyperbyte> Hey alkisg :-) I've done a clean install of Ubuntu 20.04 in a VM and tried to set up LTSP. I think it worked, but it doesn't seem to start lightdm. It shows a black screen with 1 white pixel. The server boots fine. How do I debug? I'm pretty sure SCREEN_02=shell isn't going to work anymore :-D
| |
| 20:30 | !debug-shell
| |
| 20:30 | <ltspbot> Error: "debug-shell" is not a valid command.
| |
| 20:30 | <Hyperbyte> !shell
| |
| 20:30 | <ltspbot> I do not know about 'shell', but I do know about these similar topics: 'gnome-shell', 'shell-screen'
| |
| 20:30 | <Hyperbyte> !shell-screen
| |
| 20:30 | <ltspbot> shell-screen: (#1) One way to get local root access to troubleshoot a thin client is to use a shell SCREEN: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using%20a%20shell%20SCREEN, or (#2) to enable a root debug shell, add SCREEN_02=shell and SCREEN_07=ldm to lts.conf
| |
| 20:31 | <Hyperbyte> I guess that's old
| |
| 20:31 | <alkisg> !forget shell-screen all
| |
| 20:31 | <ltspbot> Error: There is no such factoid.
| |
| 20:31 | <alkisg> s/all/2/
| |
| 20:31 | !forget shell-screen
| |
| 20:31 | <ltspbot> Error: 2 factoids have that key. Please specify which one to remove, or use * to designate all of them.
| |
| 20:31 | <alkisg> !forget shell-screen *
| |
| 20:31 | <ltspbot> The operation succeeded.
| |
| 20:31 | <alkisg> !root
| |
| 20:31 | <ltspbot> I do not know about 'root', but I do know about these similar topics: 'ROOT_PASSWORD_HASH', 'chroot'
| |
| 20:31 | <alkisg> !ROOT_PASSWORD_HASH
| |
| 20:31 | <ltspbot> ROOT_PASSWORD_HASH: To be able to login as root in vt1, read the last example in https://ltsp.org/man/ltsp.conf/
| |
| 20:32 | <alkisg> Although the easiest way to debug would be via epoptes, you wouldn't even need to leave your seat...
| |
| 21:25 | <Hyperbyte> alkisg, actually, if I press ctrl+alt+f1 I should get a shell?
| |
| 21:26 | Because that doesn't do anything... actually it seems more like the whole machine is frozen
| |
| 21:26 | <alkisg> Not a shell. A "vt" where you should be able to login using a user or root
| |
| 21:26 | Try ctrl+alt+f2, in some cases xorg runs in vt1
| |
| 21:26 | If it's frozen, then something is definitely wrong :D
| |
| 21:30 | <Hyperbyte> I guess I could just disable lightdm on startup?
| |
| 21:30 | <alkisg> I guess your problem isn't related to lightdm at all... :D
| |
| 21:31 | Maybe a graphics issue? Maybe networking?
| |
| 21:31 | You can pass systemd.unit=multi-user.target in ltsp.ipxe, to make it stop before graphics load
| |
| 21:32 | (or KERNEL_PARAMETERS=... in ltsp.conf, then run `ltsp ipxe`)
| |
| 21:32 | * alkisg waves good night for now; back tomorrow... | |
| 21:32 | <Hyperbyte> G'night, thanks
| |
| 21:37 | <adrianorg> !gnome-shell
| |
| 21:37 | <ltspbot> gnome-shell: To select gnome-shell as your default session, put this line in your lts.conf: LDM_SESSION="gnome-session --session=gnome"
| |
| 21:38 | <Hyperbyte> I want MATE though. :-)
| |
| 21:38 | But thanks, I'll look further. I get a prompt now.
| |
| 21:38 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 21:39 | <adrianorg> I'm just curious about the bot :-)
| |
| 22:52 | vsuojane1 has left IRC (vsuojane1!~vsuojanen@ec2-3-21-130-219.us-east-2.compute.amazonaws.com, Quit: leaving) | |