Solus Update Post for Week 45, 2025

Original-Syn

brent Yeah meant applets. Every DE calls them something different, lol.
Anyway, good luck. Hopefully the reset works and it is not something else.

diagnostics0

No issues with Gnome after updating and rebooting.

DinimixisDEMZ

All work's fine. GNOME 49.1

johano

On Budgie lost all custom global keyboard shortcuts.

Found a solution here courtesy of jls17

Run this command to move your existing shortcuts to the new location.

dconf write /org/buddiesofbudgie/settings-daemon/plugins/media-keys/custom-keybindings "$(dconf read /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings)"

palto42

On Solus Budgie I get an error when Signal desktop starts.

Signal starts with signal-desktop --password-store="gnome-libsecret" as suggested in the error message.

Similar issue with VScode:

It starts normal with code --password-store="gnome-libsecret"

I could fix the other issue with keyboard custom shortcuts as described by johano

c2p

All works great on KDE-Plasma 6.5.2., thx

AlphaElwedritsch

I can't find any errors or problems with my GNOME system.

The "dash to dock" extension is also working flawlessly.

Julien68

Hello, all good for me on KDE.
Small question: will we have version 6.17 in linux-current, or will we go straight to 6.18 when it's stable?

bubba66

All good on one Gnome box and 2 x Gnome laptops 🙂

palto42

With the help of ChatGpt I found a workaround:

Added the file /usr/share/defaults/etc/environment.d/90-gnome-keyring.conf

XDG_CURRENT_DESKTOP=Budgie:GNOME
XDG_SESSION_DESKTOP=budgie
DESKTOP_SESSION=budgie-desktop

tflovik

Had to open terminal and type reboot to restart the system after updating, this is on Budgie desktop.
Seems like the system now uses 400 Mb more on idle than before, have to watch this to see if it persists.

BuzzPCSOS

Harvey Thanks for the quick reply and possible answer, unfortunately the blur toggle changed nothing. Processor is an i5 gen 7 so not that old.
Updates on my i3 gen 4 tablet went fine so I am guessing that it was something that went wrong during update.
Tried sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall to check the install but something in eopkg has changed because that won't work. I just get eopkg help screen.
Tried to roll back to previous state but that also failed.
At the moment I'm thinking of re-installing which might be the easiest way unless there are any other suggestions.
Thanks.
Edit: Found that I could access eopkg repair via Solseek. Doing that now.

ermo

BuzzPCSOS I think the check command might now have an option to reinstall broken packages on its own?

Relevant Pull Request: https://github.com/getsolus/eopkg/pull/178

HuggleBerry

I had the same errors as already mentioned on Budgie, but additionally right after the update, the shutdown menu wouldn't show up. I had to restart via terminal. Otherwise so far no issues noticed

palto42

On more minor new issue since last update:
I had a custom keyboard shortcut "ctrl + alt + T" for opening a terminal, which doesn't work anymore.
If I reconfigure it, it works until next reboot. Other custom shortcuts work without issues.
I changed it now to "ctrl + alt + A" as a workaround.

ernesto

Everything is fine on XFCE. Thank's to the team

BuzzPCSOS

ermo Thank you for the link. Something seems a little wrong here but I'm not sure what is happening.
I'm pretty sure that running a command like sudo eopkg check | grep Broken | awk '{print $4}' | xargs -r sudo eopkg it --reinstall should display a list of packages that are being checked. All I get is a few minutes of higher CPU usage and then back to start again. Anyhow no improvement so still ongoing. Probably something odd that I have added at some point.

I have a kind of busy day ahead so will not be reinstalling just yet so any suggestions are welcome.
This week I updated via Solseek which did throw up a lot of KDE package errors during the update. No blame to Solseek in any way as it is a really nice wrapper for eopkg, just wish I had made a note of the errors that were thrown up as it could have pointed to the software that I need to reinstall.

tflovik

Budgie desktop is back to normal ram use now after using the system for a while, maybe there was something running in the background when i restarted the system after the update.

paracetamol

I'm on the GNOME flavor and the update looked uneventful at first, but after a while it turns out I've been affected by this bug in Mutter: https://gitlab.gnome.org/GNOME/mutter/-/issues/4416. The issue is keys are repeating indefinitely under certain conditions, such as when switching workspaces. Like the other people in the replies, I also experience it with the VS Code. I suppose the Solus team can't do much about it, so this is a heads up to other GNOME users to maybe not rush to upgrade if you rely on an Electron app such as VS Code. It's not a big problem, but it sure is annoying.

stocc

My Niri / Quickshell / DankMaterialShell installation updated smoothly (as always!)

alfisya

BuzzPCSOS The point @ermo made is that one-liner is not needed anymore. sudo eopkg check should check broken package and the prompt you for a reinstall if a broken package is found. If you use that one liner the prompt will become invisible as you pipe it to grep to only show line with "Broken" string.

Also this means we have to update our docs. Thank you for the reminder. Cheers!

Edit: Docs will be updated.

brent

BuzzPCSOS I'm pretty sure that running a command like sudo eopkg check | grep Broken | awk '{print $4}' | xargs -r sudo eopkg it --reinstall

it never has shown checked packages, I always wondered if it had a --verbose flag but I never tried it it.
PS--tried it yesterday and exited after 5 seconds which I found peculiar. Normally that command takes a while.

« Previous Page Next Page »