Announcement

Collapse
No announcement yet.

GNOME 3.30 Ready For Release Today With Many New Features & Improvements

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • GNOME 3.30 Ready For Release Today With Many New Features & Improvements

    Phoronix: GNOME 3.30 Ready For Release Today With Many New Features & Improvements

    GNOME 3.30 is releasing today as the newest feature release for this open-source desktop environment on its usual six-month release cadence...

    http://www.phoronix.com/scan.php?pag...-3.30-Features

  • #2
    Performance enhancements.. looking forward to when Shell catches up to Unity for smooth performance. Putting CLUTTER_DEFAULT_FPS=144 in /etc/environment works somewhat (my monitor's native mode is 2560x1440 @ 144Hz), but it's still fairly choppy when dragging windows (maybe a vsync issue, not sure). It's really the only thing that stops me from using Shell over Unity. Unity is smooth, Shell isn't. Bug report for Ubuntu here: https://bugs.launchpad.net/ubuntu/+s...r/+bug/1763892

    Comment


    • #3
      I wonder if Wayland will FINALLY work properly on Nvidia. It seems like the release notes imply with every GNOME release that Wayland is ready.

      Comment


      • #4
        Originally posted by lem79 View Post
        Performance enhancements.. looking forward to when Shell catches up to Unity for smooth performance. Putting CLUTTER_DEFAULT_FPS=144 in /etc/environment works somewhat (my monitor's native mode is 2560x1440 @ 144Hz), but it's still fairly choppy when dragging windows (maybe a vsync issue, not sure). It's really the only thing that stops me from using Shell over Unity. Unity is smooth, Shell isn't. Bug report for Ubuntu here: https://bugs.launchpad.net/ubuntu/+s...r/+bug/1763892
        I doubt that Gnome Shell's problems will be fixed conclusively until at least Gnome 4. Until then, the current design where all extensions run in the same thread as the GUI make such issues basically unsolvable.

        Comment


        • #5
          Originally posted by jacob View Post
          I doubt that Gnome Shell's problems will be fixed conclusively until at least Gnome 4. Until then, the current design where all extensions run in the same thread as the GUI make such issues basically unsolvable.
          It's a bit of a shame. But I'm happy I've got a very functional Unity desktop on 18.04, which in theory can last me several years, maybe long enough for more GNOME developers to have high refresh displays..

          Comment


          • #6
            Originally posted by jacob View Post

            I doubt that Gnome Shell's problems will be fixed conclusively until at least Gnome 4. Until then, the current design where all extensions run in the same thread as the GUI make such issues basically unsolvable.
            So no gaming under Wayland at the moment ?
            https://bugzilla.gnome.org/show_bug.cgi?id=745032

            Comment


            • #7
              Originally posted by jacob View Post
              I doubt that Gnome Shell's problems will be fixed conclusively until at least Gnome 4. Until then, the current design where all extensions run in the same thread as the GUI make such issues basically unsolvable.
              Merge requests for your "unsolvable problems" are (among others):

              https://gitlab.gnome.org/GNOME/mutte...e_requests/168
              https://gitlab.gnome.org/GNOME/mutte...e_requests/171

              Comment


              • #8
                All I see is MIR .. lol (as in Canonical's display server.. the irony of seeing that in this context)

                Good to see the performance focus though.

                Comment


                • #9
                  Originally posted by lem79 View Post
                  All I see is MIR .. lol (as in Canonical's display server.. the irony of seeing that in this context)
                  Additional to that: Daniel works at Canonical But I think these merge requests (even the merged ones) are an interesting read. All the troubles that a compositor has to go through. For example that Windows displays a software cursor and hides the hardware cursor when you move a window so that mouse and window movement are the same. Due to the unlocked nature of this MR this problem came up and you maybe need an additional "fix" on top of that.

                  Comment


                  • #10
                    Originally posted by -MacNuke- View Post
                    Colour me naïve, but I'm surprised at how much easier the move to GitLab has made understanding and appreciating the engineering mindset behind the ongoing efforts to improve GNOME (and GNOME Shell in particular).

                    It seems to me that the move to GitLab has been quite the win for everyone who's interested in GNOME, given how easy it is to track e.g. merge requests like you did and have them be presented within a decent looking Web UI.

                    Comment

                    Working...
                    X