DaVince wrote: > I've encountered something similar just once, but it worked after rebooting (or maybe even relogging in). Tried that? Yes, I did. I performed shutdown and boot many times without any result.