Originally Posted by RyanLupin
What third party keyboards have you tried?
I believe it was a keyboard modeled after the new keyboard in 4.2.
In any event, regardless of what apps may trigger this issue (Chrome or otherwise) the underlying issue seems to be that there is a root file or directory that should be write-protected but which clearly is not, and the solution is to get Samsung to recognize it and do something! Unfortunately, that's easier said that done, apparently.