Compositing "temporarily disabled" after upgrading o kde 4.5

terrax · 2010-08-31 12:43:10

I have this problem too.
Flickering graphic if you force compositing on.

This happens on a hd4650 mobility with the ati driver from repo.
The same thing happens in Ubuntu Maverick.

Anyone found a workaround? It doesn't help upgrading the graphic-stack to the latest available (have already tried that).
Is it a kde bug?

Last edited by terrax (2010-08-31 12:43:55)

xxxspuddy · 2010-08-31 15:56:33

Turn off direct rendering and the flickering might go away, it did for me with an onboard HD4200 using the xf86-video-atii driver.

terrax · 2010-08-31 16:00:30

Okay thx. But how well does it run and can you use blur without problems?
I have "reverted" back to the catalyst driver now, which doesn't have any problems but very slow blue effect. If I disable blur everything runs smooth.

Nerd King · 2010-08-31 17:49:02

Just a heads-up guys, I've had the flickering thing (on ATI open-source driver, lots of ATI people here I notice) and grabbed the 4.5.1 update. It fixed it. It's available on the kernel.org mirror though the server's up and down a lot as people are hammering it. DL speeds are good when you get them though (averaged 600k/s for me).

abraxas88 · 2010-08-31 17:59:32

Doesn't work on 4.5.1 either for me the whole system is updated, apart from sip package.

EDIT: Forgot to mention I'm using x86_64 Arch Linux, ATi Xpress 200M with open-source drivers.

Last edited by abraxas88 (2010-08-31 18:00:19)

iaguis · 2010-08-31 18:08:35

I have this flickering too since 4.5.0. ATI Radeon HD4850, open-source drivers, KDE 4.5.1 and x86_64

terrax · 2010-08-31 18:15:21

How is the performance with the oss drivers? What about blur with the oss drivers?
To be honest, catalysts performance with compiz is much better. I wonder how optimized kwin really is?

Last edited by terrax (2010-08-31 18:16:14)

Odaer · 2010-08-31 19:04:02

As usual it works okay with my old intel graphic.
I think its more likely something is trying to use something unsupported in the drivers.

Maybe you should try switch theme, apparently oxygen use some functionality not all driver support.

abraxas88 · 2010-08-31 19:07:54

It's not a question of themes, I don't use Oxygen.
Don't know why, it worked fine on PcLinuxOS since KDE 4.5.0
I guess they did some workaround in the drivers.

terrax · 2010-08-31 21:26:36

Its just odd the both the oss driver and the proprietary driver is sluggish.
Has anyone been lucky with the oss drivers?

abraxas88 · 2010-08-31 21:45:59

I disabled functionality checks in kwinrc and wrote

export LIBGL_ALWAYS_INDIRECT=1

in /etc/profile

It seems to work fine, even though blur doesn't want to be activated (still haven't understood why).
Try this workaround out and give me some feedbacks.

terrax · 2010-08-31 22:04:16

Thank you. It worked perfect.
I can use kde 4.5.1 compositing again with the oss drivers.

Now we just need a more performing kwin. It is still kinda sluggish both with the ati and catalyst driver.

terrax · 2010-08-31 22:09:28

Blur doesn't work for me neither with the ati driver. But it does work with the catalyst driver, but it is unuseable slow.

keripix · 2010-08-31 22:13:04

abraxas88 wrote:

I disabled functionality checks in kwinrc and wrote
export LIBGL_ALWAYS_INDIRECT=1
in /etc/profile
It seems to work fine, even though blur doesn't want to be activated (still haven't understood why).
Try this workaround out and give me some feedbacks.

I've tried the above workaround, but with the functionality checks enabled, and it works.

I've also tried the blur effect, but i can't see any difference when it's applied and when it's not. Does that mean blur isn't working?

Btw, tnx for the workaround.

abraxas88 · 2010-08-31 22:36:52

keripix wrote:

I've also tried the blur effect, but i can't see any difference when it's applied and when it's not. Does that mean blur isn't working?

You are welcome, and, yes, I'm afraid that means blur is not working. (Did the same thing to me).

kang · 2010-08-31 23:00:43

abraxas88 wrote:

I disabled functionality checks in kwinrc and wrote
export LIBGL_ALWAYS_INDIRECT=1
in /etc/profile
It seems to work fine, even though blur doesn't want to be activated (still haven't understood why).
Try this workaround out and give me some feedbacks.

Just want to add for clarity for whoever browses that it fixes the flickering problem as well, I had it on intel graphics with 4.5+ as well.

terrax · 2010-08-31 23:26:36

abraxas88 wrote:

keripix wrote:
I've also tried the blur effect, but i can't see any difference when it's applied and when it's not. Does that mean blur isn't working?
You are welcome, and, yes, I'm afraid that means blur is not working. (Did the same thing to me).

Unfortunately it doesn't work even if you fetch the latest git oss ati graphic stack. Still blur doesn't do anything.

iaguis · 2010-09-01 00:06:12

abraxas88 wrote:

I disabled functionality checks in kwinrc and wrote
export LIBGL_ALWAYS_INDIRECT=1
in /etc/profile
It seems to work fine, even though blur doesn't want to be activated (still haven't understood why).
Try this workaround out and give me some feedbacks.

Worked like a charm, thank you very much

terrax · 2010-09-01 00:08:34

Well there is a drawback forcing indirect rendering. The OpenGL stack reverts to OpenGL 1.4 rendering.
See glxinfo:

OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: Mesa DRI R600 (RV730 9480) 20090101  TCL DRI2
OpenGL version string: 1.4 (2.1 Mesa 7.9-devel)

So I won't be able to play Heroes of Newerth, if indirect rendering is forced

Last edited by terrax (2010-09-01 00:09:00)

gabriel9 · 2010-09-01 00:33:17

For me only help for fickering is to turn off blur.

Last edited by gabriel9 (2010-09-01 00:46:37)

ulixes · 2010-09-01 08:31:13

abraxas88 wrote:

I disabled functionality checks in kwinrc and wrote
export LIBGL_ALWAYS_INDIRECT=1
in /etc/profile
It seems to work fine, even though blur doesn't want to be activated (still haven't understood why).
Try this workaround out and give me some feedbacks.

Worked for me too.

ffjia · 2010-09-01 08:46:39

gabriel9 wrote:

For me only help for fickering is to turn off blur.

Did not work for me,

The X is freeze, when applying "turn off blur", I have to restart kde.

And now the icons are still flickering....

kde 4.5.1

Last edited by ffjia (2010-09-01 08:48:47)

the_inq · 2010-09-01 12:14:36

Hi everyone! Just wanted to mention that even after upgrading to 4.5.1, I have problems with desktop effects, especially with "present windows" and "window thumbnails". My chipset is Intel G41. And of course, whenever I change a setting in the Desktop Effects panel KDE freezes and I have to restart kdm :-(.

abraxas88 · 2010-09-01 12:58:54

Have you tried the workaround?

gabriel9 · 2010-09-01 13:28:28

When desktop freeze just turn off desktop effects: <Ctrl>+<Alt>+<F12>

Arch Linux

#26 2010-08-31 12:43:10

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#27 2010-08-31 15:56:33

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#28 2010-08-31 16:00:30

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#29 2010-08-31 17:49:02

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#30 2010-08-31 17:59:32

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#31 2010-08-31 18:08:35

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#32 2010-08-31 18:15:21

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#33 2010-08-31 19:04:02

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#34 2010-08-31 19:07:54

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#35 2010-08-31 21:26:36

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#36 2010-08-31 21:45:59

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#37 2010-08-31 22:04:16

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#38 2010-08-31 22:09:28

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#39 2010-08-31 22:13:04

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#40 2010-08-31 22:36:52

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#41 2010-08-31 23:00:43

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#42 2010-08-31 23:26:36

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#43 2010-09-01 00:06:12

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#44 2010-09-01 00:08:34

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#45 2010-09-01 00:33:17

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#46 2010-09-01 08:31:13

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#47 2010-09-01 08:46:39

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#48 2010-09-01 12:14:36

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#49 2010-09-01 12:58:54

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

#50 2010-09-01 13:28:28

Re: Compositing "temporarily disabled" after upgrading o kde 4.5

Board footer