iTerm2 2.9.20160510 and i2cssh failure

[Mike Brudenell]

Hi!

I'm using iTerm2 2.9.20160510 along with wouterdebie's i2cssh running on OS X 10.11.4 (15E65) …

i2cssh is a Ruby gem that gets iTerm2 to open a new window split into multiple panes, each connecting to a different host. By turning on File> Broadcast Input you can then type commands to all the host windows simultaneously. I don't use this often, but it's extremely useful when I need it.

Unfortunately something has now broken: possibly due to one of the recent iTerm2 updates or possible an OS X update. when I try to use i2cssh now to open sessions to multiple hosts it gives me this error:

/Library/Ruby/Gems/2.0.0/gems/rb-scpt-1.0.1/lib/rb-scpt.rb:542:in `_send_command': CommandError (Appscript::CommandError)

OSERROR: -1719

MESSAGE: Access for assistive devices is disabled.

OFFENDING OBJECT: app("/System/Library/CoreServices/System Events.app").processes["iTerm2"].menu_bars[1]

COMMAND: app("/System/Library/CoreServices/System Events.app").processes["iTerm2"].menu_bars[1].menu_bar_items["Window"].menus["Window"].menu_items["Select Split Pane"].menus["Select Split Pane"].menu_items["Select Pane Above"].click()

from /Library/Ruby/Gems/2.0.0/gems/rb-scpt-1.0.1/lib/rb-scpt.rb:642:in `method_missing'

from /Library/Ruby/Gems/2.0.0/gems/i2cssh-2.0.0/lib/i2cssh.rb:102:in `block (2 levels) in split_session'

from /Library/Ruby/Gems/2.0.0/gems/i2cssh-2.0.0/lib/i2cssh.rb:101:in `upto'

from /Library/Ruby/Gems/2.0.0/gems/i2cssh-2.0.0/lib/i2cssh.rb:101:in `block in split_session'

from /Library/Ruby/Gems/2.0.0/gems/i2cssh-2.0.0/lib/i2cssh.rb:100:in `upto'

from /Library/Ruby/Gems/2.0.0/gems/i2cssh-2.0.0/lib/i2cssh.rb:100:in `split_session'

from /Library/Ruby/Gems/2.0.0/gems/i2cssh-2.0.0/lib/i2cssh.rb:25:in `initialize'

from /Library/Ruby/Gems/2.0.0/gems/i2cssh-2.0.0/bin/i2cssh:298:in `new'

from /Library/Ruby/Gems/2.0.0/gems/i2cssh-2.0.0/bin/i2cssh:298:in `<top (required)>'

from /usr/local/bin/i2cssh:23:in `load'

from /usr/local/bin/i2cssh:23:in `<main>'

A key thing is the message "Access for assistive devices is disabled". However:

• iTerm2 isn't prompting me to enable assistive access, and
• Systems Preferences > Security & Privacy > Accessibility isn't letting me add iTerm2 to the list of applications permitted to control the Mac. (Trying to add it using the "+" button or dragging the application into the list doesn't add it and produces no warning/error: it just has no effect. And yes, I've unlocked the padlock in the Systems Preferences panel. :-)

I've tried deleting the iTerm2 application and restoring older 2.9 series versions from my Time machine backups, but these still have the same problem. This suggests it's not iTerm2 per se, but perhaps an OS X update that's gone by since I last used i2cssh?

I did read somewhere that accessibility permissions had changed/been tightened up in El Capitan 10.11: I think saying that settings from earlier versions of OS X were't being carried forward and applications would need to be re-authorised the first time they tried to use the assistive API (or something akin to this). However I've been running 10.11 since it's launch and have definitely used i2cssh since.

Does anyone have any ideas, please?

Cheers,

Mike B-)

[George Nachman]

Hm, I wonder if ruby needs to be added to the list of apps permitted to use accessibility?

--
You received this message because you are subscribed to the Google Groups "iterm2-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iterm2-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mike Brudenell]

I should have thought: "Turn it off and on again…"

I was vaguely uneasy on the list of applications allowed to control the Mac being empty but couldn't place why. Today, after rebooting the Mac, the list is now populated again (and includes iTerm2) and i2cssh is working again. No, I've not changed anything else: honest!

I'm going to risk applying the latest OS X update shortly which will involve another reboot, so I'll see what state things are in after that.

Cheers,

Mike B-)