I am a new iMAC user after many years on a PC. Quite often my mouse cursor freezes up on the screen and my only remedy seems to be to shut down and reboot. This can't be right! There must be a better solution. Can anyone out there assist me?
Having the same issue here. I am running the latest leopard update 10.5.2 and graphics update as well. As well as I can remember the courser freeze just started happening about a week ago and before then this has never happened. Redundant backups are in place in case the unexpected happens although my first impression on this is the operating system or software conflict not hardware.
Same thing is happening to me since updating a MBPro to 10.5.2, It is very intermittent, and often happens after the computer has been sitting idle for awhile (not asleep). When I increase the screen brightness, the cursor will be stuck. Force quit, nor any other keyboard input works. Unplugging all USB and FW devices does not help. The only solution is to force a shutdown with the power button and then do a restart.
The same thing happened on my macbook after I installed 10.5.2. It will happen if I only have Keynote running or when I have Photoshop,Ilistrator,itunes all working hard.
Are Parameter RAM (PRAM) and non-volatile RAM (NVRAM) the same things, or does it depend on the computer model?
What is stored in this (these) in 10.5.2?
Is there a reader for these?
It seem that one would first delete the caches (mor likely to become corrupted?) amd if that doesnt work to reset the PRAM where mouse settings used to be stored.
well, this thread is a bit old but i came upon it when i searched for it because my cursor freezes when i log my mom out of her account and try to log onto mine or vise versa. Only at the login screen is where it freezes same with the keyboard. Tried unplugging the USB and still nothing. I trashed the caches to see what it does if anything? Ill post back with results later in the week.
I've had the exact same problem ever since I upgraded to Leopard, and the successive updates, including the very latest 10.5.3, have not solved it! I am so disappointed. This is a severe bug. I used to be able to fix it by logging in and out, but today I had to shutdown and restart because my keyboard logout command was not getting through. I can't be sure about this, but it seems as though the problem occurs if I happen to be still be moving the mouse cursor and the logout sequence is engaged. It's as if moving the mouse cursor at this critical time is causing the system to have to keep track of it AT THE SAME TIME the system is trying to kill my user processes. The mouse cursor process ends up dead alright, all the way to the login screen! (Those who are familiar with how UNIX manages processes will understand what I'm talking about.) Please Apple, fix this. Please. This didn't use to happen in Tiger, so how does something like this get broken?
Installed Leopard (V.5.3) 2 weeks ago, and have had 3 mouse cursor freeze ups. Only way to recover has been via a hard shut down and reboot the computer. My son in law a highly skilled IT professional says its is usually an operating system issue.
If you have had a mouse cursor freeze or a fix please post to this thread an hopefully apple will provide a solution in future updates.
I can make the mouse freeze on purpose. Just wiggle the mouse when it has the blue screen and it freezes, then push control + command + eject button to shut the computer down.
My cursor freeze ups seemed to occur when scrolling in Firefox 2, since I installed firefox 3 several weeks ago the freeze problem has not occured again, has any anyone had a similar experience?
My cursor freeze ups seemed to occur when scrolling in Firefox 2, since I installed firefox 3 several weeks ago the freeze problem has not occured again, has any anyone had a similar experience?
Hi. I just wanted to let apple know that I have the same problem during logout. If I happen
to move the mouse during the logout process...my mouse pointer will freeze. I bought my
iMac with 10.5.2 and it did this from the begining. Even after installing 10.5.3 and 10.5.4
updates.
