The blog

TextMate mate error: An uncaught exception was raised

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.

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


  1. Kenny Saunders
    2008.11.13

    Did you ever find a work around? I’m having the same problem.


  2. Steve
    2008.11.13

    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](http://www.usboverdrive.com/ “”)


  3. Steve
    2008.11.13

    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!


  4. Matt
    2008.11.13

    Oh thank you, I was going crazy, trying to work this out!


  5. Scott
    2008.11.13

    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!!!


  6. Clint
    2008.11.13

    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.


  7. erfon
    2009.02.12

    I’m getting the exact same error. I used to have LCC installed but haven’t in quite a while. I ran the uninstaller again just in case but it said nothing was installed either. I even checked for any running LCC processes but didn’t see any… I’m still getting that error, it’s annoying!


  8. Steve
    2009.02.12

    @erfon - I was pretty sure that removing all LCC stuff took care of it. I did notice, though, that an update for Textmate was released; I installed it just the other day. Maybe try applying the TM update, see if that helps.


  9. James Strachan
    2009.05.18

    Awesome - huge thanks! I’d never have guessed it was LCC breaking TextMate!

    I found updating LCC to the latest version (2.6) fixed this too!

Leave a Reply