Just updated on Budgie. Was able to login, lock screen, change theme without issue ?

budgie-extras applets if you happen to use them

Who isn't? :D
All supported applets are working fine.

Budgie here, so far so good, I feel that the session is opening faster :)
sleep & hibernate are ok.

Items tested and working:

• Abiword
• Claws Mail
• Polari
• Quod Libet
• gtkhash

Tested Transmission, downloaded an iso without issue

Tested IBUS with the following keyboards/character pickers:

• English
• Spanish
• Russian
• Japanese (had to launch ibus-daemon with the panel)
• Emoji
• Unicode

gThumb open and edit an image using the tools crop, rotate and resize.
bookworm open an ebook and a PDF file. Increase/Decrease font size, align lines right and left, dark mode and try different profiles.

Budgie: After the update I noticed that some of my applets were gone. I tried to open Budgie Desktop Settings, which restarted the panel. Trying to open it again showed the "Oh no, something went wrong!" screen and forced me to log out.
I get these messages when trying to open Budgie Desktop Settings:

Apr 18 17:58:00 solus-pc budgie-panel[2524]: Settings schema 'com.solus-project.budgie-wm' does not contain a key named 'pause-notifications-on-fullscreen'
Apr 18 17:58:00 solus-pc audit[2524]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined pid=2524 comm="budgie-panel" exe="/usr/bin/budgie-panel" sig=5 res=1
Apr 18 17:58:00 solus-pc kernel: traps: budgie-panel[2524] trap int3 ip:7fa497f3fee7 sp:7ffc9ef4d4c0 error:0 in libglib-2.0.so.0.6800.1[7fa497f02000+8b000]
Apr 18 17:58:00 solus-pc gnome-session[2309]: gnome-session-binary[2309]: WARNING: Application 'budgie-panel.desktop' killed by signal 5
Apr 18 17:58:00 solus-pc gnome-session-binary[2309]: WARNING: Application 'budgie-panel.desktop' killed by signal 5

On the other hand I just played a round of Gnome Mahjongg without issues :)

If you tried opening up Budgie Desktop Settings and it crashed, as well as seeing the below mentioned log item, then that's curious indeed. The respective schema was correctly added by @serebit in this commit, so it would have the schema. Is it possible you're not running our Budgie somehow, ever compiled it from source yourself? That would explain the Budgie Desktop Settings crashing the panel, since that happens if you are using a Budgie Desktop that isn't compiled against the new gsettings-desktop-schemas and gnome-settings-daemon, since I have a patch in our Budgie which uses the right keys from the right schema for font-hinting and font-antialiasing.

Apr 18 17:58:00 solus-pc budgie-panel[2524]: Settings schema 'com.solus-project.budgie-wm' does not contain a key named 'pause-notifications-on-fullscreen'

It'd also run counter to @algent's testing of budgie-extras applets. I've personally tested the screenshot applet and it functions, didn't see any missing and our ABI has not changed.

Tested Vocal, added podcasts from iTunes search and directly from URL, played podcasts without issue. Scrolling through audio, skip button working as expected.

I noted that the mouse-over text in the taskbar is weird. See image. I don't have a second Budgie machine to confirm this on, someone else will need to try it.

Notes on the new Budgie sync for those testing this upgrade:

• If you notice the Budgie panel crashing at any point (which can be either restarting or vanishing entirely), report it with any journalctl logs from budgie-panel from the time of the crash.
• If you use the existing "Disable Night Light mode when windows are fullscreen" or the new "Pause notifications when windows are fullscreen" settings, please report if you find an application that does not properly trigger either of these.

If you encounter these issues, report them on the Budgie issue tracker. They are unlikely to be Solus-specific.

@JoshStrobl So I did a eopkg it --reinstall budgie-desktop and restarted. While I had to re-add most of my applets, everything works fine now. Guess there might have been some leftover from when I built my own Budgie for testing. Sorry for the confusion!

Budgie issues should be reported on its own issue tracker @serebit, not here. We state it on the welcome section of Phabricator. Budgie issues may not be Solus specific.

@davidjharder Vocal reports its WM_NAME and _NET_WM_NAME as "com.github.needleandthread.vocal" instead of just Vocal, so it shows up as that. Once you pin, close, and re-launch it, Budgie will use the DesktopAppInfo. There is probably some refinements we can make around that in.

Sorry, I only added it to my previous comment at the bottom, but GNOME Mahjongg works correctly (played two games without any issues).

I think it can already be updated next Saturday

Various fixes for GNOME Shell have been synced via R993:b917bf05685c: Sync with git.. If you use GNOME Shell, I encourage you to update and test.

I'd like to add that I use GNOME and have had no major issues with this upgrade. I haven't yet tried the new patches yet though.

Using Budgie and it seems like I am stuck with Night Light enabled at a specific temperature and with no way to turn it off, unfortunately. Could not use throwback without switching back to the stable repository, either, due to the removal of the epihany package.

In T9683#183757, @Phantop wrote:

Using Budgie and it seems like I am stuck with Night Light enabled at a specific temperature and with no way to turn it off, unfortunately. Could not use throwback without switching back to the stable repository, either, due to the removal of the epihany package.

It's configurable using both the Night Light section under the Display panel in GNOME Control Center, as well as more granular control using the Night Light applet. Working fine here. If you are having issues with it, I would appreciate if you could file a bug at https://github.com/solus-project/budgie-desktop/ with your journal content during the night mode setting temperature changing so I can see if there is an issue in GNOME Settings Daemon or Mutter for it (or a fix already in place).

Tested Lyx: Created a test document viewed the pdflatex output, used spellcheck. Works as expected.

@Phantop Any chance this was after some sort of power saving mode, like screen dimming enabling or wake-from-suspend? Seeing https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1835

@Phantop I think i have the same issue, had a red/orange tint on the screen after updating, turning Night Light off did not change anything. Found that changing color profile for my screen, brought back the normal colors i was used to. In my 4 years on Solus the color profile have been the same (the name of my monitor), and i have not had this issue previously.

Settings > Colors - Remove your color profile, then try adding "Colorspace: sRGB".

In T9683#183749, @JoshStrobl wrote:

Various fixes for GNOME Shell have been synced via R993:b917bf05685c: Sync with git.. If you use GNOME Shell, I encourage you to update and test.

After installing this update "gnome-shell is upgraded from 40.0-71-1-x86_64 to 40.0-72-1-x86_64 with delta", the background (wallpaper) turned black. Re-setting the wallpaper or switching it to a different one has no effect, it's black still.

Instead of black background i get blue background. Tried to resintall gnome-shell but issue is not resolved. Can't change background from gnome-settings and gnome-tweeks too.

Found that the issue is reported here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4138

I built gjs with this patch and fixed the background issue.

Thanks I'll get ours fixed @algent.

In T9683#183764, @Katoa wrote:

@Phantop I think i have the same issue, had a red/orange tint on the screen after updating, turning Night Light off did not change anything. Found that changing color profile for my screen, brought back the normal colors i was used to. In my 4 years on Solus the color profile have been the same (the name of my monitor), and i have not had this issue previously.

Settings > Colors - Remove your color profile, then try adding "Colorspace: sRGB".

Ah this fixed it! Yeah same, have been using Solus for 4 years and never had this issue before. Thanks for the help.

Looks like the color/ICC display profile issue has been reported, despite the post's headline this affects both AMD & Nvidia users.
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071

The solution for now is to choose another profile than the default.

The boring thing is that when computer resume work after sleep, I have to put two times the password in login window. After entering password first time login window is loaded again, then you have to put the password for the second time.

In T9683#184057, @algent wrote:

The boring thing is that when computer resume work after sleep, I have to put two times the password in login window. After entering password first time login window is loaded again, then you have to put the password for the second time.

Yeah I can report this same issue on Budgie.

@algent and @Phantop, @YakoYakoYokuYoku was able to reproduce it when using Auto Suspend + lock when screen turns off. Unfortunately I have not yet been able to reproduce it. I tried validating on both my laptop (fully AMD) and desktop (AMD CPU + NVIDIA GPU). Could you folks let me know what hardware you're running on?

Found some issues filed in Mutter land related to resume from suspend, but they seem to be mostly related to Wayland and Intel:

• https://gitlab.gnome.org/GNOME/mutter/-/issues/1763
• https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4113
• https://gitlab.alpinelinux.org/alpine/aports/-/issues/12605
• This one happens under Xorg: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4148

After inspecting logs provided by YakoYako, the only thing I noticed was lines like gkr-pam: the password for the login keyring was invalid. , however in those cases the login password may have literally been invalid, and random Source ID ### was not found [...] which is a non-fatal GLib warning. In my case there was an immediate gkr-pam unlock on the keyring, then the usual pam_warn.

In T9683#184120, @JoshStrobl wrote:

@algent and @Phantop, @YakoYakoYokuYoku was able to reproduce it when using Auto Suspend + lock when screen turns off. Unfortunately I have not yet been able to reproduce it. I tried validating on both my laptop (fully AMD) and desktop (AMD CPU + NVIDIA GPU). Could you folks let me know what hardware you're running on?

I'm using an Intel i7 6700 CPU and an XFX AMD RX 570 GPU on an HP 2B47 motherboard (OEM) on a desktop.

Unfortunately I have not yet been able to reproduce it. I tried validating on both my laptop (fully AMD) and desktop (AMD CPU + NVIDIA GPU). Could you folks let me know what hardware you're running on?

https://dev.getsol.us/P16 is my journalctl log since waking from sleep.

Thanks to some additional testing with @serebit and a sneaking suspicion it was related to a gnome-settings-daemon change, I asked @serebit to test if moving sudo mv /usr/share/dbus-1/services/org.gnome.ScreenSaver.ForBudgie.service ~/xyz resolved the issue after a reboot and at least the early report indicated it was.

Before I tag a new release of budgie-screensaver, @Phantop could you be a lovely hooman and try running the command above, rebooting, and seeing if it fixes the issue for you too?

Btw my hardware is:

$ lscpu
 Model name:          AMD Ryzen 7 2700 Eight-Core Processor
$ lspci
 1d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] 
 1d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tobago HDMI Audio [Radeon R7 360 / R9 360 OEM]

sudo mv /usr/share/dbus-1/services/org.gnome.ScreenSaver.ForBudgie.service ~/xyz

@JoshStrobl I run that command and the issue was resolved after reboot.

GNOME Pomodoro tested as i did in Gnome 3.38.

Issues:
Closing the program by clicking the X, will leave it open if you look in System Monitor. Closing it from the drop down menu by choosing quit, will close the program as expected. Cant find any open bug reports regarding this issue.

Not tested:
Plugins

GNOME Maps tested (been using the program under Gnome 3.38)

Issues:
None

Not tested:
Set up OpenStreetMap Account