Sync Updates for Week 27, 2025

AlphaElwedritsch

Gnome user: 393.27 MB
Did the security updates already as cherry-picked
No issues at all.
Once more again, Thanks a lot...

and yes, I rebooted this time too😉

brent

AlphaElwedritsch and yes, I rebooted this time too

🙂 nice

VaSAMiAn

no problem here on budgie (laptop Asus TUF DASH F15)

MetaNorm

My system is still not booting with the latest kernel. Glad that I can use 6.14.6-319 as fallback option. I hope for future updates that solve the problem.

penny-farthing

48 system updates to process for Solus in Discover today.

I encountered the same issue again described in the following post:
https://discuss.getsol.us/d/11724-sync-updates-for-week-25-2025/13

I am a French Budgie user and I uninstalled Solus Software, as suggested, by typing the following command:
sudo eopkg rm solus-sc solus-sc-icons
I precise that I configured Discover to apply system updates after rebooting.

Today, after selecting "Tout mettre à jour" (Update All) and then "Re-démarrer" (Restart), the reboot occurred with the processed task counter showing 50%. During the reboot, no packages to process were displayed, and when I logged in, the system updates to process were still present.
So I repeated the process in the same way, and during the reboot, the packages to be processed were displayed, prompting another reboot. When I logged in, I could see that the system update had completed successfully.

I plan I will configure system updates in Discover by opting for "Immédiatement" (Immediately) in the future, and then I will restart my computer once they're complete so they're operational.

Otherwise, nothing else to report since processing this update.

Solarmass

penny-farthing I plan I will configure system updates in Discover by opting for "Immédiatement" (Immediately) in the future, and then I will restart my computer once they're complete so they're operational.

not a fan of offline updates too? 🙂

ernesto

NO problem on xfce. Thank's for the job done.

abentroth

I just installed the update. Everything is fine on my system, Solus 4.7
Gnome 47 updated to Gnome 48, everything is running fine
Thank's for the job done.

banger

Keyboard backlight brightness control seems to have disappeared in Plasma. 😮

banger

banger Keyboard backlight brightness control seems to have disappeared in Plasma. 😮

And now its back after a reboot.

Original-Syn

Finally got around to being able to update and test, been on vacation. All tested good.
Configs tested and working...

QEMU VM: Solus Budgie ✅
Framework 13 AI300: Solus Plasma ✅
Thinkpad T14 Gen 1 (Intel 10th Gen): Solus Plasma ✅
Legion Laptop 8845HS w/Nvidia dGPU: Solus Plasma ✅

SilverBird775

~~Cannot boot with kernel 6.14.11, had to choose the previous 6.14.6. Looks like it hangs on amdgpu leaving all displays in sleep mode.~~

AMD RX6600

Edit: Weird! It seems booting fine now with 6.14.11, but I didn't change anything at all, except choosing via GRUB the previous kernel two times. It's something about the postponed graphics firmware update, I guess?

MetaNorm

SilverBird775
You're in luck. My system is still hanging. No graphic signal seems to be given up. The monitor switches to energy saving mode. Kernel 6.14.6-319 is the last suitable version.

penny-farthing

Solarmass

Not in the current context... although in theory, that should be the obvious choice.
But nothing serious either; the important thing is to be able to properly process the Solus updates sent by the development team. 😉

EbonJaeger

Cherry-picked valkey for CVE-2025-32023 and CVE-2025-48367.

SilverBird775

MetaNorm What makes it scarier, I got into a very similar situation with all-AMD notebook before. Promised smooth first time linux experience to my bro while finally managed to convert him away from windows... well, you guess it, the live CD is totally hangs on booting with a display blank. Found the archive Solus ISO, flashed, installed, updated. It kind of works now, yet keeps hanging on hibernation wake up. The point is, I skipped like a 3 years of updates and I'm not even sure next updates will not cause it to break again. As I learned from my googling, the drivers are trying some firmware features that are expected to be found but de-facto they are stubs or bugged. It seems at some point this APU was blacklisted to not use advanced BIOS features which made kernel bootable again. Sorry to be not much of help. It's Linux, so it happens. I'm not a fan of the imposed firmware updates because of the cases like this.

banger

My Discover just updated my KEK CA. For the dumb, what is it. 😃

Original-Syn

banger KEK (Key Enrollment Key) is a for updating the Secure Boot database (DB) and the forbidden signature database (DBX). The DB = list of trusted software and drivers, while the DBX = list of blocked or malicious ones.

banger

Original-Syn

Many thanks I wondered why a Discover asked for a reboot. Curiously it said Microsoft KEK CA which puzzled me.

MetaNorm

SilverBird775
I'll wait for a few more updates and try switching over to LTS Kernel.
Btw I never had serious issuses during my time with Solus. There were little things with my StarLite Tablet (maybe to exotic hardware), but not with my main machine. Lets hope we are facing just a temporary problem.

AlphaElwedritsch

banger For some things it is simply a matter of being patient 😉