Menu

#832 Can't open a recent project

3.6
closed-invalid
nobody
None
5
2016-07-27
2016-07-27
No

MacOS X latest version: 10.11.6

I can't open a recent project (with 4.0 and the current release)

I get an error box (attached) saying

org.eclipse.jgit.errors.UnsupportedCredentialItem: ssh ...

The project file is located in a git repository on the local harddrive. What can I do? The status line is something like "error when checking out the project from the remote repository".

1 Attachments

Discussion

  • Patrick Gundlach

    I should add: I have created a project, translated one HTML file and saved the files (command D). Then quit OmegaT and restart it and use "recent projects" and selected my project.

     
  • Aaron Madlon-Kay

    This does not make sense for both 4.0 and 3.6 or earlier. Please indicate the exact versions of OmegaT you are using.

    The screenshot indicates 3.6 or earlier trying to open a git-based team project hosted on github.com, where the private key used for the host github.com is protected by a passphrase. OmegaT 3.6 does not support passphrase-protected private keys; either remove the passphrase or switch to HTTPS-based authentication.

    If you don't think you're using a team project, then you must be running 3.6 and have put the project somewhere inside a git repository. Place the project outside of any git repositories (there must not be a .git folder at any level up the path hierarchy from the folder).

    None of this makes sense for 4.0, which will prompt for passphrases and does allow non-team projects to be placed inside git repositories.

     

    Last edit: Aaron Madlon-Kay 2016-07-27
  • Patrick Gundlach

    You are correct, sorry. I have downloaded the 'newest' version, which is 3.6.0 update 1.

    Where can I download a newer version? I won't change my git settings.

     
  • Didier Briel

    Didier Briel - 2016-07-27
    • status: open --> closed-invalid
    • Group: 4.0 --> 3.6
     
  • Didier Briel

    Didier Briel - 2016-07-27

    I close, because this is not a bug. There are workarounds available, and the issue is fixed in 4.0.

    Didier

     
  • Patrick Gundlach

    @Didier Where can I download version 4?

     
    • Didier Briel

      Didier Briel - 2016-07-27
       
      • Patrick Gundlach

        Thank you! I'll try it out

         

Log in to post a comment.

MongoDB Logo MongoDB