Open hcientist opened 9 years ago
Most likely an issue with afloat and not EasySIMBL although it would certainly be reasonable for EasySIMBL to blacklist itself by default to prevent something like this happening.
If you just need to regain access to things, you might to look in /Library/ScriptingAdditions
or ~/Library/ScriptingAdditions
and delete the scripting additions. Also you can look in /Library/Application Support/SIMBL/Plugins
or ~/Library/Application Support/SIMBL/Plugins
and delete the plugins.
At some point i crashed a browser (possibly unrelated?) and then finder became unresponsive, so i relaunched it. It was again unresponsive. I rebooted, it was unresponsive... (many hours and a trip to a tech shop), then i deleted easysimbl.app from /applications and it was fine (i tried to follow the uninstall instructions, but any app i opened became immediately unresponsive during the whole ordeal, so i could not un-check use SIMBL) i was on
osx 10.10.3
. I hadEasySIMBL-1.7.1
with afloat