El Capitan incompatible with Mad Catz Editor
I upgraded my Macbook Pro to OSX 10.11 El Capitan but sadly the mapping software for my Mad Catz Mouse (M.M.O.7) does not start anymore.
Crash Report
Process: editor [33209]
Path: /Applications/Mad Catz Editor.app/Contents/MacOS/editor
Identifier: com.madcatz.MadCatz.editor
Version: 1.0 (1.1.69)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: editor [33209]
User ID: 501
Date/Time: 2015-10-07 13:41:42.846 +0200
OS Version: Mac OS X 10.11 (15A284)
Report Version: 11
Anonymous UUID: 8B5B6605-7448-4DDA-627C-11145BEF80FE
Sleep/Wake UUID: 4D337680-5145-4CF7-B785-93E78B39BE4D
Time Awake Since Boot: 100000 seconds
Time Since Wake: 17000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[MCProfile profile]: unrecognized selector sent to instance 0x10042c350'
abort() called
terminating with uncaught exception of type NSException
Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff8b3a7bd2 __exceptionPreprocess + 178
1 libobjc.A.dylib 0x00007fff866ac4fa objc_exception_throw + 48
2 CoreFoundation 0x00007fff8b4110ed -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
3 CoreFoundation 0x00007fff8b3183d1 ___forwarding___ + 1009
4 CoreFoundation 0x00007fff8b317f58 _CF_forwarding_prep_0 + 120
5 MCDeviceLib.dylib 0x0000000100041587 -[MCProfile checkName] + 119
The result is that I have a lot of hovering problem (hover event does not fire anymore) and shortcuts macros do not work at all.
Does anyone have a workaround ?
I contacted the Mad Catz team via Facebook and Twitter 2 days ago and I still have no answer.
Solution 1:
I'm having the same issue, in a chat with Madcatz support they stated to come up with a new driver by end of this year - still a bit to suffer unfortunately.
Installing USB overdrive and controller mate are too much for me to achieve a little bump in functionality.
Solution 2:
Because of the new security implemented in El Capitan (see here), and if Mad Katz installs stuff in protected directories (such as /usr/bin
), chances are the upgrade hosed the mouse. Look in
/Library/SystemMigration/History/Migration-something-about-your-computer/QuarantineRoot
and see if there is anything about the mouse. This is likely, especially if the mouse required a kernel extension to actually function. In this case you have to wait until Mad Katz release a compatible upgrade... or you might want to disable the extra protection and reinstate the kernel extension.