Announcement

Collapse
No announcement yet.

X.Org Server 1.20.8 Released With No Sign Of GLAMOR/XWayland-Improved X.Org Server 1.21

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

  • X.Org Server 1.20.8 Released With No Sign Of GLAMOR/XWayland-Improved X.Org Server 1.21

    Phoronix: X.Org Server 1.20.8 Released With No Sign Of GLAMOR/XWayland-Improved X.Org Server 1.21

    X.Org Server 1.20.8 was released as the newest point release for this current stable branch. X.Org Server 1.20.8 brings a number of fixes with there still being no sign of X.Org Server 1.21 gearing up for release...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    I wonder why noone has forked it.

    Comment


    • #3
      1.21 more than likely will not happen micheal, xserver is in maintenance release only

      Comment


      • #4
        you'll see 1.20.9 an 1.20.10 an 1.20.11 an so on, its all Wayland an Mir now

        Comment


        • #5
          Originally posted by Anvil View Post
          1.21 more than likely will not happen micheal, xserver is in maintenance release only
          Only for Red Hat, but Red Hat is not everyone.

          Comment


          • #6
            Originally posted by frank007 View Post

            Only for Red Hat, but Red Hat is not everyone.
            Then some other people need to come and maintain it then.

            Comment


            • #7
              Originally posted by middy
              display servers are hard. look at wayland, almost 11 years and hasn't replaced xorg yet. and wayland has a lot of development behind it. along with millions poured into it by companies like red hat. if you're going to fork you need a massive movement to follow. like when xfree86 got forked to xorg. nearly all the development team behind xfree went to xorg. there's just no reason to fork xorg atm. especially when a sizable chunk of the community has a hate hard-on for xorg.
              Wayland is just a protocol fyi.

              and Wayland-compatible display servers largely has replaced Xorg, Debian, RHEL, Fedora, SUSE all default to Wayland on GNOME. The amount that's required to implement an X Server is much greater than a Wayland compositor. X you have to maintain decades of crappy protocols and drawing APIs.

              Comment


              • #8
                Originally posted by pieman
                well that's because newer versions of gnome defaults to wayland on anything that has KMS enabled. even with nvidia if the user enables nvidia KMS via kernel line with "nvidia-drm.modeset=1". wayland by default is a gnome thing as gnome is on the wayland bandwagon. yes, some distros prior to gnome defaulting to wayland like fedora adopted wayland by default, to manually start xorg session gnome you have to do something like the following:

                anyways that doesn't invalidate anything i wrote as the fact of the matter wayland ANYTHING has yet to replace xorg. fully. and if you're a nvidia user, its going to be a very long time. and there are a whole bunch of nvidia users on linux. just like a whole bunch of AMD / Intel users not using wayland as well.
                GDM ships with a udev rule that disables Wayland if the proprietary driver is detected regardless if you enable Nvidia KMS or not. You can find this in /usr/lib/udev/rules.d/61-gdm.rules

                There's not a lot that can be done to help Nvidia users (I myself am one), Nvidia unfortunately prevent anything being done there.

                Comment


                • #9
                  Originally posted by 144Hz View Post
                  There’s no need for 1.21.0

                  Xwayland fixes can go into 1.20.x
                  Fixes yes, but not new features. There are a few nice things in 1.21 that won't be backported, e.g. better flicker free (https://gitlab.freedesktop.org/xorg/...e_requests/316). And yet to be done is fractional scaling support in Xwayland (https://gitlab.freedesktop.org/xorg/...e_requests/111).

                  Comment


                  • #10
                    People will never understand simple things like "Wayland is just a protocol", even 10+ years after its introduction. LOL.

                    Seriously though, Xorg compositors and Wayland compositors aren't really that much different. All the Wayland protocol does is removing the middleman, Xorg, between KMS and the Compositor. The main reason it took so much time was because people kept clinging on their X. But after the aggressive push of Wayland it has become much better these last years.

                    Still, how hard it would be for someone from the Xorg team to just show up and organize a 1.21 Xserver release? I mean, it is not rocket science, the code is already there, just declare a code freeze date and an RC program. I mean there are still people in the Xorg team, right? After all, who is doing the point releases? Just do a biggie to bring us the rest of the features for 2nd half of 2020 distros. Anyone?

                    Comment

                    Working...
                    X