Announcement

Collapse
No announcement yet.

Preparing For The Release of Wayland 1.0

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

  • Preparing For The Release of Wayland 1.0

    Phoronix: Preparing For The Release of Wayland 1.0

    Listen to Kristian Høgsberg talk about the imminent Wayland 1.0 release, multimedia integration for Wayland/Weston, and other recent Wayland developments...

    http://www.phoronix.com/vr.php?view=MTE4NTA

  • #2
    Ubuntu and Debian does not compile GTK+ with the Wayland backend enabled.

    Ubuntu does not yet have PAM set $XDG_RUNTIME_DIR.

    Weston does not support minimize on windows.

    Weston Terminal does trigger Enter when you press the right Enter button on the numpad.

    Xwayland is not yet merged into the radeonhd and nouveau drivers.

    Ubuntu's thin scrollbars causes application crashes and needs to be disabled (export LIBOVERLAY_SCROLLBAR=0).

    libcanberra-gtk3-module causes crashes and needs to be uninstalled.

    Comment


    • #3
      Hope the proprietary nvidia driver will support wayland in the future.

      Comment


      • #4
        wayland 1.0 + e17 official release = year of the linux desktop!!!!

        I suspect Windows market share will drop by at least 20% on the first week. And after KLANG releases, 100% linux market share!

        Comment


        • #5
          And then canonical will release a new version of unity it will drop to 0%.

          Comment


          • #6
            Originally posted by uid313 View Post
            Ubuntu and Debian does not compile GTK+ with the Wayland backend enabled.

            Ubuntu does not yet have PAM set $XDG_RUNTIME_DIR.

            Ubuntu's thin scrollbars causes application crashes and needs to be disabled (export LIBOVERLAY_SCROLLBAR=0).
            Ubuntu is atleast a year way from showcasing Wayland officially. Debian's probably 4 or 5 years away. So the current lack of GTK+ support / PAM or a crash isnt really that big of a deal. Upstream / Ubuntu will fix as time allows.

            Originally posted by uid313 View Post
            Weston does not support minimize on windows.

            Weston Terminal does trigger Enter when you press the right Enter button on the numpad.
            Weston is only the reference implementation, it is not meant to be THE compositor on production systems so the fact that it currently cant do minimize isnt really that big of a deal. Kwin / Compiz / Mutter will be THE compositor, and THATS where minimize support and all the other stuff matters. Though, Weston supporting minimize should be done just for the sake of completeness.


            Originally posted by uid313 View Post
            Xwayland is not yet merged into the radeonhd and nouveau drivers.
            Technically Radeonhd is a dead project, if youre referring to the open source ATI drivers thats just "radeon." And I was under the impression that XWayland has to be merged into the Xorg server, not the respective drivers.

            Originally posted by uid313 View Post
            libcanberra-gtk3-module causes crashes and needs to be uninstalled.
            Upstream fix as time allows.

            Comment


            • #7
              Originally posted by Ericg View Post
              Ubuntu is atleast a year way from showcasing Wayland officially. Debian's probably 4 or 5 years away. So the current lack of GTK+ support / PAM or a crash isnt really that big of a deal. Upstream / Ubuntu will fix as time allows.



              Weston is only the reference implementation, it is not meant to be THE compositor on production systems so the fact that it currently cant do minimize isnt really that big of a deal. Kwin / Compiz / Mutter will be THE compositor, and THATS where minimize support and all the other stuff matters. Though, Weston supporting minimize should be done just for the sake of completeness.




              Technically Radeonhd is a dead project, if youre referring to the open source ATI drivers thats just "radeon." And I was under the impression that XWayland has to be merged into the Xorg server, not the respective drivers.



              Upstream fix as time allows.
              The Xwayland server needs a ddx driver. The current solution is using a slightly modified X driver, or use the generic software rendering WLSHM driver for xwayland, which is quite underdeveloped

              The future is probably a hardware acclerated driver for xwayland like EGL instead of wlshm
              Last edited by nerdopolis; 09-14-2012, 03:51 PM.

              Comment


              • #8
                http://www.phoronix.com/scan.php?pag...desktops&num=6
                Unity 6.4 with Compiz meanwhile was the slowest in the majority of the benchmark results.
                Wayland will be probably same disaster as Unity.

                Comment


                • #9
                  Originally posted by JS987 View Post
                  http://www.phoronix.com/scan.php?pag...desktops&num=6
                  Wayland will be probably same disaster as Unity.
                  Compiz used by Unity probably slows down OpenGL applications.
                  Wayland is similar to Compiz.
                  Last edited by JS987; 09-16-2012, 02:42 PM.

                  Comment


                  • #10
                    Originally posted by JS987 View Post
                    Compiz used by Unity probably slows down OpenGL applications.
                    Wayland is similar to Compiz.
                    lol if anything then Weston is similar to Compiz (being a compositor as an example implementation of the Wayland Protocol). The fact that you can't even make this distinction leads me to belive, that you don't know much about the whole issue.

                    Comment


                    • #11
                      Originally posted by blackout23 View Post
                      lol if anything then Weston is similar to Compiz (being a compositor as an example implementation of the Wayland Protocol). The fact that you can't even make this distinction leads me to belive, that you don't know much about the whole issue.
                      It doesn't matter how compositor is named.

                      Comment


                      • #12
                        It isn't a matter of names, the things that you posted were meaningless...

                        Comment


                        • #13
                          Originally posted by JS987 View Post
                          It doesn't matter how compositor is named.
                          Care to explain why compositing in general is a bad thing and why it should be inherently slow?

                          Comment


                          • #14
                            Originally posted by blackout23 View Post
                            Care to explain why compositing in general is a bad thing and why it should be inherently slow?
                            According to most benchmarks at Phoronix compositing slows down OpenGL applications.

                            Comment


                            • #15
                              Originally posted by JS987 View Post
                              According to most benchmarks at Phoronix compositing slows down OpenGL applications.
                              Hint: XFCE, KDE and GNOME3 also use compositing and are still faster than Unity. You should read a little bit more not just look at some graphs.

                              Comment

                              Working...
                              X