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?

              @Staudey Are we still going to have any need for this Hack after this weekend update?
              if there is one ... 😅

                unclemez I assume you're talking about either the dark theme toggle or Gradience hacks. In both cases, yes, unfortunately this will stay with us for the foreseeable future.

                  brent So a big MR fixing the functionality and performance of the Nautilus/Files List View was merged today, which also should take care of your issue of it not remembering sorting preferences [Issue no. 12 in my list]. Gonna push it to the unstable repository now.

                    10/21 update / 108 packages.
                    Staudey! Memory fixed in Nautilus. Thank you. It opened the way I left it.

                    New problem is I drag a file from Desktop to Videos. for example. and it doesn't crash like a lot of users had, it just puts me in videos folder even though I did not navigate there...

                    Lastly is this is a gnome issue?

                    korla used to be dots even for the app being used. where did this blunt ugly dash come from? If not gnome/thread-relevant please disregard.

                    all else appears fine including browsers and other apps. thanks nautilus squad!

                      I transferred my topic here, about nautilus being slow to start. From the terminal with journalctl -f I have this:

                      pat@solus ~ $ sudo journalctl -f
Mot de passe : 
oct. 23 06:31:27 solus rtkit-daemon[1137]: Supervising 3 threads of 3 processes of 1 users.
oct. 23 06:31:31 solus budgie-panel[1259]: budgie_abomination_app_group_get_windows: assertion 'self != NULL' failed
oct. 23 06:31:31 solus firefox.desktop[2088]: Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
oct. 23 06:31:33 solus dbus-daemon[1050]: [session uid=1000 pid=1050] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.86' (uid=1000 pid=4224 comm="gnome-terminal " label="unconfined")
oct. 23 06:31:33 solus systemd[1033]: Starting GNOME Terminal Server...
oct. 23 06:31:33 solus dbus-daemon[1050]: [session uid=1000 pid=1050] Successfully activated service 'org.gnome.Terminal'
oct. 23 06:31:33 solus systemd[1033]: Started GNOME Terminal Server.
oct. 23 06:31:34 solus systemd[1033]: Started VTE child process 4252 launched by gnome-terminal-server process 4231.
oct. 23 06:31:45 solus sudo[4269]:      pat : TTY=pts/0 ; PWD=/home/pat ; USER=root ; COMMAND=/usr/bin/journalctl -f
oct. 23 06:31:45 solus sudo[4269]: pam_unix(sudo:session): session opened for user root by (uid=1000)
oct. 23 06:31:51 solus dbus-daemon[1050]: [session uid=1000 pid=1050] Activating service name='org.gnome.Nautilus' requested by ':1.38' (uid=1000 pid=1259 comm="budgie-panel " label="unconfined")
oct. 23 06:31:51 solus dbus-daemon[4274]: writing oom_score_adj error: Permission denied
oct. 23 06:31:52 solus dbus-daemon[1050]: [session uid=1000 pid=1050] Successfully activated service 'org.gnome.Nautilus'
oct. 23 06:31:55 solus dbus-daemon[1050]: [session uid=1000 pid=1050] Activating service name='org.gnome.DiskUtility' requested by ':1.89' (uid=1000 pid=4274 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
oct. 23 06:31:55 solus budgie-wm.desktop[1249]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200004
oct. 23 06:31:55 solus dbus-daemon[4307]: writing oom_score_adj error: Permission denied
oct. 23 06:31:55 solus dbus-daemon[1050]: [session uid=1000 pid=1050] Successfully activated service 'org.gnome.DiskUtility'
oct. 23 06:31:56 solus dbus-daemon[571]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.104' (uid=1000 pid=4274 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")

                      With last 21 october update, dark materia gtk theme and just after a fresh laptop boot.

                        sangheeta I don't know how to read any of that. My nautilus still a little sluggish with spinning ball, but my terminal output is clean:
                        $ nautilus
                        ---wonder what yours looks like?

                            brent @Staudey --I retract my post of ^ 3 days ago. Memory of file order in Nautilus has regressed, for me, to none. No settings preserved. It was a nice 72 hours while I had it.

                                brent I'm currently looking through some new nautilus fixes. There's a patch in there that deals with additional problems regarding the sorting in list view, so might just be a solution.

                                  Staudey The other possible solution using dconf-editor is described here: https://discuss.getsol.us/d/8463-fix-for-dark-themes-with-blaring-white-applications

                                  DISCLAIMER: I haven't been active on this forum for some time or read all of the responses in this post.

                                  Since one of my posts was mentioned as a solution for theming issues I wanted to point out that I just wrote another reply in the same post explaining how to install flatpak apps that follow theming directives properly so users have the option of using Dolphin temporarily while fixes to existing are worked on.

                                  This solution will work for Dolphin AND ANY OTHER FLATPAK APP INSTALLED so it can offer a solution for using Dolphin temporarily in lieu or Nautilus OR any Gnome/Budgie/GTK app available on flatpak that might be giving people issues when installed from the repo.

                                  Thank you to everyone who have taken on the herculean task of fixing a widespread issue like this and I very much hope this can be a potential solution for some of the problems people are facing.

                                    infinitymdm Following up again on the Nautilus crash when renaming files:

                                    Just happened to me after rebooting my system. Here is the sequence of events, as best I can recall.

                                    • Launched Nautilus
                                    • Used popover menu to show hidden files
                                    • Navigated to ~/.config/gtk-4.0
                                    • Right clicked on gtk.css, and clicked rename
                                    • Pressed right arrow key
                                      Expected: Cursor moves to the end of the text entry box so I can tack a ".old" onto my file.
                                      Actual result: Nautilus immediately crashed.

                                        infinitymdm Here is the sequence of events, as best I can recall.

                                        Launched Nautilus
                                        Used popover menu to show hidden files
                                        Navigated to ~/.config/gtk-4.0
                                        Right clicked on gtk.css, and clicked rename
                                        Pressed right arrow key

                                        Expected: Cursor moves to the end of the text entry box so I can tack a ".old" onto my file.
                                        Actual result: Nautilus immediately crashed.

                                        Just repeated this procedure a few times. Nautilus crashed 6 out of 10 times. Still far too small of a sample size to be meaningful, but I'm not going to test like that all day, so...

                                        Anyways, the crashes spit out this pango error:

                                        (org.gnome.Nautilus:5916): Pango-CRITICAL **: 19:40:30.418: _pango_layout_get_iter: assertion 'PANGO_IS_LAYOUT (layout)' failed
Segmentation fault (core dumped)

                                        I suppose that means I can conclusively say this is related to Pango. I'd probably better go report it, or at least follow up on that other issue I linked earlier.

                                        One final note: selecting the file (with a left click) prior to right click > rename seems to prevent the crash. So I guess the workaround for now is to make sure you select your files before right clicking to rename them.

                                          I can reproduce the renaming crash 100% now with @infinitymdm's method. It doesn't work when nautilus is already open (even in the background), but after a killall nautilus starting it, selecting a file, rename, press right arrow, always crashes for me. I tried to get some kind of trace with gdb, but then my whole system froze, several times. Will try again later.