This is very similar to bug 410407. If it is really a gtk+2.0 bug, shouldn't it be marked as duplicate?
This is very similar to bug 410407. If it is really a gtk+2.0 bug, shouldn't it be marked as duplicate?