Heya folks! It's time for another round of the news!

Much of our focus this week has been on finalizing the Python 3 ports of eopkg and ypkg, and coming up with a solution to transition users during a regular update. This is tricky because Python is an interpreted language, and as such, the package manager does not like having its parts ripped out from under it during use. We think we have a solution, however, which will be tested over the coming weeks to ensure as robust a transition as possible.

Somewhat related, we've been working to support multi-character Unicode symbols (such as emoji) in package update commits and changelogs. Such characters would break the package index under Python 2, thus breaking the repo, as was discovered with signal-desktop and polari, meaning neither package could be updated until the problem was resolved. With the move to Python 3, this is now possible in all but one place: the Software Center, which remains Python 2 since it will Soon™ be replaced by GNOME Software and KDE Discover. When encountering one of the aforementioned characters, Software Center will not attempt to decode the HTML escape sequences in which they are presented, but instead display text that looks somewhat illegible to the naked eye. The win here is that this text no longer breaks anything on the code side, at least.

KDE Frameworks was updated to 6.1, which contains many bug fixes following the Plasma 6 release. You can read all about this update on their website. In addition, KDE Gear has been updated to 24.02.2. This release includes fixes for a crash in kcachegrind when opening the history menu, a broken volume slider in elisa, and gwenview will no longer inhibit suspend when viewing an image, and much more. The full KDE Gear changelog can be found here.

ROCm 6, AMD's open-source software stack for GPU computation, has been brought back! We had previously attempted to upgrade from ROCm 5.7 to ROCm 6.0 in January, but it was quickly reverted after discovering a crash with Blender. After 4 months, we've finally pinned down the bug and found a workaround, so you can now enjoy better performance and wider device compatibility (that is exclusive to Solus) when rendering Blender projects or running ML workflows with PyTorch. A Help Center article for more information on using ROCm is coming Soon™.

We have two deprecations this week: evopop-gtk-theme and qt5-pas. Making its debut this sync is fan2go, a daemon to control the fans of your computer.

General updates

Due to the number of updates this week, and the time it would take to categorize them, we have instead opted to create a GitHub Gist listing all the updated packages this sync.

That’s all for this week, folks! Come back next week for more Solus news!

How did this week's update go for you?

This poll has ended.

    Thank you for another trouble free update.

    Flawless here as well. Updated three Plasma laptops, one Xkde laptop, and one VM for each of the five Solus editions. Not a single error so far. Two desktops to update later, but I don't anticipate any issues with those, either.

    EbonJaeger We have two deprecations this week: evopop-gtk-theme

    users tearfully pleading with you to keep evopop: (crickets)
    /s

    that and mokat are probably the only two that have not graced my Budgie. I like the idea of phasing out some of the 2017-era icon packages.

      New appstream-data cherry-picked. (Just updating data needed for the software centers).

      Everything went well for my Budgie except for integrity of glibc being reported as Broken by eopkg check after this update. Tried reinstalling and rebooting but the issue persists.

      Maybe just one of those false positives we get from time to time?

      Checking integrity of glibc    Broken
Corrupted file: /usr/bin/ld.so
Corrupted file: /usr/lib64/libthread_db.so

        RegularJogger gnome-shell-extension-appindicator and packagekit show up as broken on my GNOME install. Everything does appear to work perfectly fine. Though now that you mentioned glibc showing broken, it shows that for me too.

          After this update (135 packages, 1,37 GiB), the terminal command sudo eopkg check give me also the same error:

          What can we do to solve it ? (I precise that I am a Budgie desktop user)

          Otherwise, nothing else to report at this time.

          Lazarus wont build it has linking issues, is there a way I can roll back?
          Kodi wont open at all missing x11 libs I thought v21 should now be running under Wayland?

          edit - after installing qt6pas-dev i could build but would be good if qt5pas-dev was still available so I can build for older qt5 systems. Also there seems to be a permissions issue. I need to change the permissions on /usr/share/lazarus otherwise builds fail

            same here.
            No reproduction steps, alas : just eopk -up then :
            Vérification de l'intégrité de glibc Cassé
            Fichier corrompu : usr/bin/ld.so
            Fichier corrompu : usr/lib64/libthread_db.so
            meaning
            glibc broken
            corrupted file : usr/bin/ld.so
            corrupted file : : usr/lib64/libthread_db.so
            This is solus with kde.
            Btw : solus is the 1st to incorporate kde framework 6.1. Congrats!!

            Same here:

            ❯ _ eopkg check glibc
Checking integrity of glibc    Broken
Corrupted file: /usr/bin/ld.so
Corrupted file: /usr/lib64/libthread_db.so

            I can confirm that eopkg check reports glibc is Broken on Solus Budgie

            mouse_AUS Kodi wont open at all missing x11 libs I thought v21 should now be running under Wayland?

            Kodi doesn't start here on Solus Budgie too:

            /usr/lib64/kodi/kodi-x11: error while loading shared libraries: libxg.so: cannot open shared object file: No such file or directory

                The update made the "icons" setting on Budgie Desktop blank, giving me an initial shock when I looked at my icons. I manually went in to change it back to what it was previously set as.

                phew, IntelliJ IDEA is working again! I think it was this one:

                xorg-xwayland was updated to 23.2.6-25 (joebonrichie).

                I looked into it last week and considered filing a bug report, but I was lazy and had faith that it would somehow get updated anyway, and lo and behold 😂

                thanks for saving me from having to use vscode!

                • [deleted]

                • Post #20

                This sync also introduces fan2goto the repos, which is a simple daemon for fan speed control written in Go. In comparison to fancontrol it provides multi-point fan curves, should work after resume from suspend and is more hassle-free as it doesn't rely on absolute hwmon paths unlike fancontrol.