I've seen that too, and yeah, the only solution I had for the user was to reboot.