it seems the more kde 4.8 gets adopted the more this bug gets revealed...
maybe a backport of your solution might be worth considering
it seems the more kde 4.8 gets adopted the more this bug gets revealed...
maybe a backport of your solution might be worth considering