Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 367722

Summary: NPE in EGitSecureStore.calcNodePath while fetching
Product: [Technology] EGit Reporter: Stefan Liebig <Stefan.Liebig>
Component: UIAssignee: Project Inbox <egit.ui-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: curtis.windatt.public, tomasz.zarna
Version: 1.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Stefan Liebig CLA 2012-01-03 02:05:16 EST 
While performing a "fetch" the following NPE occurs:

java.lang.NullPointerException
	at org.eclipse.egit.core.securestorage.EGitSecureStore.calcNodePath(EGitSecureStore.java:86)
	at org.eclipse.egit.core.securestorage.EGitSecureStore.clearCredentials(EGitSecureStore.java:107)
	at org.eclipse.egit.ui.internal.credentials.EGitCredentialsProvider.reset(EGitCredentialsProvider.java:142)
	at org.eclipse.jgit.transport.JschConfigSessionFactory.getSession(JschConfigSessionFactory.java:124)
	at org.eclipse.jgit.transport.SshTransport.getSession(SshTransport.java:121)
	at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.<init>(TransportGitSsh.java:248)
	at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:147)
	at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:127)
	at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:113)
	at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1062)
	at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:129)
	at org.eclipse.egit.core.op.FetchOperation.run(FetchOperation.java:128)
	at org.eclipse.egit.ui.internal.fetch.FetchOperationUI.execute(FetchOperationUI.java:99)
	at org.eclipse.egit.ui.internal.fetch.FetchOperationUI$1.run(FetchOperationUI.java:117)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Stefan Liebig CLA 2012-01-03 07:49:42 EST 
Found the reason:
The preference >> Network Connections >> SSH2 >> SSH2 Home
was wrong.

However, the error message does not give a hint what the cause could be.
Comment 2 Curtis Windatt CLA 2012-01-30 14:36:12 EST 
Saw this while creating a new remote.  Looking for duplicates, it looks like this is fixed for 1.3.

*** This bug has been marked as a duplicate of bug 366389 ***