Sync Updates for Week 50, 2023

brent

pillmuncher my print dialogue box reverts back to white along with something else minor. I looked in dconf for the hell of it and saw nothing.
nothing to see there.

in theory gnome-settings for me has the master dark on/off. master meaning overrides everything. It's always worked for me before. I'm at a loss.

In budgie settings you said you have both darks (I mean built-in theme on and dark theme on) enabled, as do I. Im running repo Pocillo-Dark and an outside theme (Humanity) that's I've never had any trouble with.
Be curious to see what anyone adds.

EDIT: I think I mean gnome-control-center had the master setting. I don't have it installed.

2nd EDIT: I installed it and my system was set to Dark already vs the 'Default' setting. In the end I had nothing to contribute and I apologize.

pillmuncher

brent But you did contribute. Now I know it's not just me. Thank you!

brent

Axios See if you can tell me whats different?

Resilience? It made it to my budgie 'about' settings.

penny-farthing

brent

I would like to add that if the mention Solus 4.5 Resilience actually appears in the CPU -Z software and in Budgie Control Center, this is not yet the case with the terminal command:

Administrator@Solus -PC ~ $ lsb_release -a
LSB version: 1.4
Distributor ID: Solus
Description: Solus
Release: 4.4
Codename: Fortitude
Administrator@Solus-PC ~ $

Is this normal ?

brent

penny-farthing
my opinion only; I know nothing: resilience not official yet, they are just getting ahead on branding. mylsb_release -a shows the same output because we are still on 4.4.

Harvey

penny-farthing
Reilly has now resolved this. Thank you for bringing it to our attention.

Axios

brent I thought it interesting all the graphical ones report 4.5
the terminal 4.4 oh well we are going forward Ya

Axios

Harvey Cant beat the forum for testing or breaking stuff..!!!
we can do it...lol

penny-farthing

Axios

Sorry I didn't use the right channel to report this bug.
I'll make a note of your comment for next time, thanks.

brent

@Axios @Solarmass @joluveba @ermo @TraceyC @penny-farthing and anyone else interested in the flatpak/broken issue:

basically a temporary non-problem (routing) as explained in detail by @Staudey here: https://github.com/getsolus/packages/issues/1035

FYI

ReillyBrogan

brent I updated it last, I didn't notice that the new tmpfiles they included conflicted with our existing one. I'll fix it sooner than later, but like Staudey said it is harmless and you can ignore the error.

snowee

@Harvey @ReillyBrogan
I encountered an error when I tried to sync today.
I have never seen this error message before.

[image removed as issue is resolved. Thanks Harvey]

May I know what happened in this case and how may I resolve it?

Thank you.

snowee

Replying to my own post, based on Harvey's advice on Matrix-chat.
first do a
sudo eopkg dc, followed by
sudo eopkg up -y

The sync went smoothly after that.

thank you Harvey.

Axios

penny-farthing That was not my intent with that comment.
(Sorry it came across that way) And my poor wording.

I was thinking at the time how that little issue (and others) came about and how as
a group we contributed to Solus With realizing it sometimes.

I never at the time thought about trying terminal
Some the stuff may not be ground breaking but I think in the long run pays off
I just think its all cool and important.

ReillyBrogan

We've done a sync in order to roll up changes for the next batch of RC ISOs. There haven't been too many changes since then so I won't do a new post:

adw-gtk3-theme 5.2
webkit-gtk 2.42.4, including CVE fixes for CVE-2023-42883
Flatpak fixed for duplicate tmpfiles (which was causing the "package corrupted" error message)
lsb-release updated to reflect Solus 4.5 Resilience
usysconf updated to fix a long-standing issue where GTK2 applications would take ₂₅ seconds to appear after launching them. I would like to point out that this issue has consumed a LOT of my time to figure out over the last 4 months and I'm super happy to have finally figured it out.
cpu-x 5.0.2
jq 1.7.1, which includes CVE fixes for CVE-2023-50246 and CVE-2023-50268
Fixed issue with unrar where it crashed on launch if the user did not have an AMD Zen 4 CPU.
A bunch of branding changes and fixes for the ISOs. Not really sure what changed exactly as it was mostly other team members working on them.

Axios

ReillyBrogan Congrats on you usysconf nitemare!
Yes that did make a big difference.
Thanks

Sebastian

ReillyBrogan Yeah. I can confirm that leafpad now starts without delay. Great job!!!

penny-farthing

ReillyBrogan

I confirm that the anomaly encountered on the flatpak package by launching sudo eopkg check has disappeared.

Also, lsb-release -a now displays Solus in version 4.5.

Solus has therefore changed its version number and the ISO image of this new version should come soon, taking into account, of course, the technical constraints to be managed by the team of Solus developers to produce it.

Be thanked. 👏

ReillyBrogan

Axios It wasn't actually an issue with usysconf. The issue is that we weren't creating a certain cache that glib/gtk apps use to avoid having to start a bunch of different modules, and starting all the modules was causing bugs. Usysconf is what is used to run triggers after package updates, so the update to it was just to add a new trigger to generate the cache that glib/gtk needs.

pillmuncher

I need to ask this question again:

Solus Budgie here. The problem I'm having is that all of a sudden Caja (I hate Nautilus with a vengeance), Budgie Control Center, and Software Center aren't displayed in dark mode anymore and I can, for the life of me, not figure out where to set it back to how it was. I checked both gnome-control-center and Budgie Desktop Settings and both were set to Dark Mode. Funnily, the latter was displayed in dark mode. What else could I try?

@brent seems to have the same problem.

« Previous Page Next Page »