Your best friend for file transfer.

Fetch application logoFetch

Keychain problem (8 posts)

  • Started 16 years ago by ktekinay
  • Latest reply 16 years ago from Scott McGuire
  • ktekinay Member

    I just updated to v.5.2.1 (not sure it that matters), and now Fetch can't properly access items in the Keychain. Worse, it makes the default keychain unavailable to other apps and requires a restart to fix.

    This is on an Intel iMac with all the latest System updates. I've recreated the login keychain with no effect. Any thoughts?

    Posted 16 years ago #

  • Scott McGuire Administrator

    Hi,

    We're sorry to hear you're having problems with Fetch and the keychain.

    I would try doing the following:

    * Run the Keychain Access application, which is in the Utilities folder inside your Applications folder.
    * Choose Keychain Access > Preferences
    * Click on the "First Aid" tab
    * Make sure both "Synchronize login keychain password" and "Set login keychain as default" are checked.
    * Then choose Keychain Access > Keychain First Aid
    * In the password field of the Keychain First Aid window, enter your Mac OS X admin password (this should be the same as your Mac OS X login password).
    * Click the Repair radio button.
    * Click the Start button.
    * Once it's done, close the Keychain First Aid window.
    * Click on the "login" item in the Keychains pane of the Keychain Access window.
    * Choose Edit > Change Settings for Keychain "login"
    * Make sure all the checkboxes the setting are unchecked, and click Save.

    And let us know if that fixes the problems or not.

    Thanks,

    Scott McGuire
    Fetch Softworks

    [This message has been edited by ScottMcGuire (edited 06-07-2007).]

    Posted 16 years ago #

  • ktekinay Member

    I did all that before posting AND created a new login keychain too. None of that helped.

    Posted 16 years ago #

  • Scott McGuire Administrator

    Hi,

    When you say Fetch can't properly access items in the Keychain, what exactly happens? Do you get an error message?

    And do you get an error message in the other applications that can't use the keychain too?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 16 years ago #

  • ktekinay Member

    Fetch freezes for about a minute, then the "An item has changed" dialog comes up with the "Change All" button. If you click that, it whirls for a LONG time, then comes up with an OS error. Meanwhile, the login keychain becomes unavailable in Keychain Access and to other apps, and I have to restart to resolve it.

    I can get the OS error if you need it, but it means I have to recreate the circumstances and restart, and it takes 5-10 minutes. Let me know if it's important.

    Posted 16 years ago #

  • Scott McGuire Administrator

    Hi,

    Thanks for the additional information. No, I don't think we need the exact OS error message right now.

    So other keychain-using applications work fine until you try to use Fetch? What are some of the other keychain-using applications you're using?

    And do you have keychain syncing turned on in the .Mac system preferences pane?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 16 years ago #

  • ktekinay Member

    Yes, other apps like Mail, FileMaker Pro, Timbuktu, and services like .Mac sync (turned on) and network, access the keychain without issue until I launch Fetch.

    Posted 16 years ago #

  • Scott McGuire Administrator

    Hi,

    I'm sorry not to have an answer for you right away, but no one else has reported a problem like this before. Could you please try the following?

    * Turn off .Mac syncing of the keychain temporarily.
    * Create a new login keychain (which will, presumably, be empty).
    * Try running Fetch, opening a connection, and saving a password in the keychain.
    * Close that connection, and try opening it again (so Fetch will read the password out of the keychain).

    Let us know what happens. Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 16 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.