This bug is occurring when you have a decimal number set as the protect time on the chat gcontrol options.
Example: If you've set "0.1" for the protect time option, you wont be able to disable the protectior after enabling by command.
xat allows you to turn on the protection but nobody can disable it (even an ID ranked as main owner cannot turn it off).
Apparently any value with a dot breaks it. Examples: 0.2, 0.4, 0.8, 2.5, and so on.
Adding a comma will force reset and return the input value to 1 (default time, an hour).
Whole numbers (e.g. 1, 2, 3, etc.) are working fine as far I know though.
I'm referring to this option (click here for the direct image link):