Sync Updates for Week 30, 2025

alfisya

Heya folks! It's sync day, and that means it's time for the weekly Solus roundup!

This week, Hyprland has been updated to v0.50.1, bringing a slew of improvements and fixes. Notable new config features include: monitor v2 config syntax with HDR rules, and multi-GPU support. See notes here and here.

The NVIDIA GLX driver has been updated to v570.172.08. This should be a minor bugfix release.

Niri, a scrollable tiling Wayland compositor and window manager, has been added to the repository. Out of the box, it is pretty bare. This is because with Niri, you can use just about any programs you want to create your setup; even Xfce panel. XWayland applications can be started thanks to integration with xwayland-satelite. Make sure to install the niri-session package so it shows up on the login screen.

A few packages were added to go along with Niri:

fuzzel: an application launcher.
mako-notify: A lightweight notification daemon.
swaync: The notification daemon for Sway. Includes a notification center.

Aside from Niri, Klassy has been added to the repository. Klassy is a highly customizable binary Window Decoration, Application Style, and Global Theme plugin for recent versions of the KDE Plasma desktop.

If you haven't seen it yet, check out our announcement about updating the localizations for eopkg ahead of the next release. Thank you to all that have contributed!

Security updates

bind-utils was updated to 9.20.11-37 (@silkeh). Includes security fixes for CVE-2025-40775, CVE-2025-40777.
firefox was updated to 141.0-368 (@HarveyDevel). Includes security fixes for CVE-2025-8034, CVE-2025-8044, CVE-2025-8030, CVE-2025-8036, CVE-2025-8038, CVE-2025-8041, CVE-2025-8037, CVE-2025-8032, CVE-2025-8035, CVE-2025-8029, CVE-2025-8031, CVE-2025-8028, CVE-2025-8027, CVE-2025-8043, CVE-2025-8039, CVE-2025-8042, CVE-2025-8033, CVE-2025-8040.
httpd was updated to 2.4.65-34 (@davidjharder, @davidjharder). Includes security fixes for CVE-2025-49630, CVE-2024-42516, CVE-2025-49812, CVE-2025-54090, CVE-2024-43204, CVE-2025-23048, CVE-2025-53020, CVE-2024-47252.
libxml2 was updated to 2.13.8-56 (@silkeh). Includes security fixes for CVE-2025-49794, CVE-2025-49796, CVE-2025-6121, CVE-2025-49795, CVE-2025-6170.
perl-authen-sasl was updated to 2.1800-12 (@silkeh). Includes security fixes for CVE-2025-40918.

General updates

The full list of updated packages can be found here.

For the list of currently known issues, see the dedicated thread for it. If you begin experiencing a bug, please look for an issue on our issue tracker, and open a new one if one does not exist.

That’s all for this week, folks! We'll be here same time, same place next week for another roundup of the news!

brent

just 7 packages in budgie. rebooted. all good. 👍️

banger

22 Packages in 2 Plasma machines. Brave on opening closed immediately but seems ok now after reopening.

Original-Syn

Budgie, KDE, Gnome, and XFCE test VMs all look good. KDE across 3 bare metals look good.

SethStorm666

All went well and thanks for putting Klassy into the repo 🙂

AlphaElwedritsch

6 packages on gnome went smooth

BuzzPCSOS

All good on Plasma.
Discover is behaving reliably since I uninstalled Software Centre using sudo eopkg rm solus-sc solus-sc-icons Well worth the effort.
Looking forward to seeing what the future brings for Solus.

bubba66

Budgie box says all is well, thanks 🐧

penny-farthing

15 system updates to process in Solus today, and nothing special to report except this.

Before processing this update, two kernel versions briefly appeared during boot:

- version 6.15.6-321
- version 6.14.11-320

and that is normal.

But, since this update, I only have one kernel version:

administrateur@solus-pc ~ $ uname -a
Linux solus-pc 6.15.6-321.current #1 SMP PREEMPT_DYNAMIC 2025-07-11 x86_64 GNU/Linux
administrateur@solus-pc ~ $

Sure, the computer works, but if for some reason I needed to downgrade the kernel version, I couldn't do it now.
What happened to get to this point? (unless I'm mistaken, there was no kernel update in this Solus update today (I have the Budgie version of Solus)).

Thanks in advance for your help and advice.

brent

penny-farthing Sure, the computer works, but if for some reason I needed to downgrade the kernel version, I couldn't do it now.
What happened to get to this point? (unless I'm mistaken, there was no kernel update in this Solus update today (I have the Budgie version of Solus)).

If you downgraded then I don't know why the currenct disappeared.
But why did you have to downgrade kernels again?

After update (I agree not sure there was a new kernel this week) my first two look like this in Budgie:
Solus 4.7 Endurance 6.15.6-321.conf
Solus 4.7 Endurance 6.14.11-320.conf
EFI yadda
Firmware yadda

Let me get this straight. After last update (yesterday) one of your kernels got disappeared?
[I can't tell which from your pictures].
And after for some reason you downgraded?
And now there is one kernel and it's not even identified in picture?

If all that's true then it makes sense one of the 15 packages kidnapped the kernel (sorry couldn't help myself). On paper, that is.
If you mystery-downgraded the kernel you can certainly install the new one...
then with two kernels see what the boot menu says (?).

nkwh

Brand new to Solus and going all in ...this morning's updates on Dell XPS 9350 laptop, Lenovo "chrultrabook" (both Budgie) and HP ProDesk desktop (Xfce) all seem to have gone well.

Original-Syn

nkwh Welcome to the community.

Solarmass

all good here o Budgie, nice sync 8/10 🙂

penny-farthing

brent

Perhaps I didn't express myself clearly (I'm not fluent in English (I'm French), so I use a digital translator to communicate in this forum), so please forgive me.

What I meant was that before processing the Solus update today, I had two kernels (v 6.15.6-321 and v 6.14.11-320).
After the update, there was only the kernel v 6.15.6-321, and I didn't do anything else afterwards.
Another thing: before the Solus update, the kernels were clearly identified at boot time; after the update, only “Solus 4.7 Endurance” was displayed at boot time (see screenshot above) and only kernel v 6.15.6-321 remained available.
But, unless I'm mistaken, my system should normally retain the two latest kernel versions.

That's why I wrote this post.
Should I be worried?

brent

penny-farthing Perhaps I didn't express myself clearly (I'm not fluent in English (I'm French), so I use a digital translator to communicate in this forum), so please forgive me.

please forgive me, sometimes I have to read a post 3-4 times then I overthink it..but I coulda swore you said downgrade a couple times.

But should you worry?
I will let someone more qualified than me answer this.
My personal opinion is you are in the right kernel so that's good...the only worry is why the last update disappeared the kernel...or at least made the conditions so your Boot Manager won't show it. But then again if it were there uname would be showing it...

hope someone can explain this ^^^^ this to you. I dont know what circumstance would cause a whole kernel and boot entry to suddenly disappear.

banger

penny-farthing

Clear boot manager removes the old kernel if there have been no bad starts eg non booting Solus. This was done on the last update and is automatic.

If you update from the command line you will see this happening in real time along with depmod I think due to new nvidia drivers.

Hope that is clear (boot).

TraceyC

penny-farthing What I meant was that before processing the Solus update today, I had two kernels (v 6.15.6-321 and v 6.14.11-320).
After the update, there was only the kernel v 6.15.6-321, and I didn't do anything else afterwards.
Another thing: before the Solus update, the kernels were clearly identified at boot time; after the update, only “Solus 4.7 Endurance” was displayed at boot time (see screenshot above) and only kernel v 6.15.6-321 remained available.
But, unless I'm mistaken, my system should normally retain the two latest kernel versions.

You are correct, the system should retain two kernels for the "current" kernel. Please open an issue (if there isn't one already) on our bug tracker for this. By opening an issue, it will allow our developers to look into it and keep track of progress. Thanks.

brent

banger Clear boot manager removes the old kernel if there have been no bad starts eg non booting Solus. This was done on the last update and is automatic.

How come I have a fallback kernel (2 kernels) and he does not I wonder? (both budgie).
(I'm starting to confuse myself 🙂 )

MikeK61

It depends how often you reboot.
If you reboot or turn your PC on every day it happens faster of course.
After some (3-5) boot processes without any failure clr boot manager removes the older kernel.
I only reboot once a week because i suspend my compuiter at night, so it takes longer of course.

brent

MikeK61
Solus 4.7 Endurance 6.15.6-321.conf
Solus 4.7 Endurance 6.14.11-320.conf
EFI yadda
Firmware yadda

this ^^ is the way Budgie has looked to me for almost a decade. I don't have any memory of having no fallback and/or one kernel.
I shut down every night plus a reboot for any/all updates so I reboot approx 8-10 times a week.

I feel like this is a Twilight Zone episode but in reality I must be missing something. Time to drink.