{"action":"opened","issue":{"url":"https://api.github.com/repos/dnschneid/crouton/issues/1741","labels_url":"https://api.github.com/repos/dnschneid/crouton/issues/1741/labels{/name}","comments_url":"https://api.github.com/repos/dnschneid/crouton/issues/1741/comments","events_url":"https://api.github.com/repos/dnschneid/crouton/issues/1741/events","html_url":"https://github.com/dnschneid/crouton/issues/1741","id":76047159,"number":1741,"title":"Corrupted mouse Unity 2015 Pixel","user":{"login":"fortinj1354","id":733915,"avatar_url":"https://avatars.githubusercontent.com/u/733915?v=3","gravatar_id":"","url":"https://api.github.com/users/fortinj1354","html_url":"https://github.com/fortinj1354","followers_url":"https://api.github.com/users/fortinj1354/followers","following_url":"https://api.github.com/users/fortinj1354/following{/other_user}","gists_url":"https://api.github.com/users/fortinj1354/gists{/gist_id}","starred_url":"https://api.github.com/users/fortinj1354/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fortinj1354/subscriptions","organizations_url":"https://api.github.com/users/fortinj1354/orgs","repos_url":"https://api.github.com/users/fortinj1354/repos","events_url":"https://api.github.com/users/fortinj1354/events{/privacy}","received_events_url":"https://api.github.com/users/fortinj1354/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-13T16:32:29Z","updated_at":"2015-05-13T16:32:29Z","closed_at":null,"body":"So I've been having the same corrupted mouse cursor issue that it seems a lot of other people are having (using Trusty Unity on the new Pixel). Every time when switching back to unity I have the issue, but I have found that for some reason, with a 100% reproduction rate on my end, if I type a single character into xterm at any point after switching back to unity, it fixes the mouse issue and stays fixed until I switch to chromeos and back again. I have not updated my graphics drivers as seen here #1519 and actually discovered this behavior while I was getting ready to do this."}}