Heya folks! We're here with another update post!

KDE Plasma has been updated to 6.1.2 this week. This release contains a bunch of bug fixes for the 6.1 series. The full list of changes can be found here. Alongside Plasma, KDE Gear was updated to 24.05.2. This version has many bug fixes, including fixing a memory leak in the EWS resource for kdepim-runtime, fixing "This file does not exist" after clicking on a folder in kio-gdrive, and fixing a crash caused by clicking the remove mount point button in partitionmanager. If you want to see the full changelog, click here.

The NVIDIA GLX driver has been updated to 555.58.02. The 555.58 version brings many fixes and enhancements. Perhaps most notably, it brings explicit sync support for Wayland, a significant benefit for users using NVIDIA hardware on Wayland. With explicit sync, there should be reduced latency, improved frame pacing, and better stability. Check out this article for more information. Additionally, all of our NVIDIA driver packages now support early Kernel Mode Setting (KMS), allowing the graphics driver to initialize earlier in the boot process.

BuildKit makes its debut in the repository this week. It is a concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. If you build and use Linux containers, definitely check this out!

A slew of housekeeping updates have gone in this week. While many of those don't have any version changes, they add homepages to packages, add missing AppStream metainfo files, and fix failures to build. While not the most glamorous, this work is nonetheless important.

As we said last week, a taskforce has been created to perform this work, which includes, but is not limited to:

Most of these tasks are beginner-friendly, and can be a great way to learn Solus packaging. We invite anyone that has the time and inclination to join us!

If you would like to join:

  1. Join Solus Packaging Room on Matrix
  2. Read and practice our packaging documentation
  3. Submit your first Pull Request. We recommend doing the homepage task
  4. Follow along the review process until your PR gets merged
  5. Continue on contributing!

Security updates

We have a few security updates this week. As always, be sure to install updates as they come for the latest in vulnerability protections.

General updates

The full list of updated packages this sync can be found here.

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

How did the sync go for you?

This poll has ended.

Smooth sync. I don't fully understand it, but as I see it, gnome-software isn't normally supposed to immediately download available updates and will wait 2 weeks, unless one of them is flagged as critical. Every sync so far G/S, with my preference for automatic update checking enabled, has indeed staged the updates ready for offline install. At least it confirms that auto updates work properly on my end. Either way, I'm happy to see boring updates where nothing goes horribly wrong.

This page I found explains how updates normally function: https://wiki.gnome.org/Design/Apps/Software/Updates#Tentative_Design

Note that Evan made a small mistake, we updated to Plasma 6.1 this sync which should have received a more expansive section in the notes but I think he thought we just updated to a new minor release. I'm sure he'll correct it sooner or later.

Everythig seemed to work well for my Plasma laptop. The only immediately obvious change I've noticed is in the "dock" panel. Whereas it's been recuced to a tiny square with colored dots for icons for quite a while, in this version it's a single full-size square with what can only be described as "colored slices" that now represent the 11 icons. And as before, clicking on the dock and entering edit mode cures it, so just an inconvenience.

So, apparently the dock has received some attention this week, maybe just not enough.

Oops please delete, as I found the info 🙂

  • [deleted]

  • Post #8
  • Edited

I'm having some problems with the mouse pointer freezing for a second or two every now and then.

At the moment this is not a big thing as it doesn't happen to often but I wanted to mention it just in case.

    Hey guys,
    After this sync, when i wake up my computer from sleep i have this :
    I guess the 555.58 driver maybe ? I use Plasma edition and X11. After some try i observe booting with Wayland fix the issue.
    Best regards

    [deleted] ,
    Hi, I actually have the same problem here but I am unable to say when it happens. Nothing important though.

      • [deleted]

      • Post #12

      Actually this mouse freezing is quite annoying sometimes. : )

      • ermo replied to this.

        [deleted] Actually this mouse freezing is quite annoying sometimes. : )

        • Which kind of mouse do you use and how is it connected to your system?
        • Which Desktop Environment do you use?
        • If your DE is Plasma or GNOME, which session (Wayland or X11) do you use...?

        Please be aware that we can only help you with this kind of "my thing does this weird thing" report if it contains the above information at a minimum. 🙂

            • [deleted]

            • Post #14
            • Edited

            ermo Damn it! I'm sorry! I'm an idiot! I realized later that I forgot to add basic information.

            Mouse: HP 430 Wireless Mouse connected through a USB stick.
            Desktop Environment: Plasma 6.1.2
            Wayland session running on Nvidia Geforce 1660 Super mobile version.

            Do I need to look in the Info Center and give you more detailed information?

            edit: You know, I have to mention the fact that my wireless mouse (irrelevant of make and model) can run laggy (but not freezing) when heavy torrent downloads are running. Earlier when I first mentioned the problem I was running only a web browser (with only a few tabs opens), now I'm running a web browser (with many tabs open), a torrent download manager (with very slow downloads running), a file manager and a music player and it seems to freeze a bit more often and for slightly longer periods of time then it did in the morning.

            edit 2: I've been editing some ebooks today running a web browser (with many tabs open), a file manager, an ebook editing app, an ebook viewing app and an image viewer and the mouse cursor would stutter heavily especially when editing large ebooks.

              Sync went fine as usual!

              Except for a weird crash I'm experiencing attempting to open images via Gwenview or simply Gwenview itself. I'm on plasma.

              1) I attempt to open an image/gwenview and it freezes the whole desktop session
              2) At first Gwenview appears to be running as expected, then everything stops. All other running programs become non responsive. The only thing working is the cursor.
              3) It lasts for at least 10-15 seconds before the desktop session restarts, after that all programs resume as they were
              4) Except gwenview. It doesn't actually load/open at all, therefore the image doesn't either.

              Tried restarting the computer, reinstalling gwenview etc but to no avail.

              Any help is appreciated 🙂

                ReillyBrogan

                Any image file, but gwenview itself won't open and crashes. Yes, Plasma. X11.

                  Solus Budgie, AMD 7800x3d, Asrock mobo, Nvidia rtx series

                  After sync, waiting 2 minutes, and doing a reboot, my computer hang at the "ASrock" logo.

                  Mouse and keyboard does nothing.
                  Rebooting several times does nothing.
                  Going to BIOS will lead to hard crash, need to hard power off and power on.
                  I cannot turn off BIOS quiet mode as BIOS will crash immediately after entering.
                  Cannot load my Solus 4.5 ISO from USB stick

                  UPDATE
                  Reilly Brogan assisted me over the course of 2 hours on Matrix and resolved my issue.
                  I am thankful for his help.
                  Both my desktops are running fine now.

                  For self-reference in future
                  Ctrl-Alt-F3
                  login on CLI
                  sudo usysconf run -f
                  sudo reboot

                  I tried to sync my old computer which is running Solus Budgie and have not been updated for one month.
                  I came across this error message.

                  I waited for 10 minutes and my keyboard and mouse crashed. I couldn't do anything.

                  i have no choice but to do a reset, and/or hard reboot

                  After reboot :
                  [FAILED] Failed to start lightdm.service - Light Display Manager
                  I'm at a loss at what to do now.

                  I lost my 2 desktops today, after performing the same sync.
                  Desktop 1 : synced, rebooted, stuck as "ASRock" logo, crashes at BIOS.
                  Desktop 2 : synced one month's worth of packages, 329 packages, 2.2GB, stuck at "Updated clr-boot-manager ... running" wait for 10 mins and crashed, reboot and it shows [FAILED] Failed to start lightdm.service - Light Display Manager

                  If anyone can help me, please contact me on Matrix support channel. I'm there today.
                  Thank you very much.

                  UPDATE
                  Reilly Brogan assisted me over the course of 2 hours on Matrix and resolved my issue.
                  I am thankful for his help.
                  Both my desktops are running fine now.

                  For self-reference in future
                  Ctrl-Alt-F3
                  login on CLI
                  sudo usysconf run -f
                  sudo reboot

                  Hello,

                  The Nvidia driver 555 bricked both of my system with Gnome and Plasma. Just black screen without any way to get to CLI, completely bricked. A hard boot is needed. I then went to do a clean install on both systems and everything is fine and dandy until I install the 555 driver then the same thing happens.

                  I have a 1070 (stationary) card and a 1050 (laptop)