Comment 10 for bug 74219

That makes sense that it's not beryl then, since it doesn't work correctly before beryl is even started.

So that narrows it down to two components: Amarok or GNOME. I personally don't know how to attack this bug anymore and couldn't find a similar bug upstream at bugs.kde.org That leads me to suspect that it may be a GNOME bug, but I'm not sure how to approach it. We'll have to wait for someone with more knowledge in this area to work on it.

I saw a similar issue while I was running XGL/Compiz on Kubuntu Dapper a while back, but just assumed it was a compiz thing.

If anybody else has any info on this, please share it.