[00:15] <rfm> blahdeblah, if I had to use packages incompatible with the system version, I would install them in a venv
[00:21] <blahdeblah> rfm: They aren't incompatible as far as I know.  They're just running afoul of the new python approach to insist that everything is in a venv whether it needs it or not.
[00:21] <blahdeblah> They all worked fine on 22.04.  I'm just updating my docker image for 24.04 and running into the dreaded "error: externally-managed-environment" https://paste.debian.net/1316402/
[06:48] <andreios_> I have successful upgraded from 22.04 to 24.04 and changed no configs, but I can't connect to wireguard now, it says handshake not completed on every attempted on the server. This is a minimal install on cloud
[06:52] <lotuspsychje> andreios_: LTS upgrades are not enabled yet, not reccomended either
[08:32] <andreios_> lotuspsychje: So do you thing this issue will be fixed when upgrades are enabled? Where should even lie the cause of this? And should there be some who reports this as a bug?
[08:43] <tomreyn> andreios_: see if you can reproduce it on a fresh 24.04 install. if you can, file a bug (after checking it has not been filed, yet)
[19:37] <trippeh> okay, figured out the ipv6 netboot woes - it really doesnt like having stateless addressing enabled on the network (yes, I know, bootloader bits has to be bootstrapped with DHCPv6, thats fine)
[20:05] <catalase> hello
[20:06] <catalase> ubuntu 22.04.4 lts, i try to login via the console or via ssh, and i am immediately logged out
[20:06] <catalase> any ideas?
[20:08] <ravage> did you enable password login during setup? did you specify a ssh key? do you use the ubuntu user?
[20:10] <catalase> password login, no ssh key. yes use ubuntu user
[20:11] <ravage> that should work. did not try the password login for a while
[20:13] <catalase> it's unclear why it won't work
[20:13] <catalase> are there any logs i can check?
[20:13] <ravage> the most common cause would be a wrong password of course
[20:13] <catalase> i have access to the disk
[20:14] <ravage> if this is a fresh installation i would just try it again before you start debugging
[20:14] <catalase> password is correct, it gives me the login prompt, and it even will show the successful login text
[20:14] <ravage> i am downloading the ISO. so i can verify it in a moment
[20:15] <ravage> but then you should be logged in?
[20:15] <catalase> i should be logged in, but it immediately logs me out
[20:15] <catalase> goes right back to the login prompt
[20:16] <catalase> happening on all three of my ubuntu machines
[20:16] <catalase> probably update broke it
[20:16] <catalase> but i don't know where or how to find out 
[20:16] <ravage> you could chroot in the disk and check the system logs
[20:22] <catalase> what log should i check
[20:22] <catalase> auth.log is not even logging my latest attempts apparently
[20:23] <ravage> you need a proper chroot and use journalctl
[20:23] <catalase> how can i get that without being able to login
[20:25] <catalase> even root user log me out right away
[20:34] <ravage> https://p.haxxors.com/chroot.txt
[20:34] <ravage> you can get the ISO from https://grml.org/download/
[20:36] <oerheks> if the disk is mounted RO, i could imagine the logout 
[20:36] <ravage> if this are all VMs on the same host then that may be totally possible
[20:37] <ravage> but then you have a much bigger issue maybe 🙂
[20:37] <catalase> three separate hardware, all running the same distro
[20:37] <catalase> immediately logged out after succesful login
[20:37] <catalase> both by ssh and console