Announcement

Collapse
No announcement yet.

Ubuntu 24.10 Now Available With Linux 6.11, GCC 14 & Other Upgrades

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

  • #21
    Originally posted by MrCooper View Post



    The linux-drm-syncobj-v1 Wayland protocol support landed in mutter 46.1, not 46.2.

    It's a well-known fact that mutter had been branching only after the .1 release (at least since 3.2 in 2011), and that it was thus possible in principle for new features to land in .1. Canonical must have been aware of this, or it raises questions about why they weren't.

    That said, mutter has already branched after the 47.0 release, so 47.1 won't have any new features.


    I believe Malsabku's point was that the linux-drm-syncobj-v1 Wayland protocol support is patched out of those packages, which means nvidia driver users still get to enjoy all the glitches.

    In summary, this was a tempest in a teapot.
    47 is completely out of context since we are talking about 24.04LTS which was released before 47 was a thing and since 24.04 is stable it cannot change from 46 to 47.

    Comment


    • #22
      After several years of seamless updates, this time I had two problems:
      1. Docker failed to start because containerd config now requires full URL plugin names
      2. Flatpak startup is very very slow from the UI (many minutes): https://github.com/flatpak/flatpak/issues/5968

      Comment


      • #23
        Well at least it did not force install snap and remove my deb packages this time. I'm beginning to think that only LTS releases do that.

        Comment


        • #24
          Originally posted by F.Ultra View Post

          That it was on the road-map doesn't change anything, GNOME moved away from how point releases was before.
          x.1 releases had new features before as well. This is just another example of Ubuntu getting stuck on old kernels and protocols. They are aware and actually changed policy. They are probably also going to revert the SRU decision as well.

          Comment


          • #25
            Originally posted by MrCooper View Post
            Canonical must have been aware of this, or it raises questions about why they weren't.
            Canonical mutter developers were definitely aware. Probably even happy about it.

            The policy change came from the x team. Specifically from Chris Halse Rogers (Mir author). Apparently he is not over Mir yet.

            Comment

            Working...
            X