I had this problem, and was able to get around it by disabling mouse reporting in iTerm2.