[00:07] <webchat51> Today I can no longer boot properly with 5.15.0-53-generic, after BIOS LUKS does not ask me for a password, and my monitor goes to sleep. It however works with 5.15.0-52-generic. Is there something I can do, or should I report a bug?
[00:08] <arraybolt3> webchat51: Just to be sure, no one may have maliciously modified your system, right?
[00:08] <arraybolt3> If so, try blindly typing your LUKS password and pressing Enter, and see if that works.
[00:08] <webchat51> I noticed it today because I ran out of space and rebooted. I don't know if that could cause any problems.
[00:09] <arraybolt3> And you did clear some space, right?
[00:09] <webchat51> Yeah, I'm back online with plenty of space
[00:09] <arraybolt3> Nice. OK, then I would try typing the password blindly and see if that works. I would also definitely report a bug.
[00:10] <arraybolt3> Just run "ubuntu-bug linux" in a terminal window, and follow the on-screen instructions. You will be asked to create an Ubuntu One account if you don't have one already.
[00:10] <arraybolt3> Describe in detail what you're doing to cause the bug, what you expected to happen, and what happened instead, along with any extra info you have.
[00:10] <webchat51> Oh, nice, I was thinking about the site, I just made an account there
[00:10] <webchat51> But that sounds easier
[00:11] <arraybolt3> Also see this page: https://wiki.ubuntu.com/Kernel/Bugs
[00:11] <webchat51> Thanks!
[00:11] <arraybolt3> Sure thing!
[00:11] <arraybolt3> Also, back up your data, you may be asked to do a whole bunch of stuff to your system for troubleshooting purposes, and in the event that goes really wrong, you don't want to lose your data.
[00:12] <webchat51> Luckily already did that while fixing the space issue, I was preparing for a reinstall.
[00:13] <webchat51> Btw, can I somehow see when I installed that kernel? I'm curious if it was installed since my last reboot, or if I was using it all along.
[00:13] <arraybolt3> Nice. Then you probably know the rest of what to do (back up before trying anything risky like installing a testing kernel). Also you may want to ensure that the people asking you to do things are trustworthy - you can click on a person's user profile and see what teams they're a part of to help verify that.
[00:13] <arraybolt3> webchat51: I think so, hold on one moment...
[00:14] <arraybolt3> webchat51: Try "grep install /var/log/dpkg.log".
[00:15] <arraybolt3> That should show you the dates of when packages were installed.
[00:15] <webchat51> Should that ... show dates from before I installed?
[00:16] <arraybolt3> webchat51: And if that doesn't work, try looking in an earlier log with "grep install /var/log/dpkg.log.1".
[00:16] <arraybolt3> webchat51: From before you installed the system itself?
[00:16] <webchat51> Yes
[00:16] <arraybolt3> Possibly, now that I think about it.
[00:17] <arraybolt3> When you install Kubuntu, it doesn't install every single package one at a time, it just clones the installation on the live ISO and then removes anything that only belongs on the live ISO, then does some configuration. (That's a very rough overview.)
[00:17] <arraybolt3> So it may display dates from when the packages were installed onto the ISO during the ISO build process. That would be my best guess as to why it's showing older stuff like that.
[00:18] <webchat51> Yeah, I was thinking something like that too.
[00:18] <webchat51> Does this seem right? 2022-11-15 14:44:19 install linux-modules-5.15.0-53-generic:amd64 <none> 5.15.0-53.59
[00:18] <arraybolt3> Well I have a line that looks almost exactly like that in my dpkg.log.1 file, and my system works fine, so I would think so.
[00:18] <webchat51> In that case I think I was using .52 last time I booted properly.
[00:19] <webchat51> Which seems better than if I was using .53 all the time, and then suddenly I had the problem.
[00:20] <arraybolt3> True. If booting into .52 works, and .53 has a problem, that sounds like a kernel regression. Document that fact in the bug report, that will be very helpful.
[00:20] <webchat51> Will do, and even better. I can get into KDE if I boot with 53 recovery.
[00:21] <webchat51> Thanks for the help, will report tomorrow
[00:21] <arraybolt3> Glad to help! Good luck, and thanks!
[06:14] <DDR> Well, just installed Kubuntu. Thank y'all for the quality software.
[06:14] <DDR> o7
 I really think it is the best distro (re @IrcsomeBot: <DDR> Well, just installed Kubuntu. Thank y'all for the quality software.)
 Stable customizable and light what else do i need really thank you for the quality
[10:41] <Hans_Bosch> Good morning, I have a problem with NVIDIA GTX 1650 Super on installation Kubuntu 2204
[10:42] <Hans_Bosch> is this graphics card not yet supported?
 Hans.  I am running Kubuntu on 1650 super and it's working without any hitches.  What is the problem you are facing?
[10:45] <Hans_Bosch> The installation was without problems, after reboot I get a black screen with an error about the NVIDIA card
[10:45] <Hans_Bosch> cannot log in to the system
 Do you get the grub menu?
[10:46] <Hans_Bosch> no
 ESC or press and hold shift key to get into grub menu
[10:48] <Hans_Bosch> should I reinstall without 3dr person drivers?
 Simple check the web for entering NOMODESET in the grub.  Detailed information is given.  That mostly solves your issue
[10:49] <Hans_Bosch> can I get back to you later?
 Sure
[10:49] <Hans_Bosch> thanks
 Copying to a flash from my laptop is so slow although i have ssd storage what is the problem and how to make it faster
[12:06] <oerheks>  Copying to a flash *is* slow, for all of us.
 It starts fast (100mg/s)  then it gets slower 'till (<10mg/s)
[13:43] <BluesKaj> Hi all
 dqof
[19:42] <mmikowski> keithzg: Hey just saw your post ("Uhh hmm I hadn't double-checked what kernel..."). Did the switch to 22.04 hwe fix the issue?  Please let me know either way.  If it didn't, then it is not kernel related, although the kernel firmware might be a different version which could lead to issues.
[19:58] <keithzg[m]> mmikowski: Yeah alas I just walked downstairs to my desktop PC and it's exhibiting one of the main problems I've seen since upgrading to 22.10, I can't interact with anything on the session, or at least none of my clicking causes any change to what it's displaying on screen in my Plasma/X11 session (I have only seen this problem on X11, it doesn't occur on Wayland although many *other* seemingly rendering-related problems occur on Wayland).
[20:00] <keithzg[m]> It's a weird state because it's clearly functional enough that the mouse cursor changes depending on whether it's overtop a selectable text field or not, although it's not changing when moving around corners of windows.
[20:00] <mmikowski> keithzg: We considered Wayland on the upgrade to 22.04 LTS for kfocus systems. Too many problems at that time, especially for Nvidia.  However, some significant blockers on Intel too.
[20:01] <mmikowski> Roll back to 22.04? Interim releases are always riskier and 3rd-party support is always a challenge.
[20:02] <keithzg[m]> Yeah mmikowski this is AMD (5500 XT 8GB DDR6) and Wayland has tons of issues, seems like the only sweet spot for Wayland is ARM and SailfishOS haha
[20:03] <mmikowski> Yeah, indeed. Sometimes one needs to stop beta testing and get work done.
[20:04] <mmikowski> What I do to feed my "show me the greatest" itch is to run interim releases in VBox (full screen is pretty good these days!).
[20:04]  * keithzg[m] uploaded an image: (105KiB) < https://libera.ems.host/_matrix/media/v3/download/kde.org/db0cfb0228fb62309d20219f6e89ffae1054f333/PXL_20221118_200013908.jpg >
[20:04] <keithzg[m]> Interestingly I see a rectangle in the corner of my screen that's exactly the right size to be a notification popup, but it's showing what's clearly the equivalent portion one of the wallpapers I have in my rotation instead
[20:07] <keithzg[m]> Oh trust me I'm staying LTS on my home server and everything at my work! But forcing myself to live with the bleeding edge on at least one of my systems has served me well in the past—especially since this desktop has basically identical hardware to my home server, so pain here makes for smooth sailing later on my machine where it actually needs to be running smoothly 24/7 :)
[20:07] <keithzg[m]> (I also have a Steam Deck now and this desktop was previously mostly my gaming PC, so it's even less crucial for me to get it working reliably again, I can plunk away at this problem for a long time)
[20:09] <mmikowski> keithzg: Sounds good. Well best of luck to you! Please let me know if you get it working, I'm interested what the problem is. It certainly sounds like an issue in the network stack. NFS mounts can also be trouble, so maybe there.
[20:12] <keithzg[m]> Yeah I wonder. Funny enough I don't actually have any network mounts permanently set up on this desktop; I use sshfs to mount the server disk pool, and for whatever reason I never set that up to be automatic vis autofs or whatnot, I have to do that manually each boot—and so I often don't, and I in fact didn't do so this time, so I accidentally have already checked if a network mount was the issue, hah!
[20:14] <mmikowski> keithzg[m]: Yeah, could be AMD stack too. Maybe try with iGPU (Intel?) and see if that fixes things.
[20:14] <keithzg[m]> Oh interesting, restarted SDDM and logged into a fresh Plasma/X11 session and Latte Dock didn't start this time.
[20:17] <keithzg[m]> mmikowski: Oh yeah good idea, yeah other than the new-ish AMD GPU this is very old hardware, an Intel i7 3770k is my CPU and that does have an iGPU, I should try that next. For now I'm gonna leave hardware rendering disabled (starting with 22.04 it's been disabled by default and I had to press alt+shift+F12 to enable it) and Latte Dock unlaunched, slightly unscientific test to be changing two variables but if it stays stable I'll start
[20:17] <keithzg[m]> working backwards towards repro again :D
[20:18] <mmikowski> keithzg[m]: sounds good. Again, best of luck!
[20:32] <keithzg[m]> Thank$ :)
[20:33] <keithzg[m]> Typo on that S there but I'm gonna stand by it
[21:06] <Guest51> Hi my name is Mike and I'm having a trouble and can find nothing that even sounds the same
[21:08] <Guest51> My kubuntu 20.10 was running good
[21:08] <oerheks> hi mike, ask, wait and see
[21:09] <Guest51> I left my question. If you need it over again I can
[21:15] <Guest51> I found out that there was a new version available so I down loaded the upgrade and when I went to burn it on to a disk I came up with a fault.  Since then I've tried Linux Mint, Kubuntu 19.3 and 20.1 and 21.1. I can get them running but none of them can get any thing to down load it always comes up with an error.
[21:21] <Guest51> Version 20.10 fails the same on three different computers in my family.
[21:23] <alkisg> Guest51: download whatever ubuntu 22.04 flavor you want; boot with it, and if you get an issue, mention the exact error message that you see
[21:23] <alkisg> Do not use old versions, they're unsupported
[21:25] <Guest51> I just downloaded a new version but I can't get my system to burn it to a disk. Is there something I can do I just don't know about?
[21:25] <alkisg> You want to use a CDROM or a USB stick?
[21:26] <Guest51> I triedbut the austen I have days theirs a fault.  All three of them react the same.  Even an old version I ran before
[21:27] <alkisg> I don't understand that sentence, can you rephrase it?
[21:27] <alkisg> You want to use a CDROM or a USB stick?
[21:28] <Guest51> All 3 of my systems have been running for more than a year
[21:28] <alkisg> And how is that related to what we're discussing? Are you a bot?
[21:29] <Guest51> Now itried to down load a new version and install it but my system will not burn it to a disk. I tried orbs disk and they all come up with the same error
[21:30] <alkisg> OK, I give up
[21:32] <Guest51> I tried other programs version 19.10 and 20.0 and none will run anything off of the disk I have used with out failing to continue with out a fault
[21:32] <Guest51> I've even tried Linux mint and it does the same thing
[22:04] <betablockr> Hi, I recently tried Kubuntu 22.10 but I had issues getting the Nvidia 520 open kernel driver to work on it
[22:05] <betablockr> I couldn't get it to work perfectly on 22.04 just wasn't avaliable in the additional drivers tab on 22.10
[22:05] <betablockr> I could get it to work perfectly on 22.04*
[22:10] <betablockr> Hello, wondered if someone could help. I tried installing the NVIDIA 520 open kernel on Kubuntu 22.10 but it's not avaliable in the driver tab and using command line results in Kubuntu breaking. It does however show in 22.04 and works fine just not on 22.10
[22:16] <callmepixelman> Hello everyone; this is my very first time trying to install Linux on my PC in parallel of Windows; and I just CAN'T make any ISO boot properly... I have no idea of what I could have been doing wrong. Could someone help me ?
[22:16] <betablockr> Do you have secure boot on?
[22:17] <callmepixelman> I don't think so; my BIOS is pretty bad to be honnest..
[22:17] <betablockr> You'll need to have secure boot disabled and for best measure disable fast boot
[22:18] <callmepixelman> Normally, that's what I did
[22:18] <betablockr> What program are you using to write the iso the the usb drive?
[22:18] <callmepixelman> BalenaEacher
[22:18] <callmepixelman> Currently on Win11
[22:19] <betablockr> So you plug the USB in, you adjust the boot order and the USB drive still won't boot?
[22:19] <betablockr> Sorry if I'm asking the total obvious but you'll be surprised what some people do xD
[22:20] <callmepixelman> Actually. GRUB shoes up, but when I select Ubuntu in the proposed options it crashes right away
[22:20] <callmepixelman> I'll send you a video wait
[22:20] <betablockr> It sounds like a possibility faulty USB drive, I'd run a disk part clean on it and then format and then run belana
[22:21] <callmepixelman> Even when I tried to install Kubuntu in safe graphics mode, when I try to boot it again; It just wont work
[22:21] <callmepixelman> I tried 3 USB sticks
[22:21] <mmikowski> callmepixelman: I was just going to suggest safe graphics. Go figure.
[22:21] <callmepixelman> 2 in USB2 and finally in USB3 where I can now see the Installer before it crashes
[22:21] <betablockr> I'm pretty sure secure boot must still be on or some other setting preventing booting from USB
[22:21] <callmepixelman> Probably
[22:22] <callmepixelman> HP BIOS is really not well made
[22:22] <betablockr> Ahh yeah navigating the HP BIOS is always tedious
[22:22] <callmepixelman> https://youtu.be/hXoy4PGQ5_I
[22:22] <callmepixelman> Here's a video of what's happening
[22:23] <callmepixelman> There's no GRUB error; just a plain crash
[22:23] <mmikowski> callmepixelman: I would definitely double check the ISO file checksums and reburn to the USB drive. Use the highest quality drive you can. Best check that first.
[22:23] <betablockr> Well that turned out great trying to load the url kicked me from the chat lmao
[22:24] <callmepixelman> Sorry ^^'
[22:24] <betablockr> Not your fault thing it's my browser lol
[22:24] <mmikowski> callmepixelman: I suspect corrupt image.
[22:24] <callmepixelman> mmikowski I tried the ISO on VirtualBox and I boots up perfectly
[22:25] <betablockr> It might be worth redownloading the ISO and flashing it again. Double check to make sure fast boot and secure boot are disabled, save and exit
[22:25] <mmikowski> callmepixelman: did you verify the md5sum? Real hardware uses different bits.
[22:25] <callmepixelman> I did not
[22:25] <callmepixelman> Maybe ? Just maybe; there's a problem with my USB driver that makes all flashes wrong
[22:26] <mmikowski> I suggest validating the ISO and USB as much as possible before progressing to the next likely culprit. I've seen the exact same behavior before on a low-quality USB drive.
[22:26] <mmikowski> ok, off to lunch. Best wishes!
[22:26] <callmepixelman> Thanks, I'll try my best
[22:32] <callmepixelman> I did the checksum on the ISO
[22:32] <callmepixelman> And it's right
[22:32] <callmepixelman> Based of hashed present here https://kubuntu.org/alternative-downloads/
[22:33] <callmepixelman> hashes*
[22:33] <callmepixelman> How could I "validate my USB" ? Or the ISO flashed on it ?
[22:40] <arraybolt3[m]> callmepixelman: Easiest way is to use balenaEtcher to do the flashing.
[22:40] <arraybolt3[m]> Basically you just read the entire start of the USB just after flashing it and make sure it matches with the original file perfectly. I believe that balenaEtcher does this (or something sufficiently similar).
[22:41] <callmepixelman> I'm already using BalenaEtcher
[22:41] <arraybolt3[m]> Then it's already verifying your USB.
[22:42] <callmepixelman> I tried 3 different USB stick, currently with a pretty good Samsung 32GB USB3.0 USB stick
[22:43] <callmepixelman> I don't think that could be a problem with the USB stick itslef
[22:43] <callmepixelman> itself*
[22:43] <callmepixelman> Maybe in my BIOS or IDK
[22:52] <Guest50> I have been trying to upgrade my 18.04 system to either 20.04 or eventually 22.04 and I keep getting an error in the upgrade process concerning a NETWORK problem but I have a wired connection to a DSL line and use it constantly without a problem.  Any help would be appreciated. Frank
[22:53] <mmikowski> callmepixelman: as asked by betablockr, did you ensure fastboot and secure boot were disabled in BIOS?
[22:54] <callmepixelman> SecureBoot if OFF; I don't find any FastBoot toogle in my BIOS tho...
[23:04] <callmepixelman> (Other account on Windows so I can restart this PC)