The Qt developers examined the problem and suggested a workaround, but also proved that the problem is indeed in cairo-dock.
This problem isn't fixed yet, so I think this bug should not be closed, much less being marked as invalid.
The possible workaround requires the user to load cairo-dock in a way that's not easy for the average user and such workaround should not be needed any way.
Cairo-dock needs to be fixed.
"The bug is NOT in Qt.
The reason is that something in cairo-dock or its supporting libs sets a custom colormap - on the root window...
The proper workaround is NOT to disable ARGB clients (this would eg. break plasma or translucent UI styles) but to remove the property once cairo-dock has started and (if possible) before anything else starts up.
The Qt developers examined the problem and suggested a workaround, but also proved that the problem is indeed in cairo-dock.
This problem isn't fixed yet, so I think this bug should not be closed, much less being marked as invalid.
The possible workaround requires the user to load cairo-dock in a way that's not easy for the average user and such workaround should not be needed any way.
Cairo-dock needs to be fixed.
This is the workaround suggested by Qt people (see http:// bugreports. qt.nokia. com/browse/ QTBUG-5464):
"The bug is NOT in Qt.
The reason is that something in cairo-dock or its supporting libs sets a custom colormap - on the root window...
The proper workaround is NOT to disable ARGB clients (this would eg. break plasma or translucent UI styles) but to remove the property once cairo-dock has started and (if possible) before anything else starts up.
xprop -root -remove RGB_DEFAULT_MAP"