https://bugzilla.redhat.com/show_bug.cgi?id=1313394

Mat Booth mat.booth@redhat.com changed:

What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED

--- Comment #1 from Mat Booth mat.booth@redhat.com --- Yep, I can reproduce this with the following steps:

$ su - # mkdir -p /var/svn/repos # svnadmin create /var/svn/repos/test # chown -R :wheel /var/svn/repos # chmod -R 775 /var/svn/repos # svnserve -t --foreground --listen-host localhost -r /var/svn/repos

And then the following works:

$ svn co svn+ssh://mbooth@localhost/var/svn/repos/test

But Subclipse hangs, as described above. It appears to be stuck in the native portion of javahl:

"ModalContext" #72 prio=6 os_prio=0 tid=0x00007fe2b2584800 nid=0x463c runnable [0x00007fe1fe7a7000] java.lang.Thread.State: RUNNABLE at org.apache.subversion.javahl.SVNClient.info(Native Method) at org.apache.subversion.javahl.SVNClient.info2(SVNClient.java:797) at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getInfo(AbstractJhlClientAdapter.java:2144) at org.tigris.subversion.svnclientadapter.AbstractClientAdapter.getInfo(AbstractClientAdapter.java:310) at org.tigris.subversion.subclipse.core.repo.SVNRepositoryLocation.validateConnection(SVNRepositoryLocation.java:325) at org.tigris.subversion.subclipse.ui.wizards.NewLocationWizard$1.run(NewLocationWizard.java:127) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)

https://bugzilla.redhat.com/show_bug.cgi?id=1313394

lejeczek peljasz@yahoo.co.uk changed:

What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(peljasz@yahoo.co. | |uk) |

--- Comment #3 from lejeczek peljasz@yahoo.co.uk --- I wonder if it has something to do with the fact that user account does not exist on the remote system - this would happen because one committed a typo or even more commonly did not put itsme@ as part of URL and Eclipse filled in local session's username which does not exist on remote box. If this is the problem then it's fundamental test case, which Eclipse/subversion should be able to handle .... or, there is no way a ssh client can know if that account exists on remote box and it's only the operator who deserves punishment?

https://bugzilla.redhat.com/show_bug.cgi?id=1313394

--- Comment #5 from Fedora End Of Life jkurik@fedoraproject.org --- This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.

https://bugzilla.redhat.com/show_bug.cgi?id=1313394

--- Comment #7 from Fedora End Of Life jkurik@fedoraproject.org --- This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.

https://bugzilla.redhat.com/show_bug.cgi?id=1313394

--- Comment #9 from Ben Cotton bcotton@redhat.com --- This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.