[04:04] <IrcsomeBot> <Omar> Swap
=== guiverc2 is now known as guiverc
[08:07] <IrcsomeBot> <ciacnorris> OEDU
[08:09] <IrcsomeBot> <ciacnorris> Hello everybody!
[08:09] <IrcsomeBot> <ciacnorris> Just a simple question: is the 22.04 upgrade path available for Kubuntu 20.04 users yet?
[08:10] <arraybolt3> @ciacnorris: Yes! It's just not being displayed since the app that would usually let you know that it was time you could upgrade isn't included in Kubuntu, if I'm understanding correctly.
[08:10] <arraybolt3> @ciacnorris: You should be able to simply use "do-release-upgrade" to upgrade your system. I'd highly recommend backing up all your data first in case anything goes wrong.
[08:11] <arraybolt3> (You might also use "do-release-upgrade --allow-third-party" if you use PPAs or third-party repos.)
[08:11] <arraybolt3> (Er, not also, but use the second one instead of the first one if you use PPAs or third-party repos.)
[08:35] <IrcsomeBot> <ciacnorris> Thanks for the info @arraybolt3 ! (re @IrcsomeBot: <arraybolt3> @ciacnorris: Yes! It's just not being displayed since the app that would usually let you know that it was time you could upgrade isn't included in Kubuntu, if I'm understanding correctly.)
[11:29] <scraf> Hi. Is Ubiquity still the installer for kubuntu or was there a switch to calamares?
[11:47] <IrcsomeBot> <rs2009> Ubiquity's still used by Kubuntu, just with a QT frontend which looks really similar to calamares (re @IrcsomeBot: <scraf> Hi. Is Ubiquity still the installer for kubuntu or was there a switch to calamares?)
[12:55] <BluesKaj> Hi all
[15:00] <vaio> how are you?
[15:57] <IrcsomeBot> <Lisa> Hi, I want to chat.
[16:24] <IrcsomeBot> <Omar> How to make my swap file 8 gb
[17:18] <mparillo> In Kubuntu you can install with a swap partition. You could create a swap file following these directions: https://wiki.archlinux.org/title/Swap#Manually
[17:19] <mparillo> If you have both a swap partition and a swap file, you can have them both in /etc/fstab and you can prioritize them.
[17:56] <IrcsomeBot> <Omar> Swap file and swap partition are not the same? (re @IrcsomeBot: <mparillo> If you have both a swap partition and a swap file, you can have them both in /etc/fstab and you can prioritize them.)
[17:58] <IrcsomeBot> <ykruH> you can have a file on some existing partition formatted as ext4 for example, and/or have a dedicated partition for swap
[18:47] <oerheks> !swap
[18:47] <ubottu> swap is used to move unused programs and data out of main memory to make your system faster. It can also be used as extra memory if you don't have enough. See https://help.ubuntu.com/community/SwapFaq for more info
[19:02] <Monteiro> The Kubuntu 20.4.4 LTS ends the time in April of 2003
[19:02] <Monteiro> the updates of packages will be closed ?
[19:02] <Monteiro> For example install of WINE and PlayOnlinux
[19:03] <oerheks> No, you will go over to 20.04.5
[19:03] <oerheks> which is, already here
[19:03] <Monteiro> i am playing ... testing STEAM for Windows in Kubuntu
[19:03] <Monteiro> with a WINE sandbox
[19:04] <Monteiro> thanks
=== cory_ is now known as Elephantman
=== Elephantman is now known as cory_
[19:48] <IrcsomeBot> <christophelabrie> Hello ! I have a problem. I use KDE Global Menu, but I need to launch a Qt6 app (OBS form PPA version). But I don't have menubar displayed. I have try to lot of solution, KDE_NO_GLOBAL_MENU=1, UBUNTU_MENUPROXY=none, ... But launch without menubar. Do you have any idea? : https://irc-attachments.kde.org/519c5287/file_59711.jpg
[20:14] <rbnswartz> Good afternoon I have an unbootable system after a 5.15-46 kernel upgrade, any tips on how to recover it outside of reinstall?
=== arraybolt3_ is now known as arraybolt3
[20:18] <arraybolt3> rbnswartz: Boot into the older kernel.
[20:19] <arraybolt3> Uh... I think there's a bot factoid that will link to the page on how to do that...
[20:19] <arraybolt3> Hold on, lemme find it...
[20:19] <rbnswartz> arraybolt3 Don't have an older kernel, -47 has come out and replaced the only other working kernel I had
[20:20] <arraybolt3> rbnswartz: Oh crummy. Uh... can you boot into recovery mode on either kernel?
[20:20] <rbnswartz> Can't boot into recovery on either of them
[20:20] <rbnswartz> kernel just panics
[20:20] <arraybolt3> rbnswartz: Can you take a picture of the kernel panic error?
[20:20] <arraybolt3> (Sometimes they can be solved without too much fuss.)
[20:23] <rbnswartz> arraybolt3 had to take a picture off of my phone for that https://photos.app.goo.gl/K7C1AwKMDRroiWAV7
[20:24] <arraybolt3> rbnswartz: Yep, that is *exactly* the error I was hoping to see. This fix should be easy, and you won't even have to downgrade the kernel if it works right.
[20:24] <arraybolt3> rbnswartz: Do you have a live USB you can boot from?
[20:24] <rbnswartz> I can rummage one together
[20:35] <rbnswartz> arraybolt3 I got one made and booted
[20:50] <rbnswartz> arraybolt3[m] I got one created what do I do next
[21:22] <arraybolt3_> rbnswartz: OK I'm back, thanks for your patience.
[21:22] <arraybolt3_> rbnswartz: Alright, can you open the internal drive of your computer from within the live environment?
=== arraybolt3_ is now known as arraybolt3
[21:29] <rbnswartz> yup
[21:30] <rbnswartz> I can arraybolt3
[21:31] <arraybolt3> (One moment, slightly tied up, I'll be right back.)
=== denis is now known as Guest5779
[22:13] <arraybolt3> rbnswartz: OK, here I am.
[22:14] <arraybolt3> rbnswartz: Alright, open your main hard drive in your file manager, then right-click in an empty area of the screen and click "Open Terminal" or something similar. Then run "ls boot | nc termbin 9999" and send the link that spits out. That will let me see the contents of your boot folder.
[22:21] <rbnswartz> arraybolt3 doesn't work  complains  about getaddrinfo for host termbin port 9999 failure in name resolution
[22:21] <rbnswartz> am I missing more of the domain name
[22:21] <arraybolt3> :facepalm: Yep, I typoed.
[22:21] <arraybolt3> ls boot | nc termbin.com 9999
[22:21] <arraybolt3> (Sorry about that.)
[22:23] <rbnswartz> arraybolt3 https://termbin.com/7xwm
[22:23] <arraybolt3> rbnswartz: Hmm. OK, can you do "cat boot/grub/grub.cfg | nc termbin.com 9999"?
[22:24] <arraybolt3> rbnswartz: And also "cat etc/initramfs-tools/initramfs.conf | nc termbin.com 9999"
[22:24] <rbnswartz> I did try to install an older kernel also but that didn't seem to work but it did get further in the boot and didn't panic
[22:24] <rbnswartz> sure
[22:24] <rbnswartz> https://termbin.com/aoxf
[22:25] <arraybolt3> It looks like it's failing to load the initramfs for some reason, so I'm looking for why.
[22:25] <arraybolt3> rbnswartz: You don't happen to see an "out of memory" error during very early boot, before the kernel panic, do you?
[22:25] <rbnswartz> Yes I do
[22:25] <rbnswartz> Out of memory hit enter to continue
[22:26] <arraybolt3> Got it. Then I'm sure we can fix this. Run "sudo nano etc/initramfs-tools/initramfs.conf". This will open a text editor where we can fix the problem.
[22:26] <arraybolt3> Once inside, look for a line that says "MODULES=most", and change it to "MODULES=dep".
[22:26] <arraybolt3> Then find "COMPRESS=zstd" and change it to "COMPRESS=xz".
[22:26] <arraybolt3> Then press Ctrl+S to save, then Ctrl+X to exit.
[22:27] <arraybolt3> Once that's done, the next steps will depend on whether you have disk encryption enabled or not. Did you choose to encrypt your hard drive during installation?
[22:28] <rbnswartz> No I didn't choose to encrypt it
[22:28] <arraybolt3> rbnswartz: OK. Did you do all the steps above?
[22:28] <rbnswartz> Yup
[22:28] <arraybolt3> Nice. Next step, run the following commands, in order:
[22:28] <arraybolt3> sudo mount --bind /dev dev
[22:28] <arraybolt3> sudo mount --bind /dev/pts dev/pts
[22:28] <arraybolt3> sudo mount --bind /proc proc
[22:29] <arraybolt3> sudo mount --bind /sys sys
[22:29] <arraybolt3> sudo chroot .
[22:29] <arraybolt3> update-initramfs -c -k all
[22:29] <arraybolt3> exit
[22:29] <arraybolt3> (Be careful not to make typos - all the little stuff like the presence or absence of a slash or a period is important.)
[22:30] <rbnswartz> done, chroot is such a handy tool
[22:30] <arraybolt3> Fantastic. Alright, shut down, take the live USB out, then power it back up and see what happens.
[22:31] <rbnswartz> Ok, don't need to update then
[22:31] <rbnswartz> update grub then
[22:31] <arraybolt3> Nope, shouldn't need to update grub.
[22:31] <arraybolt3> The problem is almost certanly that your initrd files were too big - the steps we just did should shrink them, possibly drastically.
[22:32] <arraybolt3> If all goes as planned, your system should boot up like normal and you can pick up where you left off.
[22:32] <rbnswartz> Yup, that totally resolved it, and you answered my next question which was what went wrong to get into that particular pickle in the first place
[22:33] <arraybolt3> \o/ As for why the initrd images are getting so big, or why they aren't working on some systems, I have no clue, but hey, if it works, it works!
[22:33] <rbnswartz> I would have never figured this out on my own, I don't know enough about the inner workings of the kernel boot process.
[22:33] <rbnswartz> Thank you so much, you saved me reinstalling software for 40+ minutes
[22:33] <arraybolt3> rbnswartz: Only reason I knew was because it's happened to a couple of other people before. Glad to help!
[22:34] <rbnswartz> Thanks a million and have a great evening
[22:34] <arraybolt3> You too!
[23:43] <mmikowski> arraybolt3: rbnswartz; We got a writeup on recovery that can be helpful.  Ironically, to solve the very same issue: https://kfocus.org/wf/recovery.html#bkm_use_chroot_to
[23:45] <mmikowski> *same issue => arraybolt3 and I discussed the initrd issue just yesterday.
[23:57] <wes_> hello