Bug#435195: compiz-kde: kde-window-decorator cannot start
reassign 390929 compiz-kde
forcemerge 390929 435195
found 390929 0.5.0.dfsg-2
thank you
Marcus Better wrote:
> When starting compiz with KDE, I get
>
> ~$ compiz --replace gconf &
> [1] 21501
> marcus@melech:~$ GLX_EXT_texture_from_pixmap is not available with direct rendering.
> GLX_EXT_texture_from_pixmap is available with indirect rendering.
> Fönsterhanterarvarning: Misslyckades med att läsa in temat "Clearlooks": Misslyckades med att hitta en giltig fil för temat Clearlooks
>
Even I can't read German anymore (please set LANG to C to any english
locale before testing next time :)), I guess this warning is caused by
some clearlooks package not being instead. compiz-gtk suggests
gnome-themes because of things like this. Since you seem to be starting
compiz with the gtk-window-decorator, clearlooks might be required here.
> ~$ kde-window-decorator&
> [2] 22238
> marcus@melech:~$ kde-window-decorator: Could not acquire decoration manager selection on screen 0 display ":0.0"
>
Is this really the way to start compiz in kde ? doesn't a plain 'compiz
--replace' or something like 'compiz --replace kde' work ?
Also note that 'gconf' is loaded automatically by compiz if present (see
the /usr/bin/compiz script).
> As a result some windows didn't have frames around them. It seems the
> reason why kde-window-decorator fails to start is simply that
> gtk-window-decorator was running:
>
> ~$ ps ax|grep window-dec
> 21508 pts/2 S 0:00 /usr/bin/gtk-window-decorator --replace
>
> This should probably not happen under KDE. Killing it and starting
> kde-window-decorator fixed the problem.
>
We have several reports about kde having problems being replaced by
compiz. KDE folks told me it should work fine, but I really need to take
a look/try at it one day. Obviously, something's going wrong there.
Merging with other bugs.
Brice
Reply to: