Sync Updates for Week 20, 2024

EbonJaeger

Heya folks! It's Friday, and that means updates are headed your way!

As a result of last week's events, we've taken measures to ensure that updating is safe and will not break your system, no matter when you last updated. An in-depth breakdown of what happened will be coming at a later date. We're still working out the details for further steps to ensure that everyone has a fully Usr Merged system in a safe and robust manner. Thanks again everyone for your patience.

Our kernels have been updated to 6.8.10 and 6.6.31 for Current and LTS branches, respectively. @ReillyBrogan switched the kernels to derive from the SOURCE_DATE_EPOCH for the kernel build time.

KDE Frameworks has been updated to 6.2.0. KDE Frameworks are 72 addon libraries to Qt which provide a wide variety of commonly needed functionality in mature, peer reviewed and well tested libraries with friendly licensing terms. See all the changes in this release here.

If you've ever used LibreOffice on Budgie with a light theme, you'll have noticed that the icons are unreadable. This is because we set LibreOffice to use the Sifr Dark icon theme by default. This wasn't an issue on the other editions because they all use dark themes by default, whereas Budgie does not. In order to have readable icons on all editions by default, this week we switched LibreOffice to default to the colored Elementary icons, ensuring that they're readable on all editions of Solus.

Over at Serpent, Ikey has been working on a replacement for clr-boot-manager called blsforme. blsforme is a management tool and library for the Boot Loader Specification. Progress on this tool has been swift and exciting, and adopting it brings us an important step closer to Solus 5. Replacing clr-boot-manager is something we are all looking forward to, as it has caused its share of headaches, and has several drawbacks.

As a result of the recent GLib CVE fix, other bugs have been revealed. One of these causes crashes with Inkscape, gedit, Handbreak, and possibly other programs, when vala-panel-appmenu is installed. We have backported a patch to GLib that fixes this issue, so these applications should no longer crash with vala-panel-appmenu is on the system.

Security updates

There are a few security updates this week:

git was updated to 2.45.1-128 (@ReillyBrogan, @ReillyBrogan). Includes security fixes for CVE-2024-32002, CVE-2024-32004, CVE-2024-32020, CVE-2024-32021, CVE-2024-32465.
libxml2 was updated to 2.12.7-48 (@joebonrichie). Includes security fixes for CVE-2024-34459.

In addition to these, Chromium-based browsers have been updated throughout the week to address zero-day flaws in Chromium: CVE-2024-4761 and CVE-2024-4947. Exploits for at least one of these is known to exist in the wild, so be sure to apply these updates if you're using Brave, Opera, Vivaldi, or any other Chromium-based web browser!

General updates

The full list of updates this week can be found here.

That’s all for this week, folks! Check in next time for more Solus news!

synth-ruiner

EbonJaeger In order to have readable icons on all editions by default, this week we switched LibreOffice to default to the colored Elementary icons, ensuring that they're readable on all editions of Solus.

nice - coloured icons are so much more readable as well. it's baffling that GIMP, Libreoffice et al. even offer monochrome icons as an option...

brent

[thanks to axios I fixed my problem so Deleting Post---also changed my vote]

Axios

brent You can go into settings now and change light dark did you try that.
Could not before

I could not switch it on this theme switched to my backup theme and was able to switch light and dark
interesting.

Staudey

CVE-2024-4761 and CVE-2024-4947. Exploits for at least one of these is known to exist in the wild

Technically true, but to be more precise exploits for both are known to exist in the wild

Google is aware that an exploit for CVE-2024-4761 exists in the wild.
https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_13.html

Google is aware that an exploit for CVE-2024-4947 exists in the wild.
https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_15.html

Axios

No issues.

brent

Axios went thru first two tabs (view and editor) and didn't bother going thru the 3rd & 4th:

thank you!

SethStorm666

No hiccup. Works perfectly! Thumbs up 🙂

Teggs

Is it... is it safe now?

😛

(Just kidding, I already updated.)

Pjol

Two laptops updated 🎉

Thank you to everyone involved 🙂

rincor

Not sure if it's related to this or previous update, but I just did a eopkg check and it lists many broken/corrupted packages, even though the system seems to work fine.
Sample output:

Checking integrity of systemd                                     Broken
Corrupted file: /bin/systemctl
Corrupted file: /sbin/halt
Corrupted file: /sbin/init
Corrupted file: /sbin/poweroff
Corrupted file: /sbin/reboot
Corrupted file: /sbin/shutdown
Corrupted file: /usr/lib/sysctl.d/50-default.conf

Checking integrity of mdadm                                       Broken
Corrupted file: /sbin/mdadm
Corrupted file: /sbin/mdmon
Checking integrity of plasma-systemmonitor                        OK
Checking integrity of kf6-kdoctools                               OK
Checking integrity of util-linux                                  Broken
Corrupted file: /bin/arch
Corrupted file: /bin/cal
Corrupted file: /bin/chfn
Corrupted file: /bin/chmem
Corrupted file: /bin/choom
Corrupted file: /bin/chrt
Corrupted file: /bin/chsh
Corrupted file: /bin/col
Corrupted file: /bin/colcrt
Corrupted file: /bin/colrm
Corrupted file: /bin/column
Corrupted file: /bin/dmesg
Corrupted file: /bin/eject
Corrupted file: /bin/enosys
Corrupted file: /bin/exch
Corrupted file: /bin/fadvise
Corrupted file: /bin/fallocate
Corrupted file: /bin/fincore
Corrupted file: /bin/findmnt
Corrupted file: /bin/flock
Corrupted file: /bin/getopt
Corrupted file: /bin/hardlink
Corrupted file: /bin/hexdump
Corrupted file: /bin/i386
Corrupted file: /bin/ionice
Corrupted file: /bin/ipcmk
Corrupted file: /bin/ipcrm
Corrupted file: /bin/ipcs
Corrupted file: /bin/irqtop
Corrupted file: /bin/isosize
Corrupted file: /bin/kill
Corrupted file: /bin/last
Corrupted file: /bin/lastb
Corrupted file: /bin/lastlog2
Corrupted file: /bin/line
Corrupted file: /bin/linux32
Corrupted file: /bin/linux64
Corrupted file: /bin/logger
Corrupted file: /bin/login
Corrupted file: /bin/look
Corrupted file: /bin/lsblk
Corrupted file: /bin/lsclocks
Corrupted file: /bin/lscpu
Corrupted file: /bin/lsfd
Corrupted file: /bin/lsipc
Corrupted file: /bin/lsirq
Corrupted file: /bin/lslocks
Corrupted file: /bin/lslogins
Corrupted file: /bin/lsmem
Corrupted file: /bin/lsns
Corrupted file: /bin/mcookie
Corrupted file: /bin/mesg
Corrupted file: /bin/more
Corrupted file: /bin/mount
Corrupted file: /bin/mountpoint
Corrupted file: /bin/namei
Corrupted file: /bin/newgrp
Corrupted file: /bin/nsenter
Corrupted file: /bin/pg
Corrupted file: /bin/pipesz
Corrupted file: /bin/prlimit
Corrupted file: /bin/rename
Corrupted file: /bin/renice
Corrupted file: /bin/rev
Corrupted file: /bin/script
Corrupted file: /bin/scriptlive
Corrupted file: /bin/scriptreplay
Corrupted file: /bin/setarch
Corrupted file: /bin/setpgid
Corrupted file: /bin/setpriv
Corrupted file: /bin/setsid
Corrupted file: /bin/setterm
Corrupted file: /bin/su
Corrupted file: /bin/taskset
Corrupted file: /bin/uclampset
Corrupted file: /bin/ul
Corrupted file: /bin/umount
Corrupted file: /bin/uname26
Corrupted file: /bin/unshare
Corrupted file: /bin/utmpdump
Corrupted file: /bin/uuidgen
Corrupted file: /bin/uuidparse
Corrupted file: /bin/vigr
Corrupted file: /bin/vipw
Corrupted file: /bin/waitpid
Corrupted file: /bin/wall
Corrupted file: /bin/wdctl
Corrupted file: /bin/whereis
Corrupted file: /bin/write
Corrupted file: /bin/x86_64
Corrupted file: /sbin/addpart
Corrupted file: /sbin/agetty
Corrupted file: /sbin/blkdiscard
Corrupted file: /sbin/blkid
Corrupted file: /sbin/blkpr
Corrupted file: /sbin/blkzone
Corrupted file: /sbin/blockdev
Corrupted file: /sbin/cfdisk
Corrupted file: /sbin/chcpu
Corrupted file: /sbin/ctrlaltdel
Corrupted file: /sbin/delpart
Corrupted file: /sbin/fdisk
Corrupted file: /sbin/findfs
Corrupted file: /sbin/fsck
Corrupted file: /sbin/fsck.cramfs
Corrupted file: /sbin/fsck.minix
Corrupted file: /sbin/fsfreeze
Corrupted file: /sbin/fstrim
Corrupted file: /sbin/hwclock
Corrupted file: /sbin/ldattach
Corrupted file: /sbin/losetup
Corrupted file: /sbin/mkfs
Corrupted file: /sbin/mkfs.bfs
Corrupted file: /sbin/mkfs.cramfs
Corrupted file: /sbin/mkfs.minix
Corrupted file: /sbin/mkswap
Corrupted file: /sbin/nologin
Corrupted file: /sbin/partx
Corrupted file: /sbin/pivot_root
Corrupted file: /sbin/readprofile
Corrupted file: /sbin/resizepart
Corrupted file: /sbin/rfkill
Corrupted file: /sbin/rtcwake
Corrupted file: /sbin/runuser
Corrupted file: /sbin/sfdisk
Corrupted file: /sbin/sulogin
Corrupted file: /sbin/swaplabel
Corrupted file: /sbin/swapoff
Corrupted file: /sbin/swapon
Corrupted file: /sbin/switch_root
Corrupted file: /sbin/tunelp
Corrupted file: /sbin/uuidd
Corrupted file: /sbin/wipefs
Corrupted file: /sbin/zramctl

And there are many more.
Is this normal?

Harvey

rincor

It's fine. As mentioned in regards to issues in last weeks sync:

The packages are not broken, the package check itself is not handling them correctly. This was mentioned above as eopkg check showing errors, and is expected.

Basically eopkg sucks as a package manager (which is why we're replacing it) and due to it's constraints we found that satisfying all of the following was impossible:

Allowing people who didn't upgrade to the Friday sync to update and have working systems

Allowing people who did upgrade to the Friday sync to update and have working systems

Having a "clean" eopkg check that succeeds for all packages.

Given these constraints we chose the solution that satisfied the first two requirements. That means that eopkg check will show that certain packages (between 20 and 30 depending on what you have installed) are "broken" which is just because it can't handle how the symlinks on the system are setup, not because those packages are actually broken.

Source: https://discuss.getsol.us/d/10599-temporary-blocking-of-updates-now-unblocked/62

algent

rincor correct command is sudo eopkg check

atriaze

top, professional work congratulations to the whole team

Lucien_Lachance

plasma (desktop) + gnome (laptop) updated and all is great.
thanks team

Solarmass

No issues to report!

jimibananas

All went smoothly except I was expecting kernel to update to 6.8.10 for current based on the message above but its at 6.8.9.
uname -a > 6.8.9-289.current #1 SMP PREEMPT_DYNAMIC 0 x86_64 GNU/Linux

I'm using Budgie. Not sure if this is an issue but thought I'd let y'all know. Please advise.

ReillyBrogan

jimibananas Is your boot partition full?

jimibananas

Hello... It doesn't appear to be.
df /boot >
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/nvme0n1p2 999148240 73065648 923027952 8% /

jimibananas

OK... it seems good now. I ran a manual update and after rebooting it was updated to 6.8.10. Everything appeared to go smoothly the first time but I left and maybe it didn't finish. Not sure but thanks for the reply.

[deleted]

Element still doesn't open if not forcing it to use xwayland

EbonJaeger

[deleted] Is there an issue on the packages GitHub page for this?