brent Gonna take a look at the issue of not remembering settings.

To your theme question: The Dark theme toggle only works in some places, like the Budgie menu and inside Budgie Desktop Setting itself (I'd have to do some research to find all instances where it applies; that's what I meant with "some apps" in the other thread). Since Materia (without the -Dark) is a light theme, everything else will be bright. Using Materia-Dark should be dark everywhere, including Budgie Desktop Settings and the Budgie menu, even if you don't toggle the Dark theme switch. Theoretically Materia-Dark should also cause libadwaita apps like Files and gnome-calculator to switch to the dark theme, because it's named with the -Dark suffix, and libadwaita has some logic integrated to detect and respect that.

      Yesterday, gnome-control-center was okay, but not today on Budgie.

      pat@solus ~ $ gnome-control-center

(gnome-control-center:4336): GLib-GIO-ERROR **: 06:06:21.396: Settings schema 'org.gnome.shell.app-switcher' is not installed
Trappe pour point d'arrêt et de trace (core dumped)
pat@solus ~ $

      Cloak
      Yes, for me too, need to clic inside the field first then delete all name and rename, if I delete the selected name first it crashes.

        When I opened two nautilus windows and copied data from one to the other it locked me out of doing anything else until the process was finished. i.e. I couldn't click anything. Happened every time I copied something after the update.

          riffer lately I've been right-click/move to/copy to old school way of moving stuff. Was wondering if the lockout exists under that method as well. It might rule something out.

            Cloak I can't reproduce this either. Can you or someone else give more exact steps?

                EbonJaeger cannot reproduce either. I renamed three desktop folders while in nautilus.

                  I have an issue in GNOME in that the Night Light function doesn't work. It's nothing to do with the graphics driver or remote desktop as the issue is present on my main AMD Ryzen 7 4800h machine my Lenovo X240 Thinkpad.

                    Staudey you are right, *-dark pretty much did all the work. went ahead and disabled Dark Theme toggle. No visible differences either. Went ahead and disabled Built In Theme too. The only difference---that I could see---with the enigmatic Built In Theme button being on or off is my task bar being opaque or solid---and bold font.
                    Check this out from my top task bar---
                    Built in theme disabled:

                    Built in theme enabled:

                    cra-cra yes?

                      Hi y'all,
                      not sure if this applies to the same GNOME stack problems, I'll mention it just in case:

                      I would click the ON/OFF button in the tray, select SHUTDOWN and would then be able to select the SHUTDOWN button in the middle of the screen by hitting the TAB key, then hit ENTER to shutdown.

                      That selection using the TAB key doesn't work anymore since the latest update.
                      Thanks for all your help!

                        SOLUSfiddler Can't reproduce this unfortunately. You're using Solus Budgie, right? Possibly a visual glitch? I can see the tab selection, but just barely. Have you tried if it works (even if the visual hint is not there)? (i.e. simply pressing TAB and Enter when the window pops up)

                        markdj I can reproduce this issue, adding to the list. [edit: Found a fix, patched in the unstable repo]

                        Cloak Unfortunately I also can't reproduce this. Added it to the list because other's have confirmed it.

                                Staudey
                                Strangely I have to say that just now I was able to use the TAB key and select SHUTDOWN!
                                But earlier tonight I had not been able to use TAB to select SHUTDOWN, not even "blind". There hadn't been any reaction and no "selected" frame around the SHUTDOWN button was visible either.

                                  In addition to several of the issues above, I have found that the text in the main area of Nautilus (not the Left Panel) is slightly blurry since the update. Also, they have given each item (file or folder) a huge tile, so that multiselecting by clicking and dragging a mouse is difficult. You are far more likely to hit the invisible tile around an item than the small invisible space left between tiles.

                                  This kind of thing makes me question not only the Gnome team's direction, but their competence. And the Solus team is left trying to make something good out of something not good, yet again.

                                    With the update, I could not take screenshots of an area and put them into the clipboard. Neither using shotcuts
                                    Ctrl + Shift + Prnt nor from terminal gnome-screenshot -ac

                                      minh Can confirm that issue. Oddly enough it works (from the command line) while the graphical app is open. There is a merge request which kinda fixes the issue, but in a weird way, and it comes with some additional problems.
                                      Unfortunately gnome-screenshot is no longer a core GNOME app, and thus receives less support (see e.g. here)

                                      Teggs Yes, that's something I've noticed too, but unfortunately I think once again an intended change by upstream (gotta google the corresponding issue tickets or changeset later)

                                      • minh replied to this.

                                            Staudey Can confirm that issue. Oddly enough it works (from the command line) while the graphical app is open

                                            Thanks for looing into this @Staudey, and your trick did the job. After trying several times, it (the terminal command) works now even without the GUI open, this is really weird. What I did in the meantime is install and uninstall flameshot and budgie-screenshot-applet. So now I'm not sure what fixed the issue. I have one question (not related to the issue directly), it doesn't work when I set up a custom shortcut like "gnome-screenshot -ac", but it works with just "gnome-screenshot". Any idea?