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?

    top, professional work congratulations to the whole team

    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

    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.

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

      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]

      • Edited

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

        Ran an update* this morning (2024-05-19) and noticed that all background images are now gone.
        IOW,

        • Budgie Control Center : Backgrounds is now empty
        • Budgie Control Center : About is now broken
          ---

        updateSolus.sh

        Cleaning package cache /var/cache/eopkg/packages...
        Cleaning source archive cache /var/cache/eopkg/archives...
        Cleaning temporary directory /var/eopkg...
        Removing cache file /var/cache/eopkg/componentdb.cache...
        Removing cache file /var/cache/eopkg/packagedb.cache...
        Removing cache file /var/cache/eopkg/installdb.cache...
        Updating repository: Solus
        eopkg-index.xml.xz.sha1sum (40.0 B)100% 0.00 --/- [--:--:--] [complete]
        Solus repository information is up-to-date.
        The following list of packages will be removed
        in the respective order to satisfy dependencies:
        budgie-backgrounds solus-artwork
        Do you want to continue? (yes/no)yes
        Removing package budgie-backgrounds
        Removed budgie-backgrounds
        Removing package solus-artwork
        Removed solus-artwork
        [✓] Syncing filesystems success
        [✓] Updating icon theme cache: hicolor success
        Updating repositories
        Updating repository: Solus
        eopkg-index.xml.xz.sha1sum (40.0 B)100% 0.00 --/- [--:--:--] [complete]
        Solus repository information is up-to-date.
        No packages to upgrade.


        *update logic

        # cat updateSolus.sh
        
        #!/bin/sh
        # Clean temporary caches from prior downloads
        eopkg delete-cache
        # Update repo
        eopkg update-repo
        # Remove orphans
        eopkg remove-orphans
        # Upgrade system
        eopkg upgrade

        That's all that I've notice so far ...

        PS: maybe editing this message will then show my updated name & avatar?

          technomaji I cannot confirm: my Background and About are populated.
          Did you reboot after that housecleaning above? check broken packages?
          I'm not seeing anything at devtracker or buddies of b.
          That's a weird one.

            For some reason, those commands uninstalled the packages containing all the artwork ajd backgrounds. You could just reinstall them.

              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...

              My Canon Printer didn`t work after update.
              I had to update /usr/sbin/cups-genppdupdate manually.

              Just had to find out.

                brent I'm pretty sure I rebooted ... and discovered the check parameter and ran it, yep. Then saw a message by another user stating that many packages show as broken but that this is a false negative ...

                The other anomaly was that both my laptops, the ThinkPad X220 and esp. the MacBook Pro6,2 2010 started locking up at random intervals after these last two updates the week of Monday 13, 2024. BEFORE these updates, I've been using SOLUS for months without a problem!

                As my desktop system had recently breathed its last, I had to rely on at least one of these laptops. Rather than spend hours and trying to figure out what the problem might be, I've actually replace the OS on the MBP with Debian. Also found a little NUC-like Gigabyte BRIX that already contained an OS. So I'm using it until the new computer arrives which will come with POP OS pre-installed.

                My time has to go into productivity ...

                I will likely come back to SOLUS as it is very solid ... it just doesn't feel solid of late with all the deltas happening.