This has been reported once before, in which case a reboot solved the problem.
So just try a reboot.