Page 1 of 6 123 ... LastLast
Results 1 to 10 of 54

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

  1. #1
    Join Date
    Jan 2007
    Posts
    13,405

    Default 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. #2
    Join Date
    Jan 2008
    Posts
    772

    Default

    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).

  3. #3
    Join Date
    Sep 2007
    Location
    Connecticut,USA
    Posts
    941

    Default

    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.

  4. #4
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,762

    Default

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

  5. #5
    Join Date
    Oct 2008
    Posts
    2,907

    Default 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.

  6. #6
    Join Date
    Oct 2009
    Location
    .ca
    Posts
    392

    Default

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

  7. #7
    Join Date
    Feb 2012
    Posts
    168

    Default

    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.

  8. #8

    Default

    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).

  9. #9
    Join Date
    Jul 2008
    Location
    Germany
    Posts
    558

    Default

    Quote 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?

  10. #10
    Join Date
    Jan 2009
    Posts
    1,518

    Default

    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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •