I've encountered something similar just once, but it worked after rebooting (or maybe even relogging in). Tried that?