Linked by Thom Holwerda on Tue 10th Feb 2009 17:13 UTC
X11, Window Managers Ever since its inception, there have been problems with Compiz; people unsatisfied with the direction of the project forked it, then they merged again. Recently, the project, now known as Compiz Fusion, faced other problems, such as multiple branches and a lack of direction. A major reorganisation of the project is supposed to fix all this.
Thread beginning with comment 348324
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: KWin
by gilboa on Wed 11th Feb 2009 22:34 UTC in reply to "RE[3]: KWin"
gilboa
Member since:
2005-07-06

Seems that KDE (or actually, the latest QT) exposes a number of deficiencies in the nVidia binary driver.
nVidia is aware of this problem and trying to fix it.

You may want to try the InitialPixmapPlacement and GlyphCache settings. [1] (In theory, they are no longer needed, but I'm stilling using them and both 2D and kwin composition seem to be working just fine)

- Gilboa
[1] http://www.nvnews.net/vbulletin/showthread.php?t=118088

Reply Parent Score: 2

RE[5]: KWin
by sbergman27 on Wed 11th Feb 2009 23:10 in reply to "RE[4]: KWin"
sbergman27 Member since:
2005-07-24

Seems that KDE (or actually, the latest QT) exposes a number of deficiencies in the nVidia binary driver.

Seems that the KDE (or maybe the latest QT) devs did not do proper (or really any) research on the driver support they were depending upon when they were blindly making those decisions and blindly writing all that code. It's not like people weren't trying to point it out to them for the last several years. Go KDE...

Edited 2009-02-11 23:12 UTC

Reply Parent Score: 2

RE[6]: KWin
by gilboa on Thu 12th Feb 2009 10:53 in reply to "RE[5]: KWin"
gilboa Member since:
2005-07-06

"Seems that KDE (or actually, the latest QT) exposes a number of deficiencies in the nVidia binary driver.

Seems that the KDE (or maybe the latest QT) devs did not do proper (or really any) research on the driver support they were depending upon when they were blindly making those decisions and blindly writing all that code. It's not like people weren't trying to point it out to them for the last several years. Go KDE...
"

You got it completely backwards!
As long as the KDE (or actually QT developers) stick to documented API's (be that OpenGL or xlib), they can, or actually, they must assume that who-ever sits on the other hand (of the API) has taken the time to implement and test each and every code path in their driver as dictated by the API.

Tell me, should QT disable support for a certain feature just because 10% of the drivers do not support it and/or support it badly? How far are you willing to go to appease broken driver developers?

What's next? Should the Linux kernel developers stop developing the Linux kernel just because a certain binary driver developer has a hard time keeping up?

- Gilboa
* And I'm not talking nVidia; If anything, as much as I dislike binary drivers I must admit that nVidia is doing it's best to give the best possible support for Linux users

EDIT: Removed a redundant comment.

Edited 2009-02-12 10:56 UTC

Reply Parent Score: 2