=== sb is now known as ostream === ostream is now known as war10ck === war10ck is now known as stromae === stromae is now known as ostream === ostream is now known as stromae === stromae is now known as ostream [02:32] hi [02:32] I am using wsl 2 with ubuntu 22.04 [02:33] the problem is, I have to start the all services manually of distro [02:34] sounds like you want r eal liniux [02:34] real linux* [02:35] my SSD was crashed and I reinstall the wsl2 before it was very fine. [02:35] Rockwood: maybe this systemd=true line in wsl.conf? https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/ [02:36] this is time i initialize the wsl via Vscode. [02:37] sarnold, https://dpaste.org/MQpxB === chris14_ is now known as chris14 [02:42] Rockwood: and /etc/wsl.conf ? [02:43] sarnold, https://dpaste.org/brJBX nothing like wsl.conf in this [02:44] I am looking in distro's etc folder. [02:46] should I create it manually? [02:46] Rockwood: I'm not sure :/ on the one hand, this post does say to put those lines in that file, on the other hand, this post was written 1.5 years ago and might not be relevant to wsl of today :( [02:46] at least it's easy to undo if it doesn't help [02:47] hmm [02:47] means uninstall the better option? [02:48] s/uninstall/uninstall is [02:49] no, just that if this change doesn't do anything, it's easy enough to sudo rm /etc/wsl.conf and try the next thing :) [02:53] sarnold, I think it's works. [02:55] sarnold, Thanks a lots. it's works not. [03:02] Rockwood: woo! thanks for reporting back :) [03:05] After add that file I shutdown and started wsl, it's working till now. [06:34] Hi. What upgrade path is there from jammy to mantic ? [06:35] yziquel75: you always need to jump to the next release first, 22.04==>22.10 [06:35] but 22.10 is eol [06:36] yziquel75: so if you want 23.10, best to fresh install [08:13] allo === TomTom_ is now known as TomTom [08:22] hi [08:54] !next [08:54] Noble Numbat is the codename for Ubuntu 24.04. For technical support, see #ubuntu-next. For testing and QA feedback and help, see #ubuntu-quality. [08:54] sorry i forgot the channel name [08:54] join #ubuntu-quality [08:59] :w [09:11] lotuspsychje thanks. I guess I'll follow the 22.04 -> 22.10 -> 23.04 -> 23.10 path. === fling_ is now known as fling [09:37] Is managed upgrade jammy -> lunar possible ? or must I do jammy -> kinetic -> lunar in two steps ? [09:48] why not wait until 24.04 is released? You can go straight from 22.04 to 24.04 [09:55] or, you know, just run do-release-upgrade and try the 23.04 noble beta? === PinkMusen is now known as Kristine [10:04] g [10:23] CosmicDJ: 23.04 is not noble [10:24] and it's alömost eol [10:25] DocMors: 23.04 is already eol [10:25] lotuspsychje, mea culpa of course it is [10:25] geirha because there is only ONE thing I need: zfs 2.2. so I go for mantic. [10:26] geirha because there is only ONE thing I need: zfs 2.2. so I go for mantic. [10:28] I'm wondering. When one has a ubuntu pro account, how does one make dist-upgrades and get the account synced with the upgrade ? [10:33] I'm a bit confused on the difference between a gnome-shell theme and a GTK4 theme. How does the default theme for ubuntu, yaru, manage to look consistent across 4 different GTK toolkits (4 if we were to count libadwaita)? [10:39] and the dist-upgrade did not update my kernel, because if oem repos. I need help. [10:43] Hello, I'm new, and wanted to ask What's the purpose of this chat ? [10:45] watson: Official Ubuntu Support Channel [10:45] Ok thanks [10:46] does anyone know whether 24.04 will hatch with FDE? === zer0bitz_ is now known as zer0bitz [10:47] how do you ensure ubuntu pro is kept up to date with jammy -> lunar -> mantic upgrades ? [10:48] Because the apt sources of ubuntu pro are not changing, and I don't know where I should find info as to how to amend them. [11:32] hello [11:34] \o [11:41] Is there a way for apt to show which kernel image provides a given version of the zfs kernel module ? [12:22] Sup [12:33] OK I'll answer myself, yes there will be FDE but it still counts as experimental [13:30] How do I torch all lxd configuration in Ubuntu and start over? I used to have a configuration on top of zfs volume and now I don't remember what I was doing but can't make it with sudo lxd init to set it up [13:31] It fails to create bridged interface , I also have VirtualBox install on same Xubuntu 22.04 host [13:40] Error: Failed to create local member network "lxdbr1" in project "default": The DNS and DHCP service exited prematurely: exit status 2 ("dnsmasq: failed to create listening socket for 10.234.138.1: Address already in use") [13:52] nikolam: sudo snap remove --purge lxd [14:05] Hi all [14:51] leftyfb, Unfortunately I get again similar message, Error: Failed to create local member network "lxdbr0" in project "default": The DNS and DHCP service exited prematurely: exit status 2 ("dnsmasq: failed to create listening socket for 10.63.68.1: Address already in use") [15:08] Error: Failed to create local member network "lxdbr0" in project "default": The DNS and DHCP service exited prematurely: exit status 2 ("dnsmasq: failed to create listening socket for 10.17.187.1: Address already in use") when trying sudo lxd init -v === stenno is now known as Guest4058 === chao is now known as stenno === nsakkos_ is now known as nsakkos === clarkk1 is now known as clarkk [18:33] I have now bug- alt+tab not working. alt looks like not registering. for what to report bug? [18:34] oh no, looks like alt seperate works. how to check if keys work? [18:34] just combo not owkirng === archie_ is now known as archie [19:28] halo [19:56] yo === guiverc2 is now known as guiverc [21:15] Hi, I upgraded my server from Ubuntu 18.04 to 20 over ssh and it completed without any errors. Once I disconnected I wasn't able to connect back and when I restarted the server, I get the following error (a kernel panic) https://imgur.com/a/1KCqpmX What is happening and how can I fix this? [21:16] yikes [21:19] You have backups, right [21:20] it sure looks like the *important* error probably scrolled off screen :( [21:20] try the safe mode boot option? [21:20] older kernel perhaps using grub? [21:22] Sounds to me like there is a missing initramfs or some other driver. try to boot with a recovery kernel as others have states === kvn_ is now known as kvn