Yeah, had exactly the same problem once and resetting the widget location fixed it. Wonder why this bug even occurs though.