GNOME Mutter 46.2 Rolls Out To Ubuntu 24.04 Users, Experimental VRR Remains Rough

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • bearoso
    Senior Member
    • Jul 2016
    • 180

    #31
    This is pathetic. Handling the display output and all it's caveats is a very technical and challenging process, and it's difficult to get right. Having each and every compositor platform implement its own display code has been a disaster.

    Come on, guys. Collaborate and create an official compositor backend library that gets everything working. At this point all we have is a mish-mash of supported and broken features, and nobody has a complete product despite Wayland existing for 15 years.

    Comment

    • bkdwt
      Phoronix Member
      • May 2024
      • 78

      #32
      Originally posted by bearoso View Post
      This is pathetic. Handling the display output and all it's caveats is a very technical and challenging process, and it's difficult to get right. Having each and every compositor platform implement its own display code has been a disaster.

      Come on, guys. Collaborate and create an official compositor backend library that gets everything working. At this point all we have is a mish-mash of supported and broken features, and nobody has a complete product despite Wayland existing for 15 years.
      Welcome to Open-Source world!

      Comment

      • QwertyChouskie
        Senior Member
        • Nov 2017
        • 636

        #33
        Originally posted by bearoso View Post
        This is pathetic. Handling the display output and all it's caveats is a very technical and challenging process, and it's difficult to get right. Having each and every compositor platform implement its own display code has been a disaster.

        Come on, guys. Collaborate and create an official compositor backend library that gets everything working. At this point all we have is a mish-mash of supported and broken features, and nobody has a complete product despite Wayland existing for 15 years.
        wlroots exists, and that's what basically everything that's not Gnome or KDE or Cosmic uses. Nobody can force Gnome or KDE or Cosmic to switch to wlroots, nor would you probably want to (the Dev effort would be way higher than any benefit at this point).

        Comment

        • bkdwt
          Phoronix Member
          • May 2024
          • 78

          #34
          Still not in repos.

          Comment

          • Sonadow
            Senior Member
            • Jun 2009
            • 2261

            #35
            Originally posted by Shadywack View Post

            Ironic too considering each release breaks the majority of extensions people come to depend on, causing either the distro and/or extension maintainer to have to rebase every release. Stability in software often considers backwards compatibility, which Gnome is terrible at historically. Suse still prioritizes Plasma too, and I don't see YaST moving to the insanity of gtk4 anytime soon.
            So why are you on Linux?

            Every version of glibc introduces breakages where software built against a newer glibc cannot be used on an older glibc.
            Qt6 cannot run Qt5 stuff.
            GTK4 cannot run GTK3 stuff.
            The Linux kernel breaks ABI every single fucking release. Modules built on one kernel release cannot be used on another kernel release.

            Comment

            • SpyroRyder
              Senior Member
              • Feb 2014
              • 390

              #36
              Originally posted by Daktyl198 View Post

              Not sure why people still believe that Canonical is somehow antithetical to FOSS. They routinely create FOSS solutions to problems and invite other developers and distros to help make their solution better.

              Not their fault that Red Hat tends to come around a year later, make something basically the same but market it better and get more support. To Canonical's credit, they then drop their own software and follow the "industry standard". Snap is the one place they haven't done that, and it's because flatpaks don't have everything that Canonical's enterprise users want.
              Thats some rose glasses looking at some of their controversies. Its true for Upstart but thats about it. AppArmour technically came before SELinux but Ubuntu didnt use it til 2007, long after both had been around and several years after Fedora had included SELinux. Their MIR wayland competitor was annouced just as Wayland had been spec finalised and planning was going to its implementation. Unity8 and their mobile dreams were built on MIR so its no wonder they didnt take off or see outside contributers.

              Snap and Flatpak you are right about though, theyre from about the same time and have a lot of differences. That said Flatpaks success over snaps in the eyes of the greater distro community is because it only takes care of apps so is a bit more flexible for the distros to manage. Having snaps means having the all encompasing snap store, of which you can only have ome configured at a time. Flatpak is more flexible for the distros using it

              Comment

              • hf_139
                Senior Member
                • May 2023
                • 316

                #37
                Originally posted by You- View Post

                I like how you are reality have never met. it does however lead to poor quality trolling.

                How many enterprise stability distributions offer a default desktop other than gnome?

                RHEL? Gnome
                Ubuntu LTS? Gnome
                Debian? Gnome
                SUSE? Gnome.

                Even historically non-gnome places like SUSE have Gnome as their desktop for their enterprise offering.
                And what did those enterprise distributions get for it?
                One of the worst RCE exploits, that was there for over a decade and only god knows how much it got abused.

                CVE-2023-43641 is a vulnerability in libcue, which can lead to code execution by downloading a file on GNOME.


                If you use GNOME in any security relevant setup after this, you can not be helped. And thank god those enterprise distributions are mostly installed on servers with no desktop environment at all.

                Comment

                • Hibbelharry
                  Senior Member
                  • Jun 2009
                  • 623

                  #38
                  Originally posted by hf_139 View Post
                  If you use GNOME in any security relevant setup after this, you can not be helped. And thank god those enterprise distributions are mostly installed on servers with no desktop environment at all.
                  Sorry, but your comment is deprecated so shouldn't be answered or considered. People, please go on.

                  Comment

                  • spicfoo
                    Senior Member
                    • Nov 2023
                    • 695

                    #39
                    Originally posted by hf_139 View Post

                    And what did those enterprise distributions get for it?
                    One of the worst RCE exploits, that was there for over a decade and only god knows how much it got abused.
                    If RCE exploits were a problem for you, you wouldn't be running Linux either since it had many more than any desktop environment did and unlike you, we do know several including https://nvd.nist.gov/vuln/detail/CVE-2022-47939 actively being exploited.

                    Comment

                    • MrCooper
                      Senior Member
                      • Aug 2008
                      • 620

                      #40
                      Originally posted by Eberhardt View Post
                      The only potential drama is that GNOME added explicit sync support in 46.1, which seems to be totally stable though.
                      And Ubuntu apparently patch that out anyway, which means nvidia users still get the same old glitches.

                      Comment

                      Working...
                      X