anyone else having issues with the last update?

[skyfishgoo]

EUFI? I thought it was UEFI, or did they make some new thing to add another acronym?

i'm dyslexic, and often make typos... i'll add UEFI to my massive spell check dictionary so it will flag me.


—

you can go ahead and install those other packages, and anything else that comes along as the issue is only with the linux-firmware package, so uncheck that one and update the rest.

if you no longer want to see it listed in discover you use sudo apt-mark hold linux-firmware and it will stop showing it in discover.

it then your duty to remember that you have it on hold tho, so simply unchecking the box is probably the best answer for most ppl until this gets fixed.

[skyfishgoo]

What are these? I'd be curious to see if I can see if any have been.

mainly the slew of "not saving settings" type bugs... wobbly windows is on and cant be turned off was the first one i hear of and now the edge barrier setting is not saving either, i've heard.

that kind of thing

[steve7233]

update: the Microsoft EUFI dbx package has dropped off the list so now

3 standard LTS security updates
Inst libgit2-1.7 [1.7.2+ds-1ubuntu3] (1.7.2+ds-1ubuntu3.1 Ubuntu:24.04/noble-updates, Ubuntu:24.04/noble-security [amd64])
Inst yelp [42.2-1ubuntu0.24.04.1] (42.2-1ubuntu0.24.04.2 Ubuntu:24.04/noble-updates, Ubuntu:24.04/noble-security [amd64]) []
Inst libyelp0 [42.2-1ubuntu0.24.04.1] (42.2-1ubuntu0.24.04.2 Ubuntu:24.04/noble-updates, Ubuntu:24.04/noble-security [amd64])
Inst linux-firmware [20240318.git3b128b60-0ubuntu2.27] (20240318.git3b128b60-0ubuntu2.29 Ubuntu:24.04/noble-updates [amd64])
Conf libgit2-1.7 (1.7.2+ds-1ubuntu3.1 Ubuntu:24.04/noble-updates, Ubuntu:24.04/noble-security [amd64])
Conf yelp (42.2-1ubuntu0.24.04.2 Ubuntu:24.04/noble-updates, Ubuntu:24.04/noble-security [amd64])
Conf libyelp0 (42.2-1ubuntu0.24.04.2 Ubuntu:24.04/noble-updates, Ubuntu:24.04/noble-security [amd64])
Conf linux-firmware (20240318.git3b128b60-0ubuntu2.29 Ubuntu:24.04/noble-updates [amd64])
​

but it still causes the same issue upon reboot, forcing me to restore from a snapshot.

EUFI? I thought it was UEFI, or did they make some new thing to add another acronym?

[claydoh]

and given some of the problems i keep hearing about, it's not pulling me in.

tbh, the same has been said for all LTS-LTS upgrades.
And also tbh the waiting for upgrades is (mostly, imo) about having as few broken or failed upgrades as possible and less to do with any possible KDE bugs or ui differences that users will need to deal with. But luckily in 26.04's case, with Plasma 6.6 now also being LTS, some of these might be addressed.

there are a couple of bugs i'm watching to see those are gonna get fixed first.

What are these? I'd be curious to see if I can see if any have been.

[skyfishgoo]

exactly right... i would have to do a complete reinstall to access 26.04 at this time, and given some of the problems i keep hearing about, it's not pulling me in.

my understanding is the upgrade will be offered sometime around the release of 26.10 and/or the point release of 26.04.1

at that time i'll decide when i want to jump, but there are a couple of bugs i'm watching to see those are gonna get fixed first.

[claydoh]

maybe a dumb question , but why you on 24.04 ?
wouldn't upgrading to 26.04 maybe solve some things ?
maybe it's just me ,but i always like to be on the latest release / updated

I tend to be that way myself, but LTS users tend to wait for official upgrades to be turned on, which iirc hasn't happened yet.

And to be honest, it is this sort of problem that might tend to keep some LTS users leery of upgrading.

[die.boer]

maybe a dumb question , but why you on 24.04 ?
wouldn't upgrading to 26.04 maybe solve some things ?
maybe it's just me ,but i always like to be on the latest release / updated

[claydoh]

It won't show in Discover but will be mentioned that it is behind held when using apt.

[skyfishgoo]

yeah, i'm keeping everything else up to date but keep unchecking the firmware package until i see some movement on the bug report you cited.

seems like they know what went wrong but haven't issued a new package (as far as i can tell).

i assume when a new package is released it will be a new version number, so .29 > .30 or similar.


also question: if i were to sudo apt-mark hold linux-firmware would i still see update notices in discover?

nvrmind: the answer i no... it no longer shows in discover ... i just have to remember to sudo apt-mark unhold linux-firmware when the update comes out

[claydoh]

Those are kernel packages, and I'd guess that they are most likely security patches. No idea if they help or hurt the firmware issue so I'd continue to hold that specific package until you are ready to test it out.

[skyfishgoo]

all that shows me is that the packages will be installed

it doesn't show me what will happen after i reboot.

[Snowhog]

should i pull the trigger?

Just open Konsole and simulate the update: sudo apt update && sudo apt --simulate full-upgrade to see what will happen.

[skyfishgoo]

welp, there is a slew of linux-* updates available today

does anyone know if this fixes anything with the linux-firmware package?

should i pull the trigger?

[skyfishgoo]

do you see the grub screen when you reboot?

the advance options menu choice will take you to all of you other kernels you have installed and for each one there will be recovery options available.

go into the recovery option for your current kernel and at /near the bottom of the list recovery tools will be root login

use that, enter your password and you should find yourself at root level command prompt where you can run apt commands without using sudo

the command above will install the specific version of linux-firmware that you had prior to the update.

then when you reboot it should come up normally again and discover will prompt you to update the package ... DO NOT DO THIS YET.

the next thing you should do is search for timeshift and install it.

set it up to take daily snapshots of your OS so you can get back to a working machine without much fuss... just be sure to keep a thumb drive with a LIVE instance of kubuntu on it so you can use it to recover when you can't boot to the OS.

[vanadiumboy]

@vanadiumboy, unless you have a back up of your system you can restore, you will need to try and revert the linux-firmware package back to the previous version 20240318.git3b128b60-0ubuntu2.27, which seems to be working fine.

you should be able to accomplish this via the Advanced settings in GRUB using the root login tool

apt install linux-firmware=20240318.git3b128b60-0ubuntu2.27


should do it

What is the root login tool? Do you have some steps written somewhere?
I can get into GRUB easily and choose Advanced Settings but that would just give a list of different kernels already installed on my PC.