Sync Updates for Week 25, 2025

EbonJaeger

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

Mesa has been updated to 25.1.4. This update includes a fix for certain applications only showing a black window when launched. The full changelog can be found here.

The image editor GIMP has been updated to 3.0.4, the first of the 3.0 series to reach the Solus stable repository. GIMP 3.0 is the end result of seven years of hard work by volunteer developers, designers, artists, and community members. There are a lot of changes, including a move from GTK 2 to GTK 3. Check out their release announcement for further details. NOTE: If GIMP crashes on your system, and you're on Wayland, ensure that the environment variable GTK_MODULES does not contain appmenu-gtk-module. As long as you've installed all updates and rebooted, this should not be the case.

Next week, we will be changing the eopkg symlink to point to the Nuitka-compiled eopkg.bin version of Eopkg. We've been working on this for a while, and we now feel that it is ready to become the default over the original Python 2 version. This is the next big step towards removing Python 2 from our repository, and it's been a long time coming. Users on the Unstable repository are encouraged to help test eopkg on the command line once the update lands after today's sync.

We have a couple of new packages this week. First is nautilus-open-any-terminal, a Nautilus extension adding a context menu entry for opening other terminal emulators than gnome-terminal. Secondly, we have dool, a command line tool to monitor many aspects of your Linux system, including CPU, memory, network, load average, and more. dool is a successor to dstat, which was discontinued in 2019.

Security updates

We have a handful of security updates this week. Make sure to install updates to get the latest vulnerability fixes.

httrack was updated to 3.49.6-9 (@davidjharder). Includes security fixes for CVE-2017-14062.
jq was updated to 1.8.0-11 (@androidnisse). Includes security fixes for CVE-2025-48060, CVE-2024-23337, CVE-2024-53427.
valkey was updated to 8.1.2-5 (@androidnisse). Includes security fixes for CVE-2025-27151.
xorg-server was updated to 21.1.18-108 (@HarveyDevel). Includes security fixes for CVE-2025-49180, CVE-2025-49179, CVE-2025-49175, CVE-2025-49177, CVE-2025-49176, CVE-2025-49178.
xorg-xwayland was updated to 24.1.8-35 (@HarveyDevel). Includes security fixes for CVE-2025-49180, CVE-2025-49179, CVE-2025-49175, CVE-2025-49177, CVE-2025-49176, CVE-2025-49178.

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!

brent

EbonJaeger Next week, we will be changing the eopkg symlink to point to the Nuitka-compiled eopkg.bin version of Eopkg. We've been working on this for a while, and we now feel that it is ready to become the default over the original Python 2 version. This is the next big step towards removing Python 2 from our repository, and it's been a long time coming.

🏆️
that's huge.

Updated, rebooted, tried most of the updated apps, everything is groovy. thank you all.

IBurntMyRice

EbonJaeger changing the eopkg symlink to point to the Nuitka-compiled eopkg.bin version of Eopkg

Will this have any notable differences to the current Eopkg package, or is it simply a Python 3 version?

Original-Syn

Tested Budgie VM and Plasma bare metal. Quick tests show no issues so far.

banger

Plasma all good on 2 bare metal. 🙂

Axios

All good on known issues (plasma)
opensnitch still does not run.

Thanks for all the hard work and listening to our grumblings.

alfisya

IBurntMyRice For now, it is pretty much 1:1 port. We do have some planned(wishlist) improvement but it will only happens after full transition for users is completed.

FAb7D

Gimp 3 !!!! 🥳 Great update!

ermo

Imagine that:

ermo@virgil:~
$ eopkg --version
eopkg.bin 4.2.1 ()
ermo@virgil:~
$ ls -l /usr/bin/eopkg*
lrwxrwxrwx 1 root root        9 Jun 21 11:59 /usr/bin/eopkg -> eopkg.bin
-rwxr-xr-x 1 root root 10346293 Jun 14 03:51 /usr/bin/eopkg.bin
lrwxrwxrwx 1 root root        9 Jun 21 11:59 /usr/bin/eopkg-cli -> eopkg.bin
-rwxr-xr-x 1 root root     2178 Jun 21 02:01 /usr/bin/eopkg.py2
ermo@virgil:~
$ /usr/bin/eopkg lr
Solus [inactive]
   https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz
Unstable [active]
   https://cdn.getsol.us/repo/unstable/eopkg-index.xml.xz
ermo@virgil:~
$ pisi --version
bash: pisi: command not found
ermo@virgil:~
$ eopkg.py2 --version
eopkg.py2 3.12.5
ermo@virgil:~
$

@sheepman4267
Using pisi to hand over ownership to eopkg.bin (and disabling the pisi executable/link)?

Cheeky. And clever. 🧠 🤘 😎

Does this mean you're all set now for the epoch bump where the eopkg.py3/eopkg.bin packages own the respective symlinks? Because I am guessing you are...

sheepman4267

ermo
It just seemed like the easiest way to get py3 eopkg into production. Trying to reduce the number of big changes all happening at once during the epoch.

Which... Is the next task! There's still work to be done on the mechanics of the transition, but we are close. I'm just happy that we've got python 2 out of production use. Can't wait to get it uninstalled.

johano

All good on laptop and desktop, exciting to hear plans around eopkg and the deprecation of python 2. Great work!

Thanks to @algent for the speedy packaging of Ulauncher 6!

ernesto

HI
Everything is fine on XFCE.
Thank's to the team for the work done.

penny-farthing

26 system updates processed in Solus today (187.26 MB), but Discover is having trouble during processing these updates.

Indeed, when I click "Tout mettre à jour" (Update All), I then select "Re-démarrer" (Restart), and then, normally, the task counter in the bottom left corner increments in % and should then restart the computer; there, the Solus system updates are processed and, once completed, generate a new reboot.

But nothing like that today: after selecting "Tout mettre à jour" (Update All), then the "Re-démarrer" (Restart) option, the reboot started a few seconds later, without waiting for the countdown of tasks to be processed. When I logged back in, I noticed that the Solus system updates weren't being processed.
I tried the operation again, and the result: the same thing.
I did it again one last time: after rebooting, the system updates were processed, then after the second reboot, after opening a new session, I noticed that these updates were processed correctly.

This is the first time this has happened to me on Solus Budgie.
What do you think about it?

EbonJaeger

penny-farthing Do you still have solus-sc installed? Having another software center installed tends to interfere with offline updates, no matter which one you're using.

TraceyC

penny-farthing

I wasn't able to reproduce this on a system that still has Solus SC installed, but there could very well be a race condition or other conflict condition I didn't run into. I recommend removing the Solus SC and trying again.

It's safe to uninstall Solus SC and its icon pack with

sudo eopkg rm solus-sc solus-sc-icons

If you still run into this bug, please open an issue on our bug tracker for this. By opening an issue, it will allow our developers to look into it and keep track of progress. Thanks.

We'll look at publicizing this conflict to void further problems.

penny-farthing

EbonJaeger

TraceyC

Thank you both for your answers. 👍

So, I validated the recommended terminal command, then restarted my computer.
I will keep you informed after the next sync day.

Does this also mean that the solus-sc package will be removed from the next ISO image for version 4.8 of Solus? (since KDE Plasma, Budgie and XFCE opted for Discover and Gnome for Gnome Software)

Lucien_Lachance

all good, just waiting for 6.4 🙂

unclemez

Lucien_Lachance 6.4.1 was released already
maybe that one will be shipped, who knows

TraceyC

I've added a note in the known issues about the software center conflicts, with the remedy.

TraceyC

penny-farthing (since KDE Plasma, Budgie and XFCE opted for Discover and Gnome for Gnome Software)

That's a good question. This situation brings up an aspect of our Software Center transition that hadn't been clear until now. The Solus Team will take this into consideration as we plan 4.8, which will install Discover or GNOME Software by default.

I had been working on an FAQ, which I've now published, that mentions this.

penny-farthing

Since this Solus update, the software Safe Eyes doesn't open anymore:
(*) It's an application which protect your eyes from eyestrain with pause reminder.

pascal@solus-pc ~ $ safeeyes
Traceback (most recent call last):
  File "/usr/bin/safeeyes", line 33, in <module>
    sys.exit(load_entry_point('safeeyes==2.1.6', 'console_scripts', 'safeeyes')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/bin/safeeyes", line 25, in importlib_load_entry_point
    return next(matches).load()
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/importlib/metadata/__init__.py", line 205, in load
    module = import_module(match.group('module'))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 999, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/usr/lib/python3.12/site-packages/safeeyes/__main__.py", line 32, in <module>
    from safeeyes import utility
  File "/usr/lib/python3.12/site-packages/safeeyes/utility.py", line 24, in <module>
    import imp
ModuleNotFoundError: No module named 'imp'
pascal@solus-pc ~ $

Why is this happening and what can I do?

alfisya

penny-farthing Axios Fix will be coming next sync (Or soon if it is cherry-picked). Cheers!

Edit:
It is on unstable now. You can try it but be cautious. I think it is safe tho.

sudo eopkg it https://packages.getsol.us/unstable/s/safeeyes/safeeyes-2.2.3-16-1-x86_64.eopkg