Sync Updates for Week 30, 2025

ernesto

Everything is fine on XFCE. Thank's for the job done.

TraceyC

joluveba has apparently disappeared since I updated. You must have touched something that solved it. Thank you!

As much as I'd love for us to be able to take credit for that, it wasn't us. The crash was probably fixed by the plasmashell and/or KDE Connect developers. When we updated the various parts of Plasma, we would have gotten the fix.

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.

penny-farthing

TraceyC

Thanks for your feedback, issue created:
https://github.com/getsolus/packages/issues/6112

Staudey

TraceyC You are correct, the system should retain two kernels for the "current" kernel.

I thought a clr-boot-manager update only keeps the vendor selection (i.e. newest packaged kernel version IIUC), currently running kernel, and most recent successfully booted kernel around. So if you update, reboot at least twice using the new kernel, and then run a clr-boot-manager update (manually or via some package management or usysconf operation) it will delete the old kernel. Or was this changed at some point?

Granted, this might not often happen under normal usage (I'm not sure under which circumstances a clr-boot-manager updateis triggered, outside of a kernel update)

from man clr-boot-manager:

       update
           Perform an update operation on the configured boot directory. This will analyze kernels available from the software distribution that are currently in‐
           stalled, and pick the ideal candidates for installation.

           This includes the current vendor selection for each kernel type, the currently running kernel, and the most recent successfully booted kernel  of  each
           type currently installed.

           All other kernels not fitting these parameters are then removed in accordance with vendor policy, and removed from the boot directory. For UEFI systems
           this is the EFI System Partition..

Harvey

Staudey

I read something similar by silke on our github issues the other day but now I can't find it. I was going to ask if they had manually ran sudo clr-boot-manager update but I went to bed instead.

banger

I am confused as I only have one boot entry which says Solus Endurance 4.7 since the last update. Last week I had the two entries. Eopkg ran clr-boot-manager update and depmod this week. This is on my UEFI system.

Harvey

The older kernel is for emergencies should a newly installed kernel not boot on your system. Even then it will not work in all scenarios such as if you use the proprietary nvidia drivers, in which case booting into the old kernel that used to work before updating would now not work.

So having the previous kernel there is sometimes useful, but it is never required even if something goes wrong. IMO it should delete old failback kernels after awhile even if that results in only having 1 boot choice. Which means even if this is a bug, I think it should become a feature.

brent

Harvey The older kernel is for emergencies should a newly installed kernel not boot on your system. Even then it will not work in all scenarios such as if you use the proprietary nvidia drivers, in which case booting into the old kernel that used to work before updating would now not work.

So having the previous kernel there is sometimes useful, but it is never required even if something goes wrong. IMO it should delete old failback kernels after awhile even if that results in only having 1 boot choice. Which means even if this is a bug, I think it should become a feature.

much clearer picture; that was driving me crazy-schrodinger's kernel. thanks

banger

Harvey IMO it should delete old failback kernels after awhile even if that results in only having 1 boot choice. Which means even if this is a bug, I think it should become a feature.

I thought that was how it was supposed to work!

banger

Anyone tried niri? Couldn't get a niri session to run on a plasma VM but got a niri window to run inside plasma wayland session. Interesting tool.

TraceyC

banger

Please start a new thread since this is a different topic than how the sync went. Thanks.

stocc

banger As TraceyC says, it should be a new thread, but in short, yes I'm running it on my main laptop happily.

Harvey

Cherry-picked vivaldi-stable 7.5.3735.58

« Previous Page