Heya folks! It's sync day, and that means it's time for the weekly Solus roundup!

KDE Plasma has been updated to 6.3.4 this week. This is a minor bugfix release. Highlights for this version include a fix for glitching while scrolling with touch, and stop replaying scrollbar mouse events to the same position in KStyle. Check out the full release announcement here. Qt6 has also been updated to 6.8.3. Their announcement can be found here.

GNOME was also updated to 47.5. This is a bugfix release for the 47 series. @joebonrichie is also already working on packaging GNOME 48, so stay tuned!

Next sync, we will be updating our LTS kernel to the latest in the 6.12 series. After that update, both of our kernels will be on 6.12 for a little bit before the -current branch is moved to 6.14 series. Kernel 6.6, you gave us the incredible 6.6.6 release, and the even better 6.6.66 release. We'll never forget you.

If you haven't already, we encourage you to try using GNOME Software or KDE Discover instead of the Solus Software Center for your package management needs. The more people that test them, the better we can make the experience!

Future ISOs will come with KDE Discover on Budgie, Plasma, and Xfce, and GNOME Software on GNOME.

We have a couple of new packages in the repository this week. First up is OpenSnitch. OpenSnitch is an interactive firewall inspired from Little Snitch. Users are able to monitor and view outbound connections. At the moment, the ebpf modules are not packaged, meaning that vpn users who use wireguard will not have access to the internet.

Secondly, Deskflow has been packaged up. Deskflow is the official upstream project for Synergy, the project that spawned the forks barrier and input-leap. They have recently re-focused on the OSS side of their project. It appears to be well maintained, and supports the Synergy protocol, unlike the alternatives.

General updates

The full list of updated packages can be found here.

For the list of currently known issues, see the dedicated thread for it. If you begin experiencing a bug, please look for an issue on our issue tracker, and open a new one if one does not exist.

That’s all for this week, folks! We'll be here same time, same place next week for another roundup of the news!

How did the sync go for you?

This poll has ended.

    I am on budgie Opensnitch doesnt seem to be starting unless I am missing something
    Rebooted even
    SC installed some python stuffs
    Just part when run from terminal I think its the important

    WARNING: system tray not available. On GNOME you need the extension gnome-shell-extension-appindicator.
	Read more: https://github.com/evilsocket/opensnitch/wiki/GUI-known-problems#gui-does-not-show-up
	If you want to start OpenSnitch GUI in background even if tray not available, use --background argument.

[notifications] show() exception: You must call notify2.init() before using the notification features.
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/opensnitch/notifications.py", line 104, in show
    ntf.show()
  File "/usr/lib/python3.11/site-packages/notify2.py", line 222, in show
    nid = dbus_iface.Notify(appname,       # app_name       (spec names)
          ^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/notify2.py", line 66, in __getattr__
    raise UninittedError("You must call notify2.init() before using the "
notify2.UninittedError: You must call notify2.init() before using the notification features.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/opensnitch/service.py", line 224, in __show_gui
    self._show_systray_msg_error()
  File "/usr/lib/python3.11/site-packages/opensnitch/service.py", line 239, in _show_systray_msg_error
    self._desktop_notifications.show(
  File "/usr/lib/python3.11/site-packages/opensnitch/notifications.py", line 107, in show
    raise Exception("[notifications] show() exception:", e)
Exception: ('[notifications] show() exception:', UninittedError('You must call notify2.init() before using the notification features.'))
Aborted

    Ran from terminal (sudo opensnitch-ui --background ) and it started giveing me notifications but could not surf anywhere once I hit allow
    Would have to crash it again but said something about not finding python3-Notify? maybe we missing it?
    I did not see it in SC

      Same, can't start Opensnitch on Budgie

      Everything good on Plasma Wayland for me. Another big thank you to the Solus team. Good work.

      EbonJaeger

      Thanks, 68 packages (1,09 GiB) updated in Solus and nothing to report at this time.

      My daily desktop is Budgie desktop.
      I tested recently Discover and I must that I prefer it to Gnome Software.

      Actually, Solus Software is set to display a notification when new updates arrive; this doesn't seem to be the case for Discover (unless I'm not looking in the right place).
      Is this configurable (and if so, how to do?) or will I have to check every Saturday if updates have been sent?
      This would be particularly useful when urgent security updates need to be processed quickly, such as those for web browsers for example.

          penny-farthing

          Discover has notifications and is configurable. I have not tested discover's ability to show notifications outside of Plasma however. They should be enabled by default.


              Everything OK with my three computers.

              I'm using Gnome Software for some time now, but I have a problem that sometimes it is stuck in infinite loading. I have no idea why or how to find out why is that happening.

                Harvey

                OK thanks, I found where it is.
                We must click on the 3 vertical dots in the top right-hand corner, then on “Configurer les mises à jour...”. (Configure updates...), like below:

                I noticed that in your screenshot, the "Apply system updates immediately" option is checked: wouldn't it be better to select the "After reboot" option?
                Thank you in advance for your feedback.

                    penny-farthing I noticed that in your screenshot, the "Apply system updates immediately" option is checked: wouldn't it be better to select the "After reboot" option?

                    If you are fine having to reboot after every update, sure. Offline updates can provide a smoother experience.

                    Personally I will not be enabling it. I am on the unstable repository sometimes updating multiple times per day and I do not really gain anything from this option, I can deal with any issues that may arise by not enabling it.

                    AlphaElwedritsch not every update requires a reboot, so why always reboot...

                    The average user has no idea what updates need a reboot and which do not. Some major updates to systemd. DE, etc can cause breakages / weirdness until you reboot. Unfortunately the ability to reboot / shutdown via the GUI is sometimes part of what breaks or worse the entire computer appears to stop responding.

                    Offline updates solve these types of issues and probably should be enabled by default.

                        AlphaElwedritsch not every update requires a reboot, so why always reboot...

                        I reboot religiously after updates. Maybe so no surprises later.

                          I have no choice but to reboot, because I always run my updates at the end of the day, before shutting down. 😆

                          While we're talking reboots, Gnome Software asks for a reboot while sudo eopkg up does not. Is there any reason why it does this?