Week 9, 2026

ernesto

Everything is fine on XFCE. Great Thanks

VTMarik

So update, i ran pip install pyopenssl just to see what would happen: It found the already extant system package, defaulted to that, complained that pip had a new version (so i updated it) and after all that Deluge just runs like normal.

Not sure what in that step of Windows-esque easter egging did the trick, but that fixed it.

Solarmass

report from Budgie PC: very good update

Original-Syn

On the road but tested on my weak Surface Go 3 and everything worked and it didn't blow up. Thanks for covering the social posts this week.

EbonJaeger

Cherry-picked python-openssl to fix support for newer python-cryptography (fixes crashes with programs like Deluge).

isaak

gnome OK

wingman-4

Pleasant plasma update.

penny-farthing

77 updates for Solus Budgie today and 2 things to report.

1) When Discover finishes processing its updates for Solus, it prompts me to restart, but when I click the corresponding button, nothing happens. Therefore, I have to restart using the User Indicator button in the taskbar.

2) If everything works normally after this update, the sudo eopkg check terminal command still displays the same error regarding the linux-current package. If I apply the suggested fix, it displays an error concerning clr-boot-manager
(it's a problem I already encountered during the previous Solus update, cf. https://discuss.getsol.us/d/12474-week-8-2026/48)

Vérification de l'intégrité de linux-current                                  Cassé
Fichier corrompu : usr/lib64/modules/6.18.13-330.current/modules.softdep

The following packages are broken:
linux-current
Reinstall the broken packages? (oui/non)oui
Taille totale du/des paquets(s) : 238.89 MB
Téléchargement 1 / 1
Paquet linux-current trouvé dans le dépôt Solus
linux-current-6.18.13-330-1-x86_64.eopkg [en cache]
Finished downloading packages.
Désactivation des interruptions clavier pour les opérations sur les fichiers.
Installation 1 / 1
linux-current-6.18.13-330-1-x86_64.eopkg [en cache]
Installation de linux-current, version 6.18.13, millésime 330
Extraction des fichiers de linux-current
linux-current installé
 [✓] Syncing filesystems                                                success
 [✗] Updating clr-boot-manager                                           failed

A copy of the command output follows:

[FATAL] cbm (../src/bootman/bootman.c:L590): FATAL: Cannot mount boot device /dev/sdb5 on /boot: Invalid argument


 [✗] Updating clr-boot-manager                                           failed

A copy of the command output follows:

[FATAL] cbm (../src/bootman/bootman.c:L590): FATAL: Cannot mount boot device /dev/sdb5 on /boot: Invalid argument


 [✓] Running depmod on kernel 6.18.13-330.current                       success
administrateur@solus-pc ~ $ uname -a
Linux solus-pc 6.18.13-330.current #1 SMP PREEMPT_DYNAMIC 2026-02-21 x86_64 GNU/Linux

What can I do?
Thank you in advance for your help and advice.

AAndresH

penny-farthing

Ignore it, it's not a problem that affects the system, I also use Budgie and finding out that is not that this truly broken is a false positive. As long as the system functions is not a problem.

Zenurik

Is the new plasma-login-manager package included in the release?

EbonJaeger

Zenurik Not yet. We're still trying to get it to work.

AlphaElwedritsch

well done on no problems, thanks

berjer

Since the update, Plasma no longer runs.
The start menu does not open with the mouse and only opens with a delay when using the keyboard.

AlphaElwedritsch

If it's no longer running, how can the start menu open, even if with a delay?

berjer

The login window and login function work. The application menu cannot be opened with the mouse.
The application menu opens very slowly with the keyboard. Restarting or shutting down is only possible with the terminal window.
It is on 2 PC's the same

berjer

How can I ignore that the application menu not open with the mouse?
And with keyboard it open after 20-30 seconds

TraceyC

berjer
The post above yours was replying to penny-farthing, as shown above the text.

Please open a ticket on our bug tracker for the bug with the application menu on your systems.

MikeK61

This update didn't go very well on my KDE Plasma.
First Discover stopped the update with disk full error.
So i did it with Solseekand the update finnished.

After reboot i noticed a few crash reports.
kaccess

Hint: You are currently not seeing messages from other users and the system.
Users in groups '1001', 'avahi-autoipd', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
PID: 2293 (kaccess)
UID: 1000 (mike)
GID: 1000 (mike)
Signal: 6 (ABRT)
Timestamp: Mon 2026-03-02 11:48:41 CET (3h 55min ago)
Command Line: /usr/bin/kaccess
Executable: /usr/bin/kaccess
Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kaccess.service
Unit: user@1000.service
User Unit: plasma-kaccess.service
Slice: user-1000.slice
Owner UID: 1000 (mike)
Boot ID: bda7be9177da45a6b865448808dfb8c7
Machine ID: ad6059b5df253cf22323d397513a8861
Hostname: mike-solus
Storage: /var/lib/systemd/coredump/core.kaccess.1000.bda7be9177da45a6b865448808dfb8c7.2293.1772448521000000.zst (present)
Size on Disk: 521.2K
Message: Process 2293 (kaccess) of user 1000 dumped core.

            Stack trace of thread 2293:
            #0  0x00007fb2306a977b pthread_kill (libc.so.6 + 0xa977b)
            #1  0x00007fb230647646 raise (libc.so.6 + 0x47646)
            #2  0x00007fb230629286 abort (libc.so.6 + 0x29286)
            #3  0x00007fb231030dde n/a (libQt6Core.so.6 + 0x230dde)
            #4  0x00007fb23104d31f n/a (libQt6Core.so.6 + 0x24d31f)
            #5  0x00007fb23104f36d _ZNK14QMessageLogger5fatalEPKcz (libQt6Core.so.6 + 0x24f36d)
            #6  0x00007fb2318a871c n/a (libQt6Gui.so.6 + 0x2a871c)
            #7  0x00007fb2318a5cb4 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt6Gui.so.6 + 0x2a5cb4)
            #8  0x00007fb2318a8ac4 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x2a8ac4)
            #9  0x00007fb2310e1292 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x2e1292)
            #10 0x00007fb23189fcde _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x29fcde)
            #11 0x00007fb232239747 _ZN19QApplicationPrivate4initEv (libQt6Widgets.so.6 + 0x239747)
            #12 0x000056247c58a52d n/a (/usr/bin/kaccess + 0x1352d)
            #13 0x00007fb23062b529 n/a (libc.so.6 + 0x2b529)
            #14 0x00007fb23062b5da __libc_start_main (libc.so.6 + 0x2b5da)
            #15 0x000056247c584265 n/a (/usr/bin/kaccess + 0xd265)
            
            Stack trace of thread 2313:
            #0  0x00007fb2306afd02 n/a (libc.so.6 + 0xafd02)
            #1  0x00007fb2306a3ab8 n/a (libc.so.6 + 0xa3ab8)
            #2  0x00007fb23072ac43 ppoll (libc.so.6 + 0x12ac43)
            #3  0x00007fb2308e0bdf n/a (libglib-2.0.so.0 + 0x81bdf)
            #4  0x00007fb2308e0cf8 g_main_context_iteration (libglib-2.0.so.0 + 0x81cf8)
            #5  0x00007fb231412bbe _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x612bbe)
            #6  0x00007fb2310ee646 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2ee646)
            #7  0x00007fb23121cb16 _ZN7QThread4execEv (libQt6Core.so.6 + 0x41cb16)
            #8  0x00007fb23158a3ae n/a (libQt6DBus.so.6 + 0x523ae)
            #9  0x00007fb2312d31d5 n/a (libQt6Core.so.6 + 0x4d31d5)
            #10 0x00007fb2306a783e n/a (libc.so.6 + 0xa783e)
            #11 0x00007fb23073971c n/a (libc.so.6 + 0x13971c)
            ELF object binary architecture: AMD x86-64

Same with xembedsniproxy and
gmenudbusmenupr

eopkg check shows no errors.

I did reboot 2 times.

I would be very grateful for any hints how to solve this.

TraceyC

MikeK61 First Discover stopped the update with disk full error.

I recommend starting a new Support thread for your issue. The first thing you should check is to make sure your disk isn't actually running out of space. But - new thread.

Xoph

All good on 2 Plasma systems. Just had to wait until I got my internet back before upgrading.

Apparently when construction works cut through not one, but 2 major fiber lines coming into the community it can take a while to properly repair.

brent

Xoph Apparently when construction works cut through not one, but 2 major fiber lines coming into the community it can take a while to properly repair.

my ISP is so lackadaisical when this happens. Many days pass. I feel your pain here.

Xoph

brent But hey they said they would credit my account for $10 after not having internet for 2+ days. 🙄😒

« Previous Page Next Page »