11-12-2009 01:52 PM - edited 11-12-2009 01:54 PM
Yeah just double checked, no prefs, no LCC and the problem persists.
I have found this similar entry with a rather unpleasant solution. I hesitate taking on such a task without someone at Logitech confirming that I am S.O.L. and have no other choice.
Guess thier mice are just crap?
11-13-2009 07:53 AM
Well, I gave the surgery a try, found a clear bit of broken plastic that looks like it came from the bit that holds the laser in place, which was also cracked. So regardless it looks like I will need a new one sooner rather than later. I did the operation and it seems to have worked at least temporarily. It was indeed the little metal bit that had just worn and needed a little spring to it. Not really having any ill effects from the other broken or cracked parts, still, I would hope for better quality.
01-07-2010 07:49 AM
ended up tossing mine. even after the surgery, which fixt the problem, the mouse just felt a little wonky after. I have ordered the new MX, doesnt have the auto smooth scroll, but hopefully they learned from the mistakes of the last one. If not, this will be my last Logitech product.
02-15-2010 12:52 PM
After updating LCC to 3.x I had the same problem!
I tried removing LCC from System Preference panel and it did not work, still the LCC was installed.
I solve the problem by removing the LCC using the uninstaller located in the Utility folder of Mac OS X.
It seems that this is a software problem...
02-16-2010 11:45 AM
I have received the performance MX and it is not much better. the accuracy when selecting text or even just clicking on things seems a little off.
It is making me just want to give up and deal with the apple mouse.
06-05-2010 12:51 PM - edited 06-05-2010 12:54 PM
In fairness to Logitech ...
I found this forum searching about the "double-click problem" ... and I was searching about the topic because I began experiencing the same problem a couple of months ago with my Kensington mouse, running OS X 10.4.11 on a Power Mac G5.
From what I've read so far, I'm coming to the conclusion that the problem is NOT with Logitech, NOT with OS X 10.6 Snow Leopard (as some have suggested) and NOT with Intel-based machines.
To me, the finger seems to be pointing at Apple. (Some sort of update?)