core-ai-bot
commented
3 years ago 
The same to LinuxMint 17(KDE),but all right at Ubuntu 14.04 32bit
Open core-ai-bot opened 3 years ago
core-ai-bot
commented
3 years ago
The same to LinuxMint 17(KDE),but all right at Ubuntu 14.04 32bit
core-ai-bot
commented
3 years ago 
@mcmanimie Do you have any extensions installed? It could be the case that an extension has messed up the nodejs instance that's running (Brackets uses node for extension installation).
core-ai-bot
commented
3 years ago 
As noted, in my testing I deleted all my extensions and even trashed the Brackets folder under Application support, rebooted, then reinstalled. No dice.
One thing that could be an issue is that at one point I installed (and then uninstalled) Adobe Edge Code.
core-ai-bot
commented
3 years ago
Ahh, sorry, I missed the disabling of extensions.
The installation/removal of Edge Code should not have an impact on this.
Were there any other errors in the dev tools? ("File watchers went offline!", perhaps?)
core-ai-bot
commented
3 years ago 
Me too having the same issue with Brackets v0.45 and Mac OSX 10.9. I started using Brackets yesterday, and couldn't install any of the extensions. Console logs the error "Unknown installation error extensionManager domain is undefined", and nothing else. Tried dragging a zip file to the specified location, but produced the same error on console.
core-ai-bot
commented
3 years ago
@dangoor There were no other errors I could discern.
FWIW - I was able to install (most) plugins manually (Beautify failed, as did the Extension Ranker).
core-ai-bot
commented
3 years ago
@mcmanimie Thanks for all of the troubleshooting you've been doing on this.
It sounds to me like there's no reason that the Brackets-node process would be having trouble, which leads me back to this from your original description:
I've ensured that brackets was included in the firewall exceptions list
In Brackets, Node runs in a separate process (Brackets-node). That process listens on a random port (at least, I think it's random). On my machine right now, I see it listening on 56560. If Brackets-node is unable to listen on that port or Brackets is unable to connect to that port, then you'd see an error of the sort you're seeing.
Assuming you're using the standard OS X Firewall, make sure you've allowed Brackets-node to accept incoming connections. I'm guessing that's what you did based on the quote above, but I wanted to double check because that's the best explanation I have for what you're seeing.
core-ai-bot
commented
3 years ago
@dangoor - I have the Brackets.app selected to allow incoming connections, yes. And, since the brackets-node process sits within the Brackets.app package I assumed it inherited the firewall exception. I don't see a way to drill down into the package to select the brackets-node process specifically.
core-ai-bot
commented
3 years ago
@mcmanimie Are you using the standard OS X Firewall? Brackets-node needs to be specifically authorized in the System Preferences. (Security & Privacy > Firewall > Firewall Options...). I've highlighted the necessary setting in the screenshot below:
core-ai-bot
commented
3 years ago
@dangoor How do I select Brackets-node though? As I said, it sits in the Brackets.app bundle (at least for me) and the Add button doesn't allow me to drill down into the Brackets.app package to select it.
core-ai-bot
commented
3 years ago
For me, as soon as I started up the firewall, there was a prompt asking me whether I should allow Brackets-node to accept incoming connections.
Ahh, I see a difference. I was running from master and not a release. I just fired up a release build and did not get prompted at all. That's probably because of the "Automatically allow signed software..." setting. Do you have that turned on?
core-ai-bot
commented
3 years ago core-ai-bot
commented
3 years ago
Ha, well, it's magically working all of a sudden. I literally have no idea why. I made no substantive changes to my computer in the past week short of rebooting a few times.
core-ai-bot
commented
3 years ago
Hmm... That is mighty odd. I'll go ahead and close this now, then. Reopen it if it stops working again. (Also note that if you do ever run Brackets from a git clone you may need to update the firewall permissions)
core-ai-bot
commented
3 years ago 
It broke for me. Steps that led to it borking:
core-ai-bot
commented
3 years ago 
I think I have the same issue on Mint 17. I even did a purge and deleted the .config/Brackets directory. As soon as I use Brackets 1.1, extension installation is broken. I got the following log:
Download the React DevTools for a better development experience: http://fb.me/react-devtools /thirdparty/react.js:4356 NodeSocketTransport - start /LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:87 Unknown installation error extensionManager domain is undefined /extensibility/Package.js:408
is there anything I could try to investigate further?
I was able to pop dev tools and the error is:
"Unknown installation error extensionManager domain is undefined"
I've ensured that brackets was included in the firewall exceptions list, moved all extensions into the disabled folder, and even deleted the entire Brackets directory and reinstalled. No dice.