Administrator
|
I upgraded to 4.5.2 yesterday, and today I noticed that Present Windows is broken. When activating the effect it first seems to work, but then everything slows down and the windows disappear (I only see the darkened backgrounds). Finally compositing is automatically disabled.
If I disable functionality checks I can see that the CPU shoots up to 100 % when using the effect. Just tried around now and noticed that disabling Direct Rendering makes it work as before. The Desktop Grid effect with Present Windows enabled always works, even with direct rendering. Some more information: Arch KDE 4.5.2 packages (vanilla) Nvidia GeForce FX 5200 card with the nvidia-173xx-173.14.28 driver Compositing type: OpenGL, Texture From Pixmap; XRender doesn't have this problem
Problem solved? Please click on "Accept this answer" below the post with the best answer to mark your topic as solved.
10 things you might want to do in KDE | Open menu with Super key | Mouse shortcuts |
Administrator
|
On Trunk, using Intel graphics, this works without problems. Don't know if any changes were made between 4.5.2 and Trunk though.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
KDE Developer
|
There was a change between 4.5.1 and 4.5.2 which makes the Lanczos filter work on more graphics cards. Unfortunately it does not work on them. You have to add your graphics card to the magic blacklist
|
Administrator
|
How do I do that?
Problem solved? Please click on "Accept this answer" below the post with the best answer to mark your topic as solved.
10 things you might want to do in KDE | Open menu with Super key | Mouse shortcuts |
KDE Developer
|
Please follow the instructions on http://blog.martin-graesslin.com/blog/2 ... n-effects/
|
Administrator
|
Sweet, thanks for the link. In case anyone else encounters this, I did the following:
1. Run
You'll see something like this:
2. Open ~/.kde[4]/share/config/kwinrc in a text editor. 3. Under [Blacklist][Lanczos], I added
(The values are from the command in step 1.) 4. Restart KWin or logout and login again. mgraesslin: Should I report it somewhere so it can be added by default, or are you aware of it now? Is this something that might be fixed in a newer driver version? (Note that I didn't downgrade as I wrote in my original post - it seems to be more troublesome than I thought.)
Problem solved? Please click on "Accept this answer" below the post with the best answer to mark your topic as solved.
10 things you might want to do in KDE | Open menu with Super key | Mouse shortcuts |
KDE Developer
|
I doubt that I will update the blacklist in a minor release and the blacklist ist designed to not blacklist new driver versions, so don't think that it's worth reporting it.
|
Registered users: bancha, Bing [Bot], Evergrowing, Google [Bot], lockheed, mesutakcan, sandyvee