@dinocro I see, so maybe it's really something wrong with the extension. Perhaps you can visit its webpage on the store, and read latest comments - maybe someone else has the same issue like you, and/or add your complain about it, so that the author may try fix it.
