Solus Update Post for Week 45, 2025

brent

somehow I don't think my Operation-Reinstall-1-Package-At-A-Time-Til-You-Find-The-Problem plan is very well thought out 🙂

Buddies of B gave me the old panel reset command. Maybe that will be next.

Or wait for 4.8 but I won't ask the eta 😉

Back to Endeavour to finish some work. Thanks all who rushed to help me. That's what I LOVE about Solus. You all rock.

brent

Harvey If you decide to roll back then you roll back, not cherry-pick what you will or will not update

lesson learned, thanks Harvey

TraceyC

elfprince Too many components + weekly updates = potential problems and breakage. Not enough time for testing.

This is why we test things in unstable before rolling them out to Polaris. For contrast, I've been running on unstable for a number of years now and rarely run into major bugs.

And, of course, the best way to make sure we have as little disruption as possible is to have more people testing with unstable. Everyone is welcome to test, if their situation allows. We welcome bug reports for bugs and packaging issues.

Original-Syn

TraceyC Same. Only my systems at my office and in the vm lab are on stable as a precaution. The rest are on Unstable. Try to report what I do find and so far nothing serious.

EbonJaeger

Budgie users who are experiencing the crashing issue, please keep discussion about it to this thread so the information is all in one place, and that other replies don't get missed in this thread. Thank you.

TraceyC

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

Have a look at the known issues

palto42

TraceyC In my view the workaround proposed for Signal in known issues is sub-optimal, since it need to be applied per application and only fixes the key access and not the proper desktop detection (e.g. tray icon looks still different).
The root cause of the issue is the change of XDG_CURRENT_DESKTOP in Budgie from Budgie:GNOME to just Budgie which affects all Electron based apps. So the better workaround for me is to revert this change as posted here palto42 (only XDG_CURRENT_DESKTOP needs to bet set).

pomon

brent If the *.xml file is missing, I described a fix to get eopkg working again. You just need to visit the Solus repository online and copy the path to the specific *.eopkg package (either my method or the script by @NigelGreenway below).

EbonJaeger

palto42 The root cause of the issue is the change of XDG_CURRENT_DESKTOP in Budgie from Budgie:GNOME to just Budgie which affects all Electron based apps. So the better workaround for me is to revert this change as posted here

The problem is, this will just cause different problems because it causes a bunch of GNOME-specific processes to start that cause broken-ness with Budgie, as it creates a race condition with Budgie session management and daemon, which is why we changed the value of that variable in the first place.

mbevks

I use the Faba icons and the icon for Veracrypt isn't working anymore. I've temporarily switched to a different icon set but have not otherwise figured out how to fix the problem.

banger

I have multiple Discover entries in the App chooser when you want to run a program and it asks you which to open with. No big deal just a heads up for Plasma.

TraceyC

banger I have multiple Discover entries in the App chooser when you want to run a program and it asks you which to open with.

I see the same thing in Solus as well as Fedora 43, so it's not Solus specific.

Please open a new bug on the KDE bug tracker in the "general" component of the "xdg-desktop-portal-kde" product. Thanks.

brent

Axios Uh when using my laptop a gnome advertisement popped up where notifications usually do
and said gnome needs your help i didnt catch all of what it said.

finally saw this for the first time just now and kinda stared at it for a while.
not something I want to keep seeing but in @Original-Syn 's link they claim
"GNOME users could expect a short, non-intrusive reminder just twice a year—a gentle nudge to support the project that powers millions of Linux desktops around the world"

By my math I won't see this again til April. I'm ok with that because someone will find a way to disable this way before then 🙂 .

Axios

brent You can disable both gnome and kde
For gnome
gsettings set org.gnome.settings-daemon.plugins.housekeeping donation-reminder-enabled 'false'
For KDE
kcmshell6 kcm_kded
Brings up a settings menu and you deselect it and apply

brent

Axios what about budgie?

TraceyC

Axios You can disable both gnome and kde

To clarify - you can disable the donation reminders using these. This will not disable GNOME or KDE.

Axios

brent I used the gnome

EbonJaeger

brent The above will work on Budgie, and any other affected desktop or window manager.

This happens because the notification is a part of gnome-settings-daemon, which will be activated if any application that leverages it is running. Unfortunately, the developers that implemented it didn't think to check what environment was running before sending the notification, as noted upstream in issues such as this one.

I appreciate what they're trying to do, but I wish they had thought this through a little more before shipping it.

brent

Axios I used the gnome

at twice a year I moved it way down my to-do list. 🙂
thanks for getting back to me

Axios

TraceyC Duh I am slow sometimes..lol
will watch my typing

brent

EbonJaeger actually @Axios 's cut and paste took 2 seconds. so no worries. I appreciate what they are trying to do as well (imo not thought through enough but all small potatoes)

« Previous Page Next Page »