I am sorry about that. this issue happens only in chrome under linux (which is basically ChromeOS). the good news is that it will be fixed really soon!