Sync Updates for Week 30, 2023

ReillyBrogan
Like @WetGeek , I thank you for being so reactive in restoring gnome-mahjongg, we will be able to spend new moments of relaxation ... while working our brains !

Y'all can thank @EbonJaeger for gnome-mahjongg. I just synced his changes.

ReillyBrogan I just synced his changes.

Thanks due to both of you, then. Without @EbonJaeger , you wouldn't have had anything to sync. And without you, it wouldn't have mattered what @EbonJaeger did. You're both part of the best team in FOSS, I'm pretty sure.

DE: Gnome
I see issues with starting applications like gnome-calculator or even nautilus. It has few seconds delay. Anyone got the same? P.S. I disabled extensions before update but now the gui app doesn't even start.

I seem to have a problem with NVIDIA drivers... but of rather strange sort - nvidia-settings drops with a segfault, so do games using proton emulation, but linux-native apps seem to work. Also steam itself refuses to start

Solus Mate geen probleem na update

DE: GNOME, xorg

#delay starting apps
Can't say that this is true for nautilus, but calculator does start with some seconds delay indeed (all extensions disabled).

#cursor bold X
Furthermore, after I hit enter after password-entry in GDM to login, screen turns black to start the Gnome session and then before the Desktop is loaded so to say my mouse curser appears as a bold X, and then turns back to be my normal mouse cursor after Gnome session has fully loaded. Don't think that this has been the case before the update, can't verify though: rollback impossible due to deprecation of gnome-session-shell-experimental.
No I have to admit that I tried to by-pass this by manually installing gnome-session-shell-experimental-43.0-34-1-x86_64.eopkg which conflicted with gnome-session-shell. Then once my entire Gnome Session hang up directly after login. Gnome Session got terminated automatically.
I fixed that with sudo eopkg install --reinstall gnome-session-shell.
Just saying don't know if the X curor thing might be related to this or if it is a general issue.
(Sidenote: we really need ability to do rollback in any cases. I hope the Serpent rebase will offer this)

Thanks for Gnome 44 by the way and pipewire. Now we can finally use screen capture (video) feature of Gnomes own screenshot tool. (Though it does not seem to have capability to record audio)

#Gnome Sound settings - pipewire
So, now this gets complicated to explain. I think enabling pipewire somehow regressed Gnome Sound settings.
Before, I could choose the audio source to be recorded in the Gnome Sound Settings. And it displayed the programs playing audio at the moment including volume meter. Like pavucontrol does.
Now, it does not list the apps playing audio currently any more, and for record source selection, it only lets me choose between "Line in - internal audio" ans "Internal Mic - internal audio".
But for recording sound played by other apps, I need to choose "Monitor of internal audio analog".
Which means I was not able to record this source with audacity for example unless I installed pavucontrol and chose source "Monitor of internal audio analog" there.
Thas does not feel right to me. I should be able to make this settings/selection in the Gnome Sound Settings. No additional app should be needed for this. And I only realized that pavucontrol might help me after someone else mentioned it in this thread before.
By the way, starting audacity does lead to some strange behavior, some kind of icon battle(flickering) in top bar quick-settings-area. Icons flicker, appear, disappear (mic icon amongst others).
Tried to make a video of it. This icon battle does not happen when starting audacity while recording screen-video with simplescreenrecorder if screen-video does also capture audio (pulse-audio), but when recording screen without audio.

#yad
difficult to explain:
I havea script using yad for selecting pass passwords to be copied to clipboars (pass -c). First I enter search term, then i get a yad window showing buttons with all passwords matching, then I can click on the buttons to run pass. If I dont enter search term, i get a yad window with all my pass passwords. Used to work fine. Though, when entering no search term and yad created a window with many buttons (more than 50 certainly), there used to be a delay of several seconds for yas window to appear.
Now, if there is a yad window with many buttons eg passwords, I can see in the gnome top bar that yad has started, but no yad window does appear on screen. If I then perform left mouse click in area where yad window should be, it appears and has also kind of received the mouse click and opens dialog to enter gpg password for the password/button I have chosen(without even seeing the yad window).
Yad works as intended if there are only few buttons.

ReillyBrogan
EbonJaeger

So I'd like to join @WetGeek in thanking you both for your remarkable efficiency (and the Solus team in general).

Hi,

I had no actual problem with the sync update but the microsync caused a few quite annoying ones.
DE: Gnome, first fresh install from two weeks ago.

• Small annoyance since the sync (not tested with Xorg): occasional few second mouse freeze, no more automatic switching between onboard soundcard to the USB one when plugged. I have to use pavucontrol.

• Bigger annoyance since microsync (both Wayland and Xorg sessions): Every gnome app I tried to which the dark theme applies (Files, calculator, etc), plus firefox and libreoffice, flatpaks... load with an additional 20-25s delay whereas the few Qt and Tcl/tk behave as before the micro-sync.
  Dark theme does not apply to some apps anymore and the Gnome ones in that case start without delay (Gedit, Gparted, tweak tool).

I'd be happy to just revert to before the microsync. I hopped on Solus for the rolling release model at my own risks and am very grateful for the dev team hard work.

Also, switching between dark and light themes freeze the mouse for a good 5s and it doesn't make the slow apps load any faster.

@EbonJaeger : I have some questions about the development status of Xfce at this time. As you may remember, I easily created a Solus Xfce VM a while ago, and it went very well. Well enough for me to use it for three straight days as a daily-driver replacement for my laptop (a.k.a. it's host).

I've kept that VM updated, and would be happy to wake it up from hibernation whenever I have time, and use various utilities and applications that I haven't already used, in order to find any issues that may need to be looked at. But I don't want to overstep, or rush the team into anything that they aren't ready for yet.

How interested is the team in forum members' installing Xfce now and using it? Many of us are GNOME Boxes or VirtualBox users, and could easily create an Xfce VM. Are you welcoming this idea or discouraging it for now? If more of us do use it, and find issues that need addressing, should we just file bugs on the Dev Tracker in the normal way, or is it too early to start doing that?

And finally, on a more personal note, has any attention been given to the problem of Wayland locking up when a VM is taken to full-screen? Although I much prefer to use Wayland full time, that limits my VMs to a partial screen. So when I plan to use VMs for more than, say, installing an update, I need to boot into an X11 session. Just wondering whether this issue is getting any attention, either here or upstream.

I have added a list of known issues, solutions, and workarounds to the first post. Please check that to see if your issue already has a fix before posting it again.

WetGeek How interested is the team in forum members' installing Xfce now and using it?

Thanks for the offer.

My €0.02 is that it's better to wait until we publish an ISO to the Crew tier on OC, which will happen soon enough.

ermo it's better to wait until we publish an ISO to the Crew tier on OC

Gotcha. That will also save a step in creating a VM. No need to install one DE, add the Xfce DE, then remove the original one.

Here is Solus 4.4 with Gnome.
After recent update last Saturday I have to click in Gnome Desktop
an application always two times ?! Then it starts - but slowly ?
Seems that Gnome before update ran better, or I have to update Gnome
yet again ?!
What is this ? (Two times click ?! Somewhere else a second DirtyAngel ?!)