Page 1 of 13 12311 ... LastLast
Results 1 to 10 of 190

Thread: More Details On The OpenGL Situation In KDE's KWin

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    14,770

    Default More Details On The OpenGL Situation In KDE's KWin

    Phoronix: More Details On The OpenGL Situation In KDE's KWin

    A week ago we reported on the open-source GPU drivers causing headaches for KDE users when attempting to use the KWin compositing manager under certain conditions. Version 4.5 of the KDE Software Compilation has a few improvements to KWin and while the compositing manager does check for optional OpenGL extensions, the open-source Mesa drivers don't always do things right and it's resulted in some bugs and other issues inflicting KDE users...

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

  2. #2
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,790

    Default

    His hardware is supported by Mesa (and very well so), but when he's too lazy to install the drivers and relies on what is shipped by his outdated distro (or choose another distro), well, that's not a good thing for a developer, to put it kindly.

  3. #3
    Join Date
    Dec 2008
    Posts
    987

    Default

    Well, apparently he's an unpaid volunteer doing all this in his free time. So if he just wants to develop for the Nvidia blob, then that's his right. IMO the failure here is with KDE for relying on him to provide such an essential part of the desktop.

  4. #4
    Join Date
    Aug 2009
    Posts
    125

    Default

    Quote Originally Posted by RealNC View Post
    His hardware is supported by Mesa (and very well so), but when he's too lazy to install the drivers and relies on what is shipped by his outdated distro (or choose another distro), well, that's not a good thing for a developer, to put it kindly.
    That's a pretty lame excuse. Xorg/Mesa drivers are the broken components, not KWin. That's a fact.
    Those paid full-time Xorg/Mesa programmers should get off their lazy asses and fix their god damn drivers.

  5. #5
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,790

    Default

    Quote Originally Posted by KAMiKAZOW View Post
    That's a pretty lame excuse. Xorg/Mesa drivers are the broken components, not KWin. That's a fact.
    Those paid full-time Xorg/Mesa programmers should get off their lazy asses and fix their god damn drivers.
    And what does this have to do with a KWin dev not wanting to test his code against the open drivers, allowing him to file bug reports to X.Org? Which is entirely up to him, I'll give you that, but why make excuses about an imaginary inability to do so?

  6. #6
    Join Date
    Aug 2009
    Posts
    125

    Thumbs down

    Quote Originally Posted by RealNC View Post
    And what does this have to do with a KWin dev not wanting to test his code against the open drivers, allowing him to file bug reports to X.Org? Which is entirely up to him, I'll give you that, but why make excuses about an imaginary inability to do so?
    He is a volunteer. If his favorite distro is configured in a way that Mesa drivers don't work with his GPU, that's not his fault.
    Volunteer developers don't owe you or anyone else anything! He is not obligated to run a gazillion distributions with trunk builds of Xorg and Mesa.
    No! It's the paid Xorg/Mesa developers duty to test their drivers with with the most common composite window managers (currently Compiz and KWin, in the future Mutter as well). The current messy situation wouldn't have happened if the well paid developers did their job in the first place.
    And in case there are too few paid Xorg/Mesa developers, maybe some Linux distributors should put some money where it actually counts instead of spending it on a design team that makes purple backgrounds and moves window buttons to the left side....

  7. #7
    Join Date
    Jul 2008
    Location
    Greece
    Posts
    3,790

    Default

    Quote Originally Posted by KAMiKAZOW View Post
    He is a volunteer. If his favorite distro is configured in a way that Mesa drivers don't work with his GPU, that's not his fault.
    Volunteer developers don't owe you or anyone else anything! He is not obligated to run a gazillion distributions with trunk builds of Xorg and Mesa.
    Gazillion? What the hell are you talking about?

    Also, yes, his is not *obligated*. But it's easy to install a recent stack. Takes 20 minutes.

    Gah, I need to get back to what you said... "Gazillion"... Seriously, roflmao!

  8. #8
    Join Date
    Jan 2009
    Posts
    191

    Default

    Quote Originally Posted by KAMiKAZOW View Post
    The current messy situation wouldn't have happened if the well paid developers did their job in the first place.
    that's the thing - _currently overall situation is not that messy as he writes_, currently his situation is that messy because he using obsolete graphic stack. it was his personal choice and this is consequences of his choice - his problems, not other users and not some devs.

    Quote Originally Posted by KAMiKAZOW View Post
    maybe some Linux distributors should put some money where it actually counts instead of spending it on a design team that makes purple backgrounds and moves window buttons to the left side....
    that is true...

    Quote Originally Posted by RealNC View Post
    Blur works fine with Mesa Git and 2.6.35 here (HD4870)
    However, bypassing KWin's internal GL checks might be required for it to work.
    doesn't work for me but looking at how ugly even blacklisting for effects done (and that forced selective disabling of effects done via blacklisting at all) in kde and knowing that kde devs do not afraid of letting undocumented parameters and functions in releases i'm not surprised.

    to hell with it still, i hate blur anyway.

  9. #9
    Join Date
    Jun 2009
    Posts
    3

    Default

    Quote Originally Posted by RealNC View Post
    And what does this have to do with a KWin dev not wanting to test his code against the open drivers, allowing him to file bug reports to X.Org? Which is entirely up to him, I'll give you that, but why make excuses about an imaginary inability to do so?
    I agree that testing on all platforms is desirable, but its not always feasible, especially with free software. I think the steps they've taken though are pretty good:
    Query the driver about whether it supports feature xyz and only proceed if it does.
    If you don't have the hardware to test on, that's a pretty good strategy, unless, of course, the driver lies about what it actually supports. There's no excuse for a driver claiming capabilities it doesn't have.

  10. #10
    Join Date
    Oct 2007
    Posts
    1,273

    Default

    Quote Originally Posted by KAMiKAZOW View Post
    Those paid full-time Xorg/Mesa programmers should get off their lazy asses and fix their god damn drivers.
    They're a work in progress. For the most part, I don't hear those devs making lame excuses about why their stuff doesn't run perfectly yet (unlike this Kwin developer or Adobe).

    At any rate, patches and useful bug reports would probably be more helpful than whining about it on phoronix.com

Tags for this Thread

Posting Permissions

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