Frightening mouse cursor glitch

Discussion in 'OS X Mountain Lion (10.8)' started by powers74, Nov 25, 2012.

  1. powers74, Nov 25, 2012
    Last edited: Nov 25, 2012

    macrumors 68000

    powers74

    Joined:
    Aug 18, 2008
    Location:
    At the bend in the river
    #1
    I've been using MountainLion for about six months now and love it. However, this afternoon I noticed something very disturbing. The mouse cursor is rubber-banded to about three inches from the top, and three inches from the left of the edge of my screen. I can move the cursor momentarily, but it snaps right back to that position after a seccond or two.

    Now I say this afternoon, but really, that's just when I noticed it was a problem. My wife and I watched a movie on Netflix last night and once the movie started playing is when the symptom began as far as I know. I thought it just had something to do with BS Netflix, but apparently not.

    I shut down, and restarted and I thought I had fixed the problem because it didn't seem to be doing it any more at the log-in screen. However, once I logged in, the symptoms started again. So I logged out to see if the problem was evident at the log-in screen, and it in fact is. Is this a problem anyone else has had? Is it possibly a Trojan/malware of some sort? Any ideas welcome.
     
  2. macrumors 601

    sammich

    Joined:
    Sep 26, 2006
    Location:
    Sarcasmville.
    #2
    What mouse are you using? And maybe if you can open up Console.app (/Applications/Utilities/Console) and see if there are any messages appearing as the cursor beings to jump around.
     
  3. thread starter macrumors 68000

    powers74

    Joined:
    Aug 18, 2008
    Location:
    At the bend in the river
    #3
    MagicMouse, which I also love. Ok, I'll see if I can navigate that much. What sort of messages do I need to be looking for?
     
  4. thread starter macrumors 68000

    powers74

    Joined:
    Aug 18, 2008
    Location:
    At the bend in the river
    #4
    I don't know. I shut down again, this time over night. Started back up, the problem disappeared as mysteriously as it appeared. I'll go ahead and blame Silverlight.
     

Share This Page