Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CLOSED] All extension installations fail (WinXP) #6298

Open
core-ai-bot opened this issue Aug 30, 2021 · 21 comments
Open

[CLOSED] All extension installations fail (WinXP) #6298

core-ai-bot opened this issue Aug 30, 2021 · 21 comments

Comments

@core-ai-bot
Copy link
Member

Issue by frgc
Friday Feb 21, 2014 at 03:06 GMT
Originally opened as adobe/brackets#6951

WinXP SP3
sprint 36 experimental build 0.36.0-11506 (release 942505c3a)

"Installation failed.
Unknown internal error."

Using extension manager this is what I get immediately upon trying to install an extension. There is no network activity. There is no antivirus and I tried unblocking brackets in windows firewall.
@core-ai-bot
Copy link
Member Author

Comment by dangoor
Friday Feb 21, 2014 at 13:35 GMT

Medium priority to me to investigate.

@core-ai-bot
Copy link
Member Author

Comment by dangoor
Friday Feb 21, 2014 at 13:36 GMT

@frgc Is there anything in the console (select Show Developer Tools from the Debug menu)?

@core-ai-bot
Copy link
Member Author

Comment by damouk
Friday Feb 21, 2014 at 15:29 GMT

I have the same problem - and the same set up (WinXP Sp3, sprint 36) (I'm using this through a proxy, but Sprint 35 worked fine).

This is the only line output in Developer tools:
"Unknown installation error extensionManager domain is undefined"

@core-ai-bot
Copy link
Member Author

Comment by frgc
Saturday Feb 22, 2014 at 02:46 GMT

Same, from Dev Tools

Unknown installation error extensionManager domain is undefined
/extensibility/Package.js:367

@core-ai-bot
Copy link
Member Author

Comment by dangoor
Tuesday Feb 25, 2014 at 20:49 GMT

@bchintx Is it possible that Node fails to start up on WinXP sp3 with the new binary module for file watching?

@core-ai-bot
Copy link
Member Author

Comment by bchintx
Wednesday Feb 26, 2014 at 17:24 GMT

@dangoor Ug. Something's definitely not working right. If I delete the installed 'fswatch_win.node' file, then launch Brackets and try to install an extension, the installation succeeds.

@core-ai-bot
Copy link
Member Author

Comment by Diex
Wednesday Feb 26, 2014 at 20:16 GMT

same behavior here... after deleting 'fswatch_win.node' file, installation succeeds.

@core-ai-bot
Copy link
Member Author

Comment by bchintx
Thursday Feb 27, 2014 at 17:03 GMT

Updating title to reflect that this is Windows XP-specific.

@core-ai-bot
Copy link
Member Author

Comment by njx
Thursday Feb 27, 2014 at 21:54 GMT

Marking for sprint 37

@core-ai-bot
Copy link
Member Author

Comment by le717
Tuesday Mar 04, 2014 at 14:21 GMT

There is an old XP tower sitting in the floor of the other room, perhaps I can get a chance to set up and try this out myself sometime this week.

@core-ai-bot
Copy link
Member Author

Comment by bchintx
Saturday Mar 08, 2014 at 00:50 GMT

@JeffryBooher fixed this issue by disabling the native file watching node module on XP. See PR #7131

@core-ai-bot
Copy link
Member Author

Comment by telis93
Saturday Mar 08, 2014 at 20:38 GMT

I am experiencing this issue in Windows 7 and developer tools fail to start and when I click Debug -> Restart Node I get a js alert saying "Failed to restart node: Cannot call method 'restartNode' of undefined"

@core-ai-bot
Copy link
Member Author

Comment by dangoor
Monday Mar 10, 2014 at 13:55 GMT

@telis93 Your issue is likely a different problem. Please file a new issue.

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Tuesday Mar 11, 2014 at 17:24 GMT

Removing FBNC tag since we've decided we want to use a slightly different fix for XP -- one that doesn't cause #6551 to reappear, but that disables watchers & caching (so XP will just behave like Sprint 35).

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Wednesday Mar 12, 2014 at 01:19 GMT

New fix ongoing in PR #7170

@core-ai-bot
Copy link
Member Author

Comment by peterflynn
Wednesday Mar 12, 2014 at 06:43 GMT

Setting back to FBNC so we can test tomorrow. We should also spin off a bug about getting watchers working in XP (ideally via@bchintx's native extension still).

@core-ai-bot
Copy link
Member Author

Comment by gillisig
Friday Mar 14, 2014 at 11:16 GMT

I am getting the same issue in windows 7. Dev tools displays the same as the others:

Unknown installation error extensionManager domain is undefined /extensibility/Package.js:367

@core-ai-bot
Copy link
Member Author

Comment by bchintx
Friday Mar 14, 2014 at 17:21 GMT

Created new Issue #7200 to track fixing native file watching on Windows XP.

@gillisig The extensionManager domain error is probably a new problem. Can you please file a new issue for this? Thanks.

Closing this issue as fixed with@JeffryBooher 's now-merged pull request.

@core-ai-bot
Copy link
Member Author

Comment by mcmanimie
Tuesday Oct 21, 2014 at 22:39 GMT

I'm seeing this issue also on Mac 10.9 running v44. I can't install any extensions.

"Unknown installation error extensionManager domain is undefined"

@core-ai-bot
Copy link
Member Author

Comment by redmunds
Tuesday Oct 21, 2014 at 22:56 GMT

@mcmanimie Please open a New Issue.

@core-ai-bot
Copy link
Member Author

Comment by mcmanimie
Wednesday Oct 22, 2014 at 02:19 GMT

@redmunds My bad. Here you go: adobe/brackets#9625

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@core-ai-bot