[05:34] <lordievader> Good morning
 3NQS
 Ep8G
 1KS
[05:49] <arraybolt3> Hector_Peralta: ???
[08:48] <iomari891> greetings, I've tried everything that I know and I still can't update my 21.10 to 22.04. Is it true I have to wait until 22.04.1?
[10:34] <iomari891> Greetings, I'm still not able to update my 21.10 to 22.04. update/upgrade/do-release-upgrade -m desktop displays: "Please install all available updates for your release before upgrading"
[10:35] <iomari891> do-release-upgrade -d desktop displays: "Upgrades to the development release are only available from the latest supported release.
[11:43] <lordievader> Is your system up to date?
[12:14] <BluesKaj> Hi all
[12:17] <iomari891> lordievader: very
[12:21] <lordievader> iomari891: What is the output of `lsb_release -a`?
[12:24] <iomari891> No LSB modules are available.
[12:24] <iomari891> Distributor ID: Ubuntu
[12:24] <iomari891> Description:    Ubuntu 21.10
[12:24] <iomari891> Release:        21.10
[12:24] <iomari891> Codename:       impish
[12:27] <lordievader> You could always go the debian route (manually edit your sources to the new release). Though it is often not recommended for Ubuntu.
[12:34] <iomari891> lordievader: what of the the ppa's?
[12:35] <lordievader> It is always best to disable ppa's during an update
 hi  when i run this command it says     arraybolt3: No such file or directory (re @IrcsomeBot: <arraybolt3> gpg --keyid-format long --keyserver hkp://keyserver.ubuntu.com --recv-keys 0x843938DF228D22F7B3742BC0D94AA3F0EFE21092)
[12:56] <iomari891> lordievader: thanks
 when i run this command it says   gpg: can't open 'SHA256SUMS.gpg': No such file or directory
 gpg: verify signatures failed: No such file or directory (re @IrcsomeBot: <arraybolt3> gpg --keyid-format long --verify SHA256SUMS.gpg SHA256SUMS.txt)
 what should i do
[13:15] <pavara> hello
 hi
 im done thank you again (re @IrcsomeBot: <arraybolt3> Let me know whenever you're done with the sha256sum command.)
[17:22] <user|41> Hi
[17:22] <user|41> I Need information about Kubuntu system requirements
[17:25] <enigma9o7[m]> Minimum?  Reccommended?
[17:26] <enigma9o7[m]> Or better yet, whats your cpu/gpu/ram?
[17:46] <valorie> enigma9o7[m]: it's the same as mainline ubuntu
[17:47] <valorie> I have far more than I need and I run the same system (latest) on my 8-year-old little travel laptop
[17:48] <valorie> Sysinfo for 'valorie-Oryx-Pro': Running inside KDE Plasma 5.24.4 on Ubuntu 22.04 LTS (Jammy Jellyfish) powered by Linux 5.16.19-76051619-generic, CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz at 1166-2800/3800 MHz, RAM: 27235/32056 MB, Storage: 346/1382 GB, 262 procs, 46.24h up
[18:19] <mmikowski> @RikMills Is there a way to reset KDE setting to Kubuntu defaults? It appears that clicking on 'Reset' in system settings uses KDE defaults instead.
[18:20] <RikMills> mmikowski: not that I know of, other than just deleting the kde config files in your home folder that is
[18:29] <mmikowski> @RikMills Thank you. Yeah, KDE is getting much more demanding about default. It would be very useful if [ Defaults ] reset to Kubuntu settings instead of some hardcoded values.
[18:30] <mmikowski> @RikMills Thank you!
[18:33] <enigma9o7[m]> Could you copy everything from skel?
[18:33] <enigma9o7[m]> Or try logging in as a new user.
[18:35] <mmikowski> We definitely want to avoid Skel
[18:35] <mmikowski> The key problem is that the cascade of defaults that still occurs for some settings doesn't work from others.
[18:36] <Eickmeyer> enigma9o7[m]: From a debian packaging standpoint, skel is a no-no. Everything follows a path from xdg standards that can override default settings as set by the desktop environment developer.
[18:36] <mmikowski> @enigma9o7[m] The trouble with Skel is that once it is set, you can't change it.
[18:36] <Eickmeyer> Unforutnatley, some things cannot be overridden, which is a bug.
[18:36] <enigma9o7[m]> well login as a new user then.
[18:37] <enigma9o7[m]> that should make everything kubuntu default, no?
[18:37] <Eickmeyer> enigma9o7[m]: That's not the problem, we're coming at this from a dev standpoint.
[18:37] <Eickmeyer> (myself and mmikowski)
[18:39] <mmikowski> @enigma9o7[m] The problem is if a distro like Ubutnu Studio set some kwin defaults that fit with their look and feel, those get overridden when the user clicks defaults.
[18:40] <mmikowski> So @enigma9o7[m] and @RikMills I'm sorry, I meant to put this on devel, but I had hooked up to the wrong chatroom and was wondering where everyone was. My face-palm.
[18:40] <RikMills> I was sort of guessing that
[18:40] <mmikowski> Yeah :)
[18:42] <mmikowski> So yeah @RikMills, some attributes from xdgdata-config propagate, others don't. Most notably, kwin, but also kgobalshortcuts (which don't even appear to work *anytime* either).
[18:42] <mmikowski> I'll move this to devel now. Thanks @enigma9o7[m].
[18:43] <enigma9o7[m]> ya sorry i thought you were just a user wanting to figure out how to reset
[19:01] <arraybolt3> Oov: Are you still there? I'm just getting on IRC right now.
[19:04] <arraybolt3> Oov: Pretty sure you must have your SHA256SUMS.gpg and SHA256SUMS.txt files in the wrong folder. Pop open Dolphin, find the files, and put them in your Downloads folder. Then do "cd ~/Downloads" in a terminal and then redo the gpg and sha256sum commands.
 Im still there (re @IrcsomeBot: <arraybolt3> Oov: Are you still there? I'm just getting on IRC right now.)
 Yeah i did that and ut worked thank u very much (re @IrcsomeBot: <arraybolt3> Oov: Pretty sure you must have your SHA256SUMS.gpg and SHA256SUMS.txt files in the wrong folder. Pop open Dolphin, find the files, and put them in your Downloads folder. Then do "cd ~/Downloads" in a terminal and then redo the gpg and sha256sum commands.)
[20:07] <arraybolt3> Oov: Awesome! If everything went according to plan (good signature, ISO file OK), then you're all set! You can now use the dd command (carefully) to flash the ISO to a flash drive. Whenever that's done, there's one last step to ensure that everything goes according to plan, and that's to make sure that the flash drive hasn't corrupted the ISO during the flash operation.
[20:15] <arraybolt3> Oov: To check if your flash drive is good, open a terminal with Ctrl+Alt+T, and run "sudo su -" to enter administrator mode.
[20:15] <arraybolt3> Oov: Next, run this command:
[20:15] <arraybolt3> head -c `du -b ./lubuntu-22.04-desktop-amd64.iso | cut -f 1` /dev/<drive ID here> | cmp ./lubuntu-22.04-desktop-amd64.iso
[20:15] <arraybolt3> Oov: Hold on, botched it...
[20:16] <arraybolt3> head -c `du -b <ISO file here> | cut -f 1` /dev/<drive ID here> | cmp <ISO file here>
[20:16] <arraybolt3> Oov: Replace <ISO file here> both times with the name of your ISO file, and replace <drive ID here> with the drive ID of your flash drive (which you can find using lsblk).
[20:20] <arraybolt3> Oov: If this command finishes and produces no output, your flash drive is good and you're ready to install Kubuntu! If you get any errors, you'll need to reflash the ISO to the flash drive and check it again, and if that doesn't work, you'll need to try a new flash drive.
 i used startup disk creator (re @IrcsomeBot: <arraybolt3> Oov: Awesome! If everything went according to plan (good signature, ISO file OK), then you're all set! You can now use the dd command (carefully) to flash the ISO to a flash drive. Whenever that's done, there's one last step to ensure that everything goes according to plan, and that's to make sure that the flash drive hasn't corrupted the ISO during the flash operation.)
 where can i find drive id (re @IrcsomeBot: <arraybolt3> head -c `du -b ./lubuntu-22.04-desktop-amd64.iso | cut -f 1` /dev/<drive ID here> | cmp ./lubuntu-22.04-desktop-amd64.iso)
 you mean sdb? (re @IrcsomeBot: <arraybolt3> Oov: Replace <ISO file here> both times with the name of your ISO file, and replace <drive ID here> with the drive ID of your flash drive (which you can find using lsblk).)
[20:46] <arraybolt3> Oov: If you used Startup Disk Creator, the ISO checking steps likely won't work. Hold on one moment...
 ok
[20:50] <arraybolt3> Oov: I believe Startup Disk Creator checks the USB drive you create automatically, so you shouldn't need to verify the drive. Sounds like you're all set! You should be able to simply boot a computer from the drive and install Kubuntu from there.
 i wanna ask about boot steps in hp laptop
 and dell
 + thank you million times (re @IrcsomeBot: <arraybolt3> Oov: I believe Startup Disk Creator checks the USB drive you create automatically, so you shouldn't need to verify the drive. Sounds like you're all set! You should be able to simply boot a computer from the drive and install Kubuntu from there.)
[21:02] <arraybolt3> Oov: Happy to help! Hope all goes well!