TextMate mate error: An uncaught exception was raised

Posted on February 28th, 2008 by Steve Jamesson

So, I’ve been using this sweet mouse for a few months, the Logitech MX Revolution. And I’ve been using TextMate for at least a year or two. Well, today, I was in my terminal window, and I wanted to open a few files in TextMate. So I typed my usual command:

  steve$ mate app/views/ public/

Usually TextMate would open up real nicely, with the two folders app/view and public ready to go in a TextMate project. But no. Instead I got this lovely, sensical message:

  2008-02-28 18:04:12.522 mate[484:10b] An uncaught exception was raised
  2008-02-28 18:04:12.527 mate[484:10b] [NOTE: this exception originated in the server.]
  *** Object does not implement or has different method signature
  2008-02-28 18:04:12.528 mate[484:10b] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '[NOTE: this exception originated in the server.]
  *** Object does not implement or has different method signature'
  2008-02-28 18:04:12.537 mate[484:10b] Stack: (
      2512601675,
      2423689467,
      2512600433,
      2438770118,
      2438767977,
      2512624298,
      2512624402,
      10507,
      14446,
      9754,
      9525
  )
  Trace/BPT trap

Beautiful. That makes perfect sense.

After a bit of research at this thread, it appears that my Logitech Mouse’s software, the Logitech Control Center (v 2.4 at this time), interferes somehow with mate. LCCDaemon, I believe it’s called, is the culprit.

The Fix

Null. There is no fix. Either a) remove LCC, or b) don’t use mate. I still haven’t decided on this one… I use both like crazy. If anyone else has found a fix or an acceptable workaround, please please please let me know.

Tags: TextMate //

6 Responses to “TextMate mate error: An uncaught exception was raised”

Kenny Saunders // Mar 9, 2008 at 8:46 pm

Did you ever find a work around? I’m having the same problem.
Steve Jamesson // Mar 13, 2008 at 6:24 am

No, haven’t found a solution yet. I’ve just stopped using the full power of the mouse; I spend way too much time in a shell to ignore mate.

A friend uses almost the same setup, with the mouse, but hasn’t received that error. He uses USBOverdrive. It doesn’t work for me, but it does work for him… worth a shot: USB Overdrive
Steve Jamesson // Apr 3, 2008 at 12:34 pm

So finally, I was able to get USBOverdrive to work for me. It took a bit of research, but it seems to be in good shape now.

Under my Apps > Utilities, there was an unistaller for LCC. I had removed all the Pref files manually, but I ran the installer, restarted, then USB Overdrive started working correctly. I guess it must have removed some files that I missed, maybe just some settings.

Works for me… I can assign anything I want to my Logitech mouse MX Revolution now! Whoohoo!
Matt // May 12, 2008 at 5:40 pm

Oh thank you, I was going crazy, trying to work this out!
Scott // May 12, 2008 at 10:18 pm

I don’t know how many hours you just saved me. Thank goodness your site is one of the first hits with that error message. I just installed LCC over the weekend but would have not connected to two. Thank you!!!
Clint Miller // Jun 11, 2008 at 3:42 pm

I just updated my LCC drivers to 2.6.0 (very recently released) and am glad to say that the mate command is working again, along with a bunch of Growl notifications. Hopefully some others will benefit from this update as well.

Steve Jamesson