1Password-Typinator conflict rekindles memories of OS 8.6 and Conflict Catcher

In the 90’s I used Jeff Robbin’s Conflict Catcher 8.0.1, from Casady & Greene, to prevent system extensions from interfering with each other. It cost a pretty penny (US$80) but I bit the bullet and bought myself a copy. With it, I reached a wonderful stability despite using a diverse array of extensions.

So much stability it offered that I skipped OS9 entirely, and in 2002 I I leapt into OS X rather dramatically. Conflict Catcher was abandoned with great joy!

All this reminiscing because Typinator failed to work. Thankfully its menubar icon was displaying an odd colour and I clicked to see this message:

Typinator

I quit my applications one by one and then I realised it must be 1Password. And sure enough it was. So 1Password 3.8.20 inactivates Typinator 5.1. A conflict! Hmph! I thought I left this behind in 2002!

With OS X disabling the “event monitor” as 1Password operated in “secure keyboard mode”, I wonder if this is due to Mountain Lion (update: ML it is, see below), Typinator 5.1 or some thing for 1Password to deal with.

The 1Password webpage FAQ talks about a complication with a Google Chrome password field, but that did not apply here.

So I wrote to the Agilebits forum (which they’ve made easy to do) and hope for a solution eventually. This problem sounds slightly similar to one others had experienced earlier this year.

In the meantime, I simply to shut down 1Password when Typinator complains. I can live with that for now.

Update – Well I wrote that about 3am and there was a tweet, blog comment and email awaiting me at 7am when I woke – Agilebits is certainly responsive!

Apparently this problem emerged with Mountain Lion and I simply have to minimise, not hide, 1Password:

“Hey Otterman,

Thanks for bringing this up.

There is a bug we have tracked down where hiding 1Password will enable Secure Input mode (i.e. selecting **1Password > Hide 1Password** from the menu bar or using the ⌘H keyboard shortcut). We’re investigating a fix, but I don’t have a time frame for a specific release.

In the meantime, if you **minimize** 1Password rather than hiding it, and you should not have the problem. Also, you can switch to another application and use the **Hide Others** command ⌥⌘H to hide 1Password (as well as all other open apps) and this will not trigger Secure Input.

Please let us know if refraining from hiding 1Password doesn’t resolve the issue you were having, and we can look into it more.

Cheers,”


Khad Young
Forum Choreographer, AgileBits
http://agilebits.com/support

Advertisements

9 thoughts on “1Password-Typinator conflict rekindles memories of OS 8.6 and Conflict Catcher

  1. Hey Otterman,

    Thanks for bringing this up. We’ve replied to you on Twitter, but I just wanted to express the situation in a bit more than 140 characters if that’s okay. 🙂

    There is a bug we have tracked down where hiding 1Password will enable Secure Input mode (i.e. selecting **1Password > Hide 1Password** from the menu bar or using the ⌘H keyboard shortcut). We’re investigating a fix, but I don’t have a time frame for a specific release.

    In the meantime, if you **minimize** 1Password rather than hiding it, and you should not have the problem. Also, you can switch to another application and use the **Hide Others** command ⌥⌘H to hide 1Password (as well as all other open apps) and this will not trigger Secure Input.

    Please let us know if refraining from hiding 1Password doesn’t resolve the issue you were having, and we can look into it more:

    http://support.agilebits.com/discussion/new

    Cheers,


    Khad Young
    Forum Choreographer, AgileBits
    http://agilebits.com/support

  2. Thanks for this post. I can’t wait for this to be fixed. But I don’t understand this suggestion to minimize 1Password – I don’t have 1Password (the program) open. I just have the icon running in Chrome.

  3. Still not working for me. I have “unable” 1Password in Chrome in order to get Typinator to work. Not sure what’s triggering Typinator to stop working, but there’s definitely still a conflict here.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s