compiz team mailing list archive

[mabawsa <mabawsa@xxxxxxxxx>]

*** This bug is a duplicate of bug 459647 ***
    https://bugs.launchpad.net/bugs/459647

Yeah this is due to compositing that docky needs. What I suggested
wasn't a fix or work around only to see if compiz or related update
causes this. I had a machine that had not been updated for a few days
and went through each update I could think of that would cause this
error individually. I wanted to be more precise than pointing the finger
at compiz (this hasn't been updated recently) but unfortunately on the
machine I could not reproduce the problem. It makes me think that there
is something wrong in the configuration of the machine that shows this
issue or something wrong with gnome-panel (I have this disabled on the
machine I updated "blindly" that does not show the problem) as I use awn
solely on the machine that does not show the bug. I will create a new
user tonight on the machine that shows the error and see if the cursor
error persists on this new user. I will also try disabling gnome-panel.

If the cursor issue annoys you, then you can use metacity's native
compositing, but you won't have the bling that compiz gives.

Alt-F2
gconf-editor
key:
/apps/metacity/compositing_manager

Then run the metacity --replace

-- 
Schizophrenic cursors. Desktop cursor theme changes from the user selected theme. However the application cursor theme is correct.
https://bugs.launchpad.net/bugs/552016
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in ubuntu.