03.05.2019 Sync Report

JoshStrobl

dbarron Great to hear your update went smoothly for both Budgie and Plasma!

Lucien_Lachance

adapta theme is a bit broken https://i.imgur.com/Mn72HSY.png 🙁 (i know thats not solus' fault, and that its unmaintained)
and i dont like plata, so reverted to good old arc which seems fine

@JoshStrobl it seems the top icons thing is fixed in 3.32.2, i forgot ,what is the solus policy on such incremental updates? will we have them at some stage or are we sticking with 3.32.1 until 3.34.1 (or 3.36.1 or whatever) ?

JoshStrobl

Lucien_Lachance We'll be upgrading to GNOME Shell 3.32.2 (and all the other point releases for various GNOME software) when it's released. Right now they're still on GNOME Shell 3.32.1. That being said, I'll look into how trivial it'll be to backport that to our GNOME Shell for the time-being. We only hold off entire GNOME Stack upgrades for the larger updates / new series (so like 3.34).

Edit: I've updated the original post to have notes about Adapta and more information about Top Icons.

JoshStrobl

Update: Fix looks trivial. I'll see about backporting it.

Lucien_Lachance

JoshStrobl awesome 😁

JoshStrobl

@Lucien_Lachance Please re-enable Top Icon Plus extension, run the following command, and reboot. Let me know if it resolves your CPU usage issue. If so, I'll push it to stable.

sudo eopkg install https://packages.getsol.us/unstable/g/gnome-shell/gnome-shell-3.32.1-41-1-x86_64.eopkg

Lucien_Lachance

JoshStrobl works 😃 thanks a lot

mariojuniorjp

JoshStrobl Many thanks! This solved my problem.

JoshStrobl

@Lucien_Lachance Synced to stable. I'll update original post in a sec. Thanks for helping test!

dbarron

I did find one thing broken in Plasma, it doesn't find my sound devices at all, whereas they're fine in Budgie in the same install.

Device-1: AMD Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X]
driver: snd_hda_intel
Device-2: AMD Family 17h HD Audio driver: snd_hda_intel
Sound Server: ALSA v: k5.0.7-114.current

brent

I had 174(!) packages--like a fresh install!
But went smooth.

I am only responding to this post to say noticed I no changes in Budgie. All seems fantastic as usual. I'm noting no font or icon changes or anything else. Graci.

edit: typo

brent

brent Re-booted and double-checking since I don't want to eat my words. As far as Icons, my Faba trash can got fat, ugly, and metallic. That is all.
Tiredof Faba anyways, so just switched to Paper. It's lovely. File this under 'don't care.'

Lucien_Lachance

there seems to be a small graphical bug, maybe its well known i dont know, when rclicking a folder in nautilus on solus gnome, happens with arc, adapta, plata and adwaita, those are the ones ive tested

JoshStrobl

Lucien_Lachance Appears to be an issue with either GTK3 3.24 or Nautilus, as it happens regardless of what Nautilus release you're on: https://gitlab.gnome.org/GNOME/nautilus/issues/974

beerminer

After update, I am booting straight to TTY (not getting the desktop). I suspect it has something to do with the NVIDIA driver, but I do not know what to do - I have nvidia-glx-driver-current installed.

JoshStrobl

beerminer I would make sure you've done a full upgrade and don't have broken packages. Run:

sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

We have not updated the kernels during this sync cycle, as that is slated for tomorrow by @DataDrake

Junglist

beerminer
When I installed this round of updates last week (I temporarily switched to the unstable repo) I had the same issue twice.

One time, it occurred out of nowhere (it was not the 1st boot after installing updates), the 2nd time a game played via Wine crashed my system, and it happened after I rebooted.

Both times I resolved the issue by using eopkg history to roll back the update.

beerminer

JoshStrobl I tried that, but nothing came up broken.

JoshStrobl

beerminer

What desktop environment are you using and with what login manager? (For example, Budgie and MATE default to LightDM+slick-greeter, whereas GNOME defaults to GDM, but you can also use GDM with Budgie or MATE).
What graphics card?
Could you run sudo journalctl -b -e (basically means "show me the system log for this boot, move the pager to the end of the log) and see if you see any greeter, X11, or desktop failures?
Do you have automatic login enabled?

beerminer

JoshStrobl 1. I am using GNOME

Gigabyte GeForce GTX 1060/REV 2.0 G1 Gaming 6G
These are the lines with errors:
line 744 - failed to query NVIDIA devices
line 764 - failed to start NVIDIA persistence daemon
line 904 - unrecoverable failure in required component org.gnome.Shell.desktop
last couple lines - 2 statements of: gkr-pam: unable to locate daemon control file
I do not have automatic login enabled.

Tourette

I have Solus installed on a 128GB SSD, but it reports that it has a 640GB disk

JoshStrobl

Tourette I don't see how that's relevant to this specific update?

@Lucien_Lachance Yea I'm able to reproduce the issue. Seems to be an upstream GNOME Shell issue, no fix for it yet though: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1059 - Fortunately most users aren't going to be randomly restarting GNOME Shell.

Lucien_Lachance

there is also an issue on gnome with apps that are minimized when doing alt-f2+r, they become like ghost apps, some transparent and some not, they cant be clicked and only revert to normal after selecting them in alt-tab or by min/maxing them by other means. big screenshot
https://i.imgur.com/FRLsKSP.png

Tourette

JoshStrobl

I'm using Solus Budgie 4.0 and the About section in the Control Center used to show that the main disk is 128 GB. Now, after the update it shows a 640 GB disk, even though it's on the same disk. That's all.

JoshStrobl

beerminer The persistence daemon issue is currently normal and shouldn't affect reaching login. Did you have any extensions enabled for GNOME Shell or PAM modules enabled? If not, I would try:

Re-installing GNOME Shell, GDM, and gnome-session: sudo eopkg install --reinstall gnome-shell gdm gnome-session
Resetting world-clocks: dbus-launch gsettings reset org.gnome.clocks world-clocks
You may have a setting in dconf that is causing issue, you can try moving your settings file: mv ~/.config/dconf/user ~/.config/dconf/user.bak