csshX throwing an error in OSX 10.7
When running csshX v0.73-169 with any number of server addresses to connect to,
it throws the error:
Can't call method "qualifiedSpecifier" on unblessed reference at
/usr/local/bin/csshX line 519.
An example command:
csshX web1.example.com:1234 web2.example.com:1234 web3.example.com:1234
Looking at the code, it seems like this is an undocumented API endpoint that
may or may not have changed in Lion.
Running csshX without arguments (so it shows the help) doesn't throw the error.
Original issue reported on code.google.com by [email protected] on 26 Jul 2011 at 8:03
I'm having a really hard time reproducing this - tried two different lion
machines - both work for me with the same csshX version.
There must be something different between our environments or OS installs.
The error is not actually on the line 519 (with the magic call), it's actually
the $tabobj which is undefined, which means the doScript_in_() did not return
correctly. That call is a documented one.
Things to think about:
* OS install - do you have a fresh install (new machine) or a 10.6 upgraded to 10.7 (mine are both upgrades)
* Do you have anything special in the .csshrc
* Do you have any software like SIMBL plugins that might be messing with the OS calls
* Does csshx -d web1.example.com:1234 give any more detailed logs
Would be interested if you can think of anything else unusual about your setup.
.. Gavin
Original comment by gavin.brock on 4 Aug 2011 at 6:47
Did you manage to resolve this? Or do you have any more info? Thanks!
Original comment by gavin.brock on 16 Aug 2011 at 7:34
Hey sorry... I haven't had a chance to fully resolve this yet, but it does work
on my Mac Mini, just not my laptop. I'll let you know if I find anything.
Original comment by [email protected] on 16 Aug 2011 at 2:27
The reason for me of setting such error was the configuration of
.ssh/known_hosts file. I've use
ssh-keygen -R {server.name.com}
for servers and problem is gone.
Original comment by artyom.rozumenko on 14 Dec 2011 at 12:13
@artyom: Interesting - maybe, due to the invalid remote host identity, the ssh
client exits too fast, and csshX doesn't have time to get a hold of the
terminal. Thanks for the hint.
Original comment by gavin.brock on 14 Dec 2011 at 6:16
Same issue appeared on 10.14 Mojave beta, nothing solve it. Clean install same error:
Banyar-MacBook-Air:~ banyartibor$ csshx host1 host2 Can't call method "qualifiedSpecifier" on unblessed reference at /usr/local/bin/csshx line 524.
same issue
Yesterday was working, today I have no idea why I got this issue.
The result when execute whit the '-d' option is below:
$ csshX -d prod
Host: prod
Can't call method "qualifiedSpecifier" on unblessed reference at /usr/local/bin/csshX line 524. at (eval 28) line 1.
main::__ANON__('Can\'t call method "qualifiedSpecifier" on unblessed referenc...') called at /usr/local/bin/csshX line 524
CsshX::Window::open_window('CsshX::Window::Master', '/usr/local/bin/csshX', '--master', '--sock', '/var/tmp/tmp.0.pfmwvq', '--launchpid', 59958, '--screen', 0, ...) called at /usr/local/bin/csshX line 1158
CsshX::Launcher::new('CsshX::Launcher') called at /usr/local/bin/csshX line 2083
I also have tried removing all entries at the ~/.ssh/known_host file and still not work.
I also have tried to first connect by normal ssh to the machines in order to get the updated reference into the ~/.ssh/known_host file and also get the same error with the csshX command:
$ csshX prodall Can't call method "qualifiedSpecifier" on unblessed reference at /usr/local/bin/csshX line 524.
Laptop macbook pro with macos sierra 10.12.5 The csshX verision installed with brew is 0.74
$ csshX -v
csshX 0.74
After a complete reboot of the machine, it start working properly again. I have rolled back the changes to ~/.csshrc and ~/.ssh/known_host and also everything continues working as expected. BR,
For anyone who is wondering, it looks like the author used an undocumented call to find the window position. I strongly suspect this has been removed in Mojave. Here is the thread where he talks about finding it: https://stackoverflow.com/questions/2712655/how-do-i-get-the-window-id-and-tab-number-of-a-terminal-window-using-applescript
We're probably out of luck, unless someone who knows Objective-C can fix it.