Re: xcompmgr and KDE

Quoting Elias Pouloyiannis <[email protected]>:

> i am using KDE CVS version 20040117 (or whatever)
> 
> Although using xcompmgr with other DE (plain such as afterstep, etc) works 
> smoothly, using it with KDE will lock the xserver
> 
> xcompmgr outputs in a loop:
> 
> error 3 request 3 minor 0
> error 9 request 138 minor 4
> error 9 request 141 minor 1
> error 3 request 20 minor 0
> error 136 request 138 minor 7
> 
> and it will keep on giving the above untill i try to move a window.
> At the first move attempt it will segfault and lock the xserver
> 
> I know that thing are still under heavy development but i don't get why i 
> don't get the same behaviour with afterstep for example

I haven't tried this myself, but I think this might be the issue.  KDE can use
xrender to draw its "transparent" menus and such.  Would this cause any
problems with rendering to memory?? or conflicts with xcompmng use of xrender?

just a thought, its the only thing i can think of, i'm just a newb, so i'm
probably way out of line in my thinking.

> _______________________________________________
> xserver mailing list
> [email protected]
> http://freedesktop.org/mailman/listinfo/xserver
>