Heya folks! It's time for another weekly roundup of the happenings in Solus!

We have a couple of new additions to the repository this week: skanpage. This is a scan-to-PDF tool for KDE Plasma. If you need to scan documents, you may want to check this out. For those of you who develop with Clojure, you may be interested in the inclusion of polylith. It serves as a tool to help build reusable Clojure components.

Thanks to @ReillyBrogan, our systemd is now built with libaudit and libseccomp support. Audit messages are now collected in the system journal, meaning that AppArmor denied messages are now readable with journalctl. The auditd daemon has been disabled, since these changes make its operation redundant.

Also from @ReillyBrogan, the kernel package was updated to v6.6.16, with the BORE CPU scheduler updated to v4.1.8. We also enabled transparent huge pages by default, which should improve performance slightly for most desktop workloads. Some other changes were made to try to get automatic memory ballooning as a VM guest working, but unfortunately, there still seems to be a missing piece here. We're working on it though!

@joebonrichie spent a lot of time updating our libicu stack to version 74.2. This includes support for "new characters, emojis, security mechanisms, and corresponding APIs and implementations". You can read their release overview here.

Our glibc package was also updated this week. We were on version 2.36 for an extended amount of time before finally updating to 2.38, and now we are at version 2.39 shortly after its release; a massive improvement to our time between updates. While it likely won't directly affect regular users much, it might be nice for developers who can take advantage of new functions and improvements.

The Alsa stack was updated to v1.2.11 this week. This should bring the latest support and fixes for audio hardware to your desktops and laptops!

Security updates

As always, we bring you more security updates. Make sure you're applying all updates to make sure you are protected!

First up is an update to python-notebook to 7.0.7 by @algent, resolving two vulnerabilities:

Next up is eza, an ls replacement tool written in Rust. @EbonJaeger updated it to 0.18.2 to address this security issue:

@ReillyBrogan updated libuv to 1.48.0, fixing this vulnerability:

Earlier this week, @Harvey updated our WebKit packages to 2.42.5 to address multiple CVEs. These updates have been cherry-picked to the stable repository already.

Media updates

Gaming updates

  • citra was updated to 2090 (@infinitymdm)
  • fuse-emulator was updated to 1.6.0 (@malfisya)
  • gem was updated to 0.12.0 (@malfisya)
  • hatari was updated to 2.41 (@malfisya)
  • Heroic Games Launcher was updated to 2.12.1 (@infinitymdm)
  • mangohud was updated to 0.7.1 (@ReillyBrogan)
  • mbga was updated to 0.10.3 (@malfisya)
  • mupen64plus was updated to the latest git sources (@Staudey)
  • pcsx2 was updated to 1.7.5543 (@malfisya)
  • ppsspp was updated to 1.17.1 (@malfisya)
  • retroarch was updated to 1.17.0 (@ReillyBrogan)
  • steam was updated to 1.0.0.79(@Staudey)
  • stella was updated to 6.7.1 (@malfisya)
  • vice was updated to 3.8 (@malfisya)
  • visualboyadvance-m was updated to 2.1.9 (@malfisya)
  • yuzu was updated to 1704 (@infinitymdm)

CLI tool updates

System updates

Language updates

Other desktop updates

  • anki was updated to 23.12.1 (@Staudey)
  • birdtray was updated to 1.11.4 (@david)
  • bitwarden-desktop was updated to 2024.2.0 (@ReillyBrogan)
  • Blender was updated to 4.0.2 (@davidjharder)
  • Brave was updated to 1.62.162 (@algent)
  • brewtarget was updated to 3.0.11 (@Harvey)
  • ddcutil was updated to 2.1.3 (@ReillyBrogan)
  • Filezilla was updated to 3.66.5 (@Harvey)
  • Firefox was updated to 122.0.1. Note that we had to disable PGO building while we troubleshoot a build failure with it, so it might be slightly slower than usual until we get that figured out. We also fixed an issue that could cause webcam input to not be sent in WebRTC meetings (@ReillyBrogan)
  • fritzing was updated to 1.0.2 (@palto42)
  • homebank was updated to 5.7.4 (@algent)
  • LibreOffice was updated to 24.2.0.3 (@algent)
  • logseq was updated to 0.10.6 (@ReillyBrogan)
  • mozjs was updated to 115.7.0 (@ReillyBrogan)
  • Numix icon themes were updated to 24.02.05 (@algent)
  • Opera (stable) was updated to 107.0.5045.15 (@Harvey)
  • papirus-icon-theme was updated to 20240201 (@Staudey)
  • protonmail-bridge was updated to 3.8.2 (@FriesischScott)
  • poppler was updated to 24.02.0 (@ReillyBrogan)
  • scrcpy was updated to 2.3.1 (@Staudey)
  • syncthing was updated to 1.27.3 (@ReillyBrogan)
  • Telegram was updated to 4.14.13 (@ReillyBrogan)
  • texlive was updated to 2023.2 (@joebonrichie)
  • transmission was updated to 4.0.5 (@Staudey)
  • torbrowser-launcher was updated to 0.3.7 (@Staudey)
  • Vivaldi (stable) was updated to 6.5.3206.61 (@Harvey)
  • vscode was updated to 1.86.1 (@ReillyBrogan)
  • wxmaxima was updated to 24.02.0 (@malfisya)

That’s all for this week, folks! Tune in next week for another weekly roundup!

How did the sync go for you?

This poll has ended.

    This update personally victimized me and I want my money back

    thanks for the heads on the FF update. Does not feel sluggish at all; feels faster!

    this is an observation not a complaint. observation as in 'I really don't care, I thought you might like to know.'

    I think since the beginning of my solus journey nothing has changed: I do an update then open terminal and reboot. This time it threw a bunch of red letters saying "blah blah inhibit blah blah inhibit blah must add inhibit blah blah blah." I interpreted that as permissions and I was right. sudo reboot made the system reboot where I am encountering no problems.
    No big deal. On the importance scale: 0 (zero).

      Everything installed just fine, but I was really hoping that skanpage would work for me. It also installed without a problem, and created a menu item, but when I tried to launch it, nothing happened. So, I tried to launch it in a terminal, and this was produced:

      QQmlApplicationEngine failed to load component
      qrc:/qml/MainWindow.qml:331:26: Type ContentView unavailable
      qrc:/qml/ContentView.qml:67:13: Type DocumentPage unavailable
      qrc:/qml/DocumentPage.qml:14:1: module "org.kde.kquickimageeditor" is not installed

      Looks like some dependencies weren't included in the package.

        No worries on updates (but did check flatpak while I was at it they have updates to)

        alfisya if you install kquickimageeditor, does skanpage run?

        Yes, and I answered the question,"will this work for me"?

        I put a letter-size color page on the platen, but nothing happened when I clicked to scan it. Maybe I'll be able to figure it out if I fuss with it a bit.

        EDIT: There was also an error message saying "Error during device I/O" that disappeared after a few seconds. The workstation is a fully updated Plasma desktop. The connection is wi-fi, and obviously the connection was good, because it listed my printer/scanner.

            WetGeek from what you said, two things are happening.
            1) Scan button, when pressed, does not skan
            2) scanner does not even see a document....unless "no images" means you put a document in that only has lines of characters/type and it does see it(?).

            recognizes Epson, sees Epson, talks to epson..but can't print and cant see whatever you layed on tray/platen....makes no sense.
            unless it's deps like you said? or driver/plugin...?

              I will fix Skanpage right after lunch. I must have had kquickimageeditor already installed for something else so I didn't pick up it's absence in my testing.

              WetGeek

              I can confirm that this also worked for me, installing kquickimageeditor after installing skanpage.

                EbonJaeger I still have the bug with the workspace switcher on Budgie. If I click on the icon of a program in a different workspace, nothing happens. I have to click on the blank space around the icon to move to that workspace. I assume this is a Budgie bug but wanted to note it here too.

                    This sync didn't pop up for me initially. GNOME Software didn't show any system updates (yes I know G/S and Discover are unsupported and experimental in Solus at the moment. I'm using it at my own risk / discretion). But it also didn't show up when I ran sudo eopkg upgrade. eopkg historyshowed that the repository was updated, but updates just didn't appear.

                    I was able to fix it and here's what I did:
                    sudo eopkg delete-cache
                    sudo eopkg rdb
                    Finally I checked for updates in the usual fashion and they appeared again.

                    brent @EbonJaeger

                    sudo requirement for reboot did not persist after 2nd reboot. We're back toreboot now. It worked itself out.