total terminal does not launch anymore on the public beta of el capitan
ChristianSch opened this issue · 8 comments
… though it worked with the first developer preview. See below for console output (this very message is being repeated every two seconds).
/edit: 1.5.4 installed via homebrew
cerberus:~ nexus$ brew cask info totalterminal
totalterminal: 1.5.4
TotalTerminal
http://totalterminal.binaryage.com
/opt/homebrew-cask/Caskroom/totalterminal/1.5.4 (28 files, 4.3M)
https://github.com/caskroom/homebrew-cask/blob/master/Casks/totalterminal.rb
==> Contents
TotalTerminal.pkg (pkg)
+1, I have the same issue here.
+1 , here there are more comments but not any solution: http://discuss.binaryage.com/t/totalterminal-fails-to-start-in-el-capitan-public-beta/3958
Same issue as well, can't install it anymore.
Trying this with the El Capitan GM candidate, the same error shows in the logs. Hopefully they'll be able to address this issue by the time the official release comes around.
Well, probably not. The problem (it seems) demands a substantial change to the architecture and the way tt works, and the developers seem really inactive and uninterested in the project lately (»There is probably no need to stick with TotalTerminal anymore. Thank you for using Visor/TotalTerminal over the years. It is time to switch.«) I myself have adopted iterm 2 for now. It sucks quite a lot, but there seems to be no alternative (yet).
You can of course, reboot into recovery mode (cmd-r on mac start), pick Terminal from the Utilities menu once booted, and type: csrutil disable then reboot your mac and it starts working again. Though you do lose the benefit of System Integrity Protection features in 10.11. Do so at your own risk, and all other such disclaimers.
+1. The issue is with the new “System Integrity Protection” (SIP), but there is a workaround to disable it. Hopefully someone (more competent than myself) will manage a new major fork of totalterminal...
Hi All,
I can confirm that disabling SIP does allow Total Terminal to work again. If you're really reliant on it, that's probably the only path to keep it working on El Cap.