Week 7, 2026

Clintre

flanier Looking at the original PR it looked like it was more for testing and validation then. So not sure if there are plans beyond that at this point.

Harvey

Probably will move to sudo-rs at some point since from memory its what AerynOS uses already, but it would require more staff testing before we make such an important change.

banger

All good on Plasma #2 i5. 😃

CorvusRuber

Is anybody having issues with flatpak updates ? Unprivileged updates (flatpak update from terminal or running discover and waiting for the updates to show) seemingly hang forever, while sudo flatpak update works (even if slower than usual).
I noticed this strange behavior yesterday, before updating, and it keeps happening also after today's updates.

mkl

CorvusRuber Is anybody having issues with flatpak updates ?

No. Everything's normal.

However, that sounds more like peering issues with your provider than problems with SOLUS.
Flathub's repository is behind a Fastly CDN. You might be having peering problems with Fastly CDNs.

joluveba

CorvusRuber Yes, today I had the same issue with flatpak. Curiously, flatpak packages got updated correctly.

Clintre

CorvusRuber I noticed this before this update. I did a repair on flatpak.

flatpak repair

mkl

Everything is fine with GNOME.
However, we've only been on version 49.4 since this week, not since last week as announced in the last sync.

bubba66

The Gnome box updated no problem and the Budgie laptop is also happy 🙂

Thank you

CorvusRuber

mkl However, that sounds more like peering issues with your provider than problems with SOLUS.

First thing I thought, but that should equally affect flatpak update and sudo flatpak update.
Instead, only the unprivileged updates hang.

BuzzPCSOS

All good on Plasma. Many thanks to the team. More great work.

mkl

EbonJaeger but not least, is Fresh, a terminal text editor and IDE.

I've tried it, but I'm still a micro fan.

ernesto

Everything is fine on XFCE. Great thanks to the team

CorvusRuber

Clintre

That seems to work, tried now and immediately after tried to update. No hanging (and one stray update done)

mkl

OK, so it goes on the list of lifesaving commands 😉

Clintre

mkl
It is also in Solseek as "check" under thr tools section.

FAb7D

I'm reporting this issue (with the help of gemini 😛) encountered on my Solus system (LVM on LUKS setup) following a sudo eopkg upgrade.

The issue details:
During the update process, I received errors regarding "low space on /boot" (or similar metadata/file writing errors). I manually deleted the older kernels to free up space, but after rebooting, I noticed that /boot/EFI/com.solus-project/ was missing or empty, even though the system had successfully booted into the latest kernel.

[ERROR] cbm (../src/bootman/bootman.c:L379): No matching kernel in ///usr/lib/kernel, bailing
 ~ $ sudo clr-boot-manager remove-kernel com.solus-project.current.6.17.8-324
~ $ sudo clr-boot-manager list-kernels
* com.solus-project.current.6.18.9-327
 ~ $ sudo clr-boot-manager update
 ~ $ ls -lh /boot/EFI/com.solus-project/
ls: impossibile accedere a '/boot/EFI/com.solus-project/': File o directory non esistente
 ~ $ sudo ls -lh /boot/EFI/com.solus-project/
ls: impossibile accedere a '/boot/EFI/com.solus-project/': File o directory non esistente

It became clear that my EFI partition (/dev/nvme0n1p1) was not being mounted to /boot by the OS. Because the partition wasn't mounted, eopkg and clr-boot-manager were targeting the /boot folder on the root partition instead of the actual ESP, leading to the space errors and the mismatch I observed.

System Details:

Storage: NVMe

Encryption: LVM on LUKS

Kernel: 6.18.9-327 current

How I fixed it:
I checked my /etc/fstab and noticed the entry for the EFI partition was entirely missing. I manually added the following line:
UUID=1506-3AC5 /boot vfat defaults,errors=remount-ro 0 2

After running sudo systemctl daemon-reload and sudo mount -a, the partition mounted correctly, and a subsequent sudo clr-boot-manager update successfully synced the boot files and cleaned up the leftovers.

My Questions:
Is it normal for an LVM+LUKS installation to omit the /boot entry in fstab?
Does Solus rely solely on systemd-gpt-auto-generator for EFI mounting, and if so, why might it fail in an encrypted LVM environment?
Should I be concerned about any side effects of having this manual entry in fstab for future updates?

Thanks in advance for your help!

Staudey

FAb7D Is it normal for an LVM+LUKS installation to omit the /boot entry in fstab?

Only thing I know is that clr-boot-manager only mounts /boot on-demand when it needs to (or you manually issue the command). This should usually work fine so I have no idea what happened in your case that made it necessary to mount it permanently

Harvey

Cherry-picked opera-stable v127.0.5778.64 for CVE-2026-2441

psymage

Think this update might have fixed some occasional flickering I was having on the desktop just recently. Didn't start having that until a little while after the update last Friday but it's gone now. Haven't had it at all since updating last night and I've been on the PC all day today (this would happen at least once or twice a day during the week, if not several times).

JayC

Everything worked great for me.

« Previous Page Next Page »