This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I tried to connect through Terminal (Experimental) action to my Gentoo server and the connection finished with this message in terminal: java.util.MissingResourceException: bin/nativeexecution/Linux-unknown/pty After creating folder Linux-unknown in the ${nb_install}/ide/bin/nativeexecution/ and copy the content of the Linux-x86 it start to work. Starting with flags : -J-Dcnd.remote.logger.level=0 -J-Dnativeexecution.support.logger.level=0 I got these output in console: FINEST [nativeexecution.support.logger]: JSCH: Connecting to kremilek.klamovka.cz port 1234 FINEST [nativeexecution.support.logger]: JSCH: Connection established FINEST [nativeexecution.support.logger]: JSCH: Remote version string: SSH-2.0-OpenSSH_3.9p1 FINEST [nativeexecution.support.logger]: JSCH: Local version string: SSH-2.0-JSCH-0.1.41 FINEST [nativeexecution.support.logger]: JSCH: CheckCiphers: aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,arcfour,arcfour128,arcfour256 FINEST [nativeexecution.support.logger]: JSCH: aes256-ctr is not available. FINEST [nativeexecution.support.logger]: JSCH: aes192-ctr is not available. FINEST [nativeexecution.support.logger]: JSCH: aes256-cbc is not available. FINEST [nativeexecution.support.logger]: JSCH: aes192-cbc is not available. FINEST [nativeexecution.support.logger]: JSCH: arcfour256 is not available. FINEST [nativeexecution.support.logger]: JSCH: SSH_MSG_KEXINIT sent FINEST [nativeexecution.support.logger]: JSCH: SSH_MSG_KEXINIT received FINEST [nativeexecution.support.logger]: JSCH: kex: server->client aes128-ctr hmac-md5 none FINEST [nativeexecution.support.logger]: JSCH: kex: client->server aes128-ctr hmac-md5 none FINEST [nativeexecution.support.logger]: JSCH: SSH_MSG_KEXDH_INIT sent FINEST [nativeexecution.support.logger]: JSCH: expecting SSH_MSG_KEXDH_REPLY FINEST [nativeexecution.support.logger]: JSCH: ssh_rsa_verify: signature true FINEST [nativeexecution.support.logger]: JSCH: Host 'kremilek.klamovka.cz' is known and mathces the RSA host key FINEST [nativeexecution.support.logger]: JSCH: SSH_MSG_NEWKEYS sent FINEST [nativeexecution.support.logger]: JSCH: SSH_MSG_NEWKEYS received FINEST [nativeexecution.support.logger]: JSCH: SSH_MSG_SERVICE_REQUEST sent FINEST [nativeexecution.support.logger]: JSCH: SSH_MSG_SERVICE_ACCEPT received FINEST [nativeexecution.support.logger]: JSCH: Authentications that can continue: publickey,keyboard-interactive,password FINEST [nativeexecution.support.logger]: JSCH: Next authentication method: publickey FINEST [nativeexecution.support.logger]: JSCH: Authentication succeeded (publickey). FINE [nativeexecution.support.logger]: New connection established: pert@kremilek.klamovka.cz:1234 - Linux-Gentoo FINEST [nativeexecution.support.logger]: pert@kremilek.klamovka.cz:1234 /bin/sh: State changed: INITIAL -> STARTING INFO [nativeexecution.support.logger]: Error occurred: java.io.IOException: java.util.MissingResourceException: bin/nativeexecution/Linux-unknown/pty FINEST [nativeexecution.support.logger]: pert@kremilek.klamovka.cz:1234 /bin/sh: State changed: STARTING -> ERROR pert@kremilek.klamovka.cz:1234 /bin/sh:0[STARTING] pert@kremilek.klamovka.cz:1234 /bin/sh:0[ERROR]
this is really bad if our fallback is looking not in Linux-x86, but in Linux-unknown
Most likely the issue is gone after fixing issue 186503 (changeset is http://hg.netbeans.org/cnd-main/rev/272cdc06fedb) As to falling back to x86, I don't thing it's right thing to do just to consider we are on x86 when we really don't know the CPU type. What should be better here is error processing - an error message like "Unsupported CPU type" or "Can not determine CPU type" should be displayed instead of MissingResourceException.
Please report on progress, especially if you can make it into 6.9.1, if not please consider removing 6.9.1_CANDIDATE keyword. Thanks, -R
It works in trunk build 20100621
Petr, please check that the bug is fixed now in trunk.
Removing the 6.9.1_CANDIDATE keyword as this issue does not seem to meet basic qualification criteria (has its own changeset). It's more or less a duplicate or a subissue of already ported issue 186503. If you want to nominate it again, please provide original changeset.