Conflict with Wacom Create Tablet

ChristianP · 12-29-2011, 09:18 AM

This seems an issue with your specific MacBookPro model. Does your system include an NVidia 9400 GPU other than a 9600? Could you check if the problem is still there after putting the system to sleep once?

davewarden@me.com · 12-31-2011, 01:05 AM

Downloaded and reinstalled the latest DisplayLink driver from the website just to be certain I was up to date.

Tried tablet and same problem experienced, cursor moves to, and locks in, the upper left hand corner. Put the computer to sleep but problem persisted on restart.

Checked and I do indeed have the NVidia 9400 GPU installed in addition to the 9600.

ChristianP · 01-02-2012, 09:35 AM

Thanks for the tests. Unfortunately the problem seems related to your specific model and the dual GPU setup. The bug is on the OS side, so we can't fix it. Similar issue have been fixed on 10.7.2, so we do hope that Apple will fix this issue in the next releases.

12-31-2011, 01:05 AM	#2
davewarden@me.com Junior Member Join Date: Dec 2011 Location: Reading, PA Posts: 2	Problem Remains Downloaded and reinstalled the latest DisplayLink driver from the website just to be certain I was up to date. Tried tablet and same problem experienced, cursor moves to, and locks in, the upper left hand corner. Put the computer to sleep but problem persisted on restart. Checked and I do indeed have the NVidia 9400 GPU installed in addition to the 9600.

12-29-2011, 09:18 AM	#1
ChristianP Senior Member Join Date: Apr 2011 Posts: 280	This seems an issue with your specific MacBookPro model. Does your system include an NVidia 9400 GPU other than a 9600? Could you check if the problem is still there after putting the system to sleep once?

01-02-2012, 09:35 AM	#3
ChristianP Senior Member Join Date: Apr 2011 Posts: 280	Thanks for the tests. Unfortunately the problem seems related to your specific model and the dual GPU setup. The bug is on the OS side, so we can't fix it. Similar issue have been fixed on 10.7.2, so we do hope that Apple will fix this issue in the next releases.