Sure that this problem is already fixed? Because I'm still able to reproduce this bug on openbox 3.5.2-3.
Sure that this problem is already fixed? Because I'm still able to reproduce this bug on openbox 3.5.2-3.