Announcement

Collapse
No announcement yet.

Whoops, There's A Big Problem For Wayland GTK+

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

  • Whoops, There's A Big Problem For Wayland GTK+

    Phoronix: Whoops, There's A Big Problem For Wayland GTK+

    It turns out there's a rather serious issue for some systems when having Wayland support within GTK+ exposed, which may hinder the Wayland GTK+ availability in the near-term...

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

  • #2
    I'm not sure this is a "big problem". It seems closer to the usual growing pains of any project that tries to strike out in a new direction. Wayland does something that Nvidia didn't expect, so the driver doesn't cope with it very well. Boo fucking hoo; try running fglrx ~10 years ago (or running gnome-shell with it ~10 months ago, for that matter).

    Comment


    • #3
      Maybe it could be Wayland be needing input from nVidia and AMD so that they can make adjustments in their binary drivers and make suggestions to the developers as well. Making Wayland work with all drivers, FOSS and binary should be key and all the players involves should be working towards that goal.

      Comment


      • #4
        NVidia has officially stated that they have no current plans to support Wayland.

        Comment


        • #5
          It doesn't sound like this has anything to do with Wayland

          It's Cairo and the way GTK is using it that's the problem. It just so happens that Wayland requires that to be used, but nothing about Wayland in particular is actually causing this.

          Comment


          • #6
            The nv blob has always sucked for cairo and some gtk.

            Comment


            • #7
              Perhaps the title should be rephrased. I use Intel graphics hardware since it's had pretty good support and performance after 2006. I almost thought I had to be worried.

              Maybe when NVIDIA makes their driver compatible with Wayland, they'll see this issue and fix it as well. If they don't, we may simply maintain X11 versions of everything until the situation changes, and allow users with other hardware to use Wayland and cairo-gl. I'm not sure if this problem is going to make maintenance much more difficult, and it seems there are some fairly straightforward solutions.

              I think that, once distros start shipping with Wayland support, NVIDIA may change their positon. Their original response about not providing Wayland support could have had similar motivations as other projects that haven't totally embraced it. It's simply not ready- why should any company consider supporting something so long before it's going to be used? Even now it would seem a bit premature.

              Comment


              • #8
                I don't see how this is a problem for Wayland gtk+. It's problem for buggy nvidia blob. I hope nobody will wait for nvidia to support Wayland. It will be another reason to use AMD (if Catalyst won't have any problems).

                Comment


                • #9
                  Originally posted by RealNC View Post
                  NVidia has officially stated that they have no current plans to support Wayland.
                  And how old is this statement? One or two years?

                  Comment


                  • #10
                    they will probably support it once it gets more traction

                    and if i understood the whole thing right it will be relatively easy for them


                    as for the GTK problem it is expected to stumble upon stuff like that since there are more people playing around with wayland

                    Comment


                    • #11
                      Originally posted by Nille View Post
                      And how old is this statement? One or two years?
                      Somewhere around that. If Wayland ends up being adopted as the new standard for Linux, then I'm not sure what will happen to the binary drivers. Doesn't Wayland require DRI2 and/or Gallium3D? If yes, Catalyst also doesn't support it.

                      Comment


                      • #12
                        Originally posted by RealNC View Post
                        Doesn't Wayland require DRI2 and/or Gallium3D? If yes, Catalyst also doesn't support it.
                        My last information is that wayland need only egl and something similar to KMS.

                        Comment


                        • #13
                          Originally posted by RealNC View Post
                          Somewhere around that. If Wayland ends up being adopted as the new standard for Linux, then I'm not sure what will happen to the binary drivers. Doesn't Wayland require DRI2 and/or Gallium3D? If yes, Catalyst also doesn't support it.
                          AFAIK Gallium isn't a requirement, KMS and EGL however are. This means Wayland is a big no-no on binary blobs. KMS won't be easy for nvidia to implement in their binary blob (anyone remember the mess when OSS drivers became KMS enabled?). Another hard requirement for Wayland is EGL support, which I don't know if the binary blobs support. AMD has the upper hand here with their OSS driver.
                          Originally posted by 85c51 View Post
                          they will probably support it once it gets more traction
                          That is vey wishful thinking. Both companies have repeatedly said that their binary blobs target mainly Workstations. Wayland is meant for desktops/embedded. If OSS drivers die, so does the Linux desktop.

                          Comment


                          • #14
                            That's a problem?

                            Does that mean that gtk 3.4 will actually compile against wayland git libraries? And does that mean that cairo gl actually works with wayland now?

                            Comment


                            • #15
                              Right now wayland + weston with mesa git and stable cairo without gl and egl is very broken. Wayland-terminal crashes after inputting some characters or selecting something with the mouse, weston will crash after about 2 minutes of usage..

                              Comment

                              Working...
                              X