anyone else having issues with the last update?

[skyfishgoo]

thanks for that bug report, i think that is exactly what is happening with my machine... i even got flash of half my 2nd monitor at one point after a blind attempt to login like it was trying to bring up the shell but failed.

i filed my own bug report yesterday, which i can see in the overall list... it will probably be marked as a duplicate of the one you cited.

i will add a comment to the CONFIRMED bug report so i can stay informed.

according to the latest it looks to be a packaging issue and therefore should be easily corrected.

i'll just hold back the linux-firmware package by unchecking it in discover until the bug report is resolved.

[claydoh]

however every time i try to install linux-firmware i end up with an unusable system.

That makes it hard to determine which specific firmware is causing the issue. In 26.04, linux-firmware is now a meta-package, and there are actually separate firmware packages (see dep list) instead of one monolithic one in Noble and previous, so only ones with changes would get updated, so it will be easier to determine and isolate problems there. But in 24.04 it is all-or-nothing.

But graphics related firmware seems the obvious culprit here.

This bug report seems very relevant, and has a lot of "fire" over a couple of days, so hopefully is addressed soon:

https://bugs.launchpad.net/ubuntu/+s...e/+bug/2163303

Overall bug list for linux-firmware:
https://launchpad.net/ubuntu/+source...by=-id&start=0

[skyfishgoo]

today some new packages appeared on the list and those installed without incident, however every time i try to install linux-firmware i end up with an unusable system.

[skyfishgoo]

Ugh...what happens wheñ u tired from a 12hr nightshift and feel like u wanna contribute something here ... 😆

it's all good, get some sleep

by way of an update, i tried unchecking the firmware boxes in discover's settings but it it still wants to upgrade these packages because they are security updates, not actually firmware updates.

[die.boer]

die.boer, you are not running noble and that's not the version of the firmware package that is causing the problem.

Ugh...what happens wheñ u tired from a 12hr nightshift and feel like u wanna contribute something here ... 😆

[skyfishgoo]

@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

[skyfishgoo]

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.

[skyfishgoo]

die.boer, you are not running noble and that's not the version of the firmware package that is causing the problem.

[die.boer]

just did an update , with firmware included , rebooted and all seems fine here ...

[vanadiumboy]

I looked into it. Apparently, you can easily install an older kernel version (If you have uninstalled it). You can uninstall them and install from Synaptic.

You can't install older versions of linux-firmware without jumping through hoops, locating the cache on your HDD.

There was also a systemd update but again, same issue as for linux-firmware.

Apparently, the safe way to do a rollback is to use the BTRF filesystem or just reinstall Kubuntu from the DVD.

[vanadiumboy]

What is going on? Something is wrong with the latest update and I also suspect it was that linuxfirmware update. Is there a way to revert?

I have 1 monitor connected to a AMD Radeon RX 6800 16 GB, 1920 x 1080 60 Hz. Half the screen is corrupted. It was a bunch of vertical rainbow bars. Blue green yellow red, black and it repeats.
The right half of the screen is rainbow.
I am using the left half right now.
For some reason, when I move the mouse over the corrupted region, it looks fine.

At boot up, the BIOS looks fine, even when I go into BIOS setup (UEFI).
The GRUB menu looks fine.
The Kubuntu logo looks fine and after 20 s it switches to 1920 x1080 I think and the right half is corrupted.

I logged in and changed to lower resolutions but they all seem to have the right half corrupted.

At boot up, I went into GRUB, Ubuntu advanced setting and choose an older kernel but the same issue is present.

[skyfishgoo]

no issues with the simulated command line update... list out the same packages and says they will be installed.

the update proceed orginally without issue as well, but after a reboot when it got to the SDDM screen part it would activate the monitor, but no login screen would appear,

then it would just cycle between that state and fully black with nothing at all on the screen and no response from the keyboard.

only a hard reset would bring me back to grub.

from there i tried all the advanced settings for the current kernel as well as falling back to 6.17 but no change.

so that's when i resorted to restore from snapshot (luckily had a 24.04 live USB in my desk drawer).

edit: i may turn off firmware updates and let the rest go thru to see if that also results in the same problem (but i doubt that it will as that would mean git or yelp took down my system).

[Snowhog]

Not on 24.04, but what 'issues' did you experience?

Now that you are back to before, open a konsole and do a simulated update: sudo apt update && sudo apt --simulate full-upgrade

Are there any actual errors reported?

[skyfishgoo]

had to restore from a timeshift snapshot after applying this update in discover.... two most likely suspects are highlighted.