[Windows] bash: /dev/tty: No such a device or address #8984

Comments

cfv1984 commented Sep 29, 2015

Hi! I developed a package for atom, and when trying to publish it from windows I get this error:

After running apm publish minor from the repo I’m storing the package into.

Why is this happening?

The text was updated successfully, but these errors were encountered:

thomasjo commented Sep 29, 2015

Looks like you’re using Cygwin? Try using a normal Windows shell such as CMD or PowerShell.

cfv1984 commented Sep 29, 2015

I’m running that from cmd.exe, with git installed overriding windows tools like find and such so everything should in principle be as git wants. It’s puzzling.

gavynriebau commented Oct 1, 2015

Same problem but I worked around it by changing the git remote url to include my git username and password.

List your remote URL using:

Update the remote URL to include username and password just before github.com:

Not sure why this was necessary, I thought I’d be prompted for my credentials if git didn’t know them.

More details, hopefully relevant:

1. OS Windows 10
2. Git version is 2.6.0 from http://git-scm.com/
3. Recently done a Windows re-install

cfv1984 commented Oct 1, 2015

How does one report an issue to git itself?

50Wliu commented Oct 18, 2015

Just ran into this after updating Git to v2.6.0. I have allowed Git to be used from cmd, but not to override the default cmd commands.

robinson96 commented Nov 19, 2015

I maintain another git-wrapping tool, and my Window’s users at git 2.5 and higher are experiencing the same issue. It sounds like this might be on git’s side of things.

MaybeS commented Nov 28, 2015

i think cygwin or other bash tool interupt shell for git@sublime,

PaoloOranges commented Dec 10, 2015

I had the same error and maybe the way I fixed it could help you too.
I’m using GitExtension 2.48.05. From settings I’m using openSSH (configured via Cygwin).
I changed the following things:

• Go to Tools->Settings and in «Git»/ «Path to linux» put the bin forlder of your cygwin install
• In SSH panel, set openSSH (openSSH must be installed from Cygwin and configured to run from command line
• use ssh instead of HTTPS links. (I configured «config» file in .ssh on my home directory to use my own private rsa key )

blowsie commented Dec 18, 2015 •

Try adding this into your git config

liqiang3 commented Jan 18, 2016

it does not work

d0x2f commented Jan 26, 2016

Thanks @blowsie, worked for me.

JunaidQadirB commented Feb 17, 2016

I got this error when I changed my CygWIn home to my windows home by adding the HOME environment variable and setting it to %UserProfile%

Hiroaki-Kubota commented Feb 17, 2016

I think that install winpty may help you.
And run apm this like below:
winpty apm publish minor

AtomSetup.exe — Installation has failed #5881

Comments

garyayo commented Mar 6, 2015

I’m experiencing this error when executing AtomSetup.exe on Win 8.1 x64.

Before executing, I uninstalled my previous version of atom (182.0), deleted /AppData/Local/atom as well as /Users//.atom and cleaned the atom registries.

Anyone know what could be the issue?

The text was updated successfully, but these errors were encountered:

garyayo commented Mar 6, 2015

I was able to successfully install atom editor after running ccleaner and removing all unnecessary files.

This issue can be closed.

jcs224 commented Mar 10, 2015

I have this issue too. I ran CCleaner but no go for me. Windows 7 Pro 64-bit.

anaisbetts commented Mar 10, 2015

@jcs224 Can you hit that button and paste in the log?

jcs224 commented Mar 10, 2015

No log posted, just opens my Documents folder with nothing new in it. Should note that I am on a corporate machine with mandatory antivirus. I tried adding an exception for the installer but that didn’t seem to work either.

jcs224 commented Mar 10, 2015

@paulcbetts The installation file doesn’t work, but when I download the latest zip it works fine. Thanks for your attention on this!

Windows, after updating to atom 1.7: unable to execute. #399

Comments

underdpt commented Apr 19, 2016 •

After updating to Atom 1.7 all my builds stopped working, with the next message:

It doesn’t work with or without sh enabled, and changing que slash to «» or «/».
Also, it’s strange it states where the binaries are found, but except for the first one, the others are linux folders and I’m working on windows.

The text was updated successfully, but these errors were encountered:

noseglid commented Apr 19, 2016

The binary paths is the PATH environment variable.

Have you made sure both cmd and cwd exist and have correct access permissions?

underdpt commented Apr 19, 2016

My PATH environment isn’t related at all with the one that shows the output:

On the other hand, cmd exists but cwd not. I’m not sure cwd is a windows command anyway.

noseglid commented Apr 20, 2016

cwd is not a command, it’s the current working directory from which relative files will be resolved. If it does not exist the command cannot be execute.

The PATH is apparently different in your cmd.exe and when opening Atom (which is not uncommon). There are other issues on this project which talk about how to set the path event for an Application (such as Atom).

underdpt commented Apr 20, 2016

I’m sorry to reopen this.

This is my .atom-build.json:

As you can see, the cmd is relative to cwd , which is set to PROJECT_PATH so it should work (and was working) without touching the environment PATH :

If I set cmd to the full path of the executable, it also doesn’t works (thats the log from my first comment).

noseglid commented Apr 20, 2016 •

So where is php-win.exe located?
Is it executable?
I’m pretty sure this has nothing to do with atom-build but rather your environment. Please double-check all paths and permissions.

underdpt commented Apr 22, 2016

php-win.exe is on path: \\php-gtk2\\php-win.exe and it’s executable and readable by everyone.
The problem is not related only with this project but with any project on windows, at least for me. Projects that were working before atom being updated to 1.7, so i think that is at least related.

Anyway, I’ts working after last build package update, thanks!

underdpt commented Apr 26, 2016

Ok,
So now i find that it’s not working again. It was working just after the upgrade, but now the issue remains.
I’ll wait until the next release and check it.

noseglid commented Apr 26, 2016

I’d be willing to bet it has nothing to do with build itself but rather something that’s changing in your environment. Try and fully qualify the path to php-win.exe

underdpt commented Apr 26, 2016

Hi,
First, thanks for your patience 🙂

I already checked that, and it’s not working. I was going to recheck it now, and then it worked again. After some testing, it works (without changing the paths) if I open the project on a new window. I’m using project-ring package so I uninstalled it and the same results so it seems unrelated.

Quick resume: If I open atom and try to use any build, It doesn’t work.
If I open atom, then go to File -> New Window, and on this new window I load any project the builds works perfectly.

I’m also thinking it’s something on my environment, but it’s driving me crazy as it stopped working just after upgrading to atom1.7.

underdpt commented Apr 26, 2016

I’m now sure this has nothing to do with atom-build . Another package, atom-beautify , has the same extrange behaviour.
It seems atom/atom#11302 is related to this, so I’ll wait to the next atom release.
Thanks for your support.

I can’t install atom (windows 7): «Installation has failed: Failed to extract installer» #7915

Comments

jakedemianrosetta commented Jul 15, 2015

I downloaded the installer from the official site and when I run it, I get the error message in the title. I’ve been researching this issue and I’ve found that problem may lie in Update.exe. When I go to

I find the Update.exe file. I can open and edit all other files in this directory, but when I try to open Update.exe, I get the error:

«Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.»

But when I look at the security tab in the properties dialog of Update.exe, it shows that my account has full access.

I have no idea how to fix this issue.

The text was updated successfully, but these errors were encountered:

batjko commented Jul 15, 2015

What about the entire AppData folder? Any permission issues on that one?

Also, the access error on update.exe might not be related to the update.exe itself, but rather with what it tries to do (e.g. write to a temporary folder or something).

Do you have any temp folders or other restricted folders on your machine that are not permitted for your account (but usually are for most people)?

jakedemianrosetta commented Jul 15, 2015

Yes, I can open and edit any and all files in AppData. I don’t know the answer to the temp folder question, however. As far as I know, I don’t have any directory restrictions set up on this PC, but I could be wrong and I’m not entirely sure how to check for permissions of a folder I don’t know the name and location of.

batjko commented Jul 15, 2015

cc @paulcbetts on this one.
Not sure which part of the installer may run into this error.

anaisbetts commented Jul 15, 2015

Log file? Should be in that SquirrelTemp directory

50Wliu commented Jul 16, 2015

Also, can you try to disable any antiviruses you have when running the installer?

jakedemianrosetta commented Jul 16, 2015

@paulcbetts Not seeing a log file in thar directory. This is everything in that directory:

batjko commented Jul 16, 2015

@jakedemianrosetta Can you check this one:

jakedemianrosetta commented Jul 16, 2015

@batjko That’s the directory I was in in the image I posted.

ghost commented Jul 23, 2015

@paulcbetts So I managed to generate the SquirrelSetup.log file, by running the updater as administrator but not the setup. If I set both to run as administrator, I get caught in an infinite loop of windows asking me for permission to open AtomSetup.exe.

The log file only has one line, however:

Program: Starting Squirrel Updater:

shawmanz32na commented Aug 11, 2015

I would like to +1 this. Running the latest (1.0.5) installer fails immediately, and the only file in the

/AppData/Local/SquirrelTemp directory is an empty SquirrelSetup.log file. I’m running Windows 10 x64.

lijo-jacob commented Sep 5, 2015

I disabled my antivirus and it worked fine

FagnerMartinsBrack commented Oct 9, 2015

Maybe related to #9094?

pgcm commented Oct 12, 2015

Had the same issue on Windows 7 x64. Disabling antivirus (Mcafee) worked for me.

ms31415a16 commented Oct 20, 2015

I also have the same problem.I run installer with administrator rights but still the message «Installation has failed; Failed to extract installer» appears.

*Update: has managed to run Atom by downloading .zip windows archive instead of installer.

lisboaxd commented Feb 7, 2016

I disabled my antivirus and it also worked

panchalnv commented Feb 19, 2016

Download Atom-Windows.zip folder with this link: https://github.com/atom/atom/releases/tag/v1.5.3 Unzipped the folder Inside this folder, double click on Atom.exe to open the editor.

damieng commented Feb 24, 2016

@lisboaxd and @lijo-jacob can you let me know which antivirus product you were using that interfered?

lijo-jacob commented Feb 24, 2016

For me it was McAfee.
On Feb 24, 2016 11:40 AM, «Damien Guard» notifications@github.com wrote:

—
Reply to this email directly or view it on GitHub
#7915 (comment).

damieng commented Feb 26, 2016

Appear to be issues with McAfee and Kapersky plain flat-out blocking our installer. Not much we can do here but right now but will continue to monitor reports.

dolkee commented Mar 16, 2016

In India its netprotector which is causing the problem I excluded atom exe to start it, now its working

damieng commented Mar 16, 2016

Thanks @dolkee it’s good to know which antivirus programs are getting overprotective!

anaisbetts commented Mar 16, 2016

Appear to be issues with McAfee and Kapersky plain flat-out blocking our installer. Not much we can do here but right now but will continue to monitor reports.

We’re enlisting in the whitelist program for Slack to try to resolve this — it should carry over to all Squirrel apps

damieng commented Mar 16, 2016

That’s awesome news, thanks Paul!

On Tue, Mar 15, 2016 at 11:44 PM Paul Betts notifications@github.com
wrote:

Appear to be issues with McAfee and Kapersky plain flat-out blocking our
installer. Not much we can do here but right now but will continue to
monitor reports.

We’re enlisting in the whitelist program for Slack to try to resolve this

• it should carry over to all Squirrel apps

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#7915 (comment)

ejubkadric94 commented Mar 26, 2016

Avast antivirus blocked the installation on my windows 7..

smallx commented Apr 8, 2016

Yeah, yeah. 关掉杀毒软件就行了。

6 of 6 tasks complete

laubianchi commented Jun 8, 2016

This message error occurs because I have not enough free space on my disk C:\

RANDALUZ commented Jul 21, 2016

Good afternoon , I have not heard very well if they said the solution to the problem , but also happens ami me , and I’m desperate means , PLEASE HELP .

damieng commented Jul 21, 2016

Turn off anti virus temporarily If that doesn’t work either try portable zip version or paste contents of squirrelsetup.log

ShivaShinde commented Jul 24, 2016

Same problem, I have uninstalled my macfee, I didnt find any options, So, I kicked off 😉 Windows10 should be okay without anti-virus!!

FagnerMartinsBrack commented Jul 24, 2016 •

Guys, this issue is CLOSED. If you want to report a new issue that was not fixed by doing what was proposed above, please create a new one with proper stacktrace like #9094 and link it here if you believe it might be related.

Commenting on closed issues will make no difference since there will be no visibility and therefore the maintainers will not dedicate any effort to fix your error!

50Wliu commented Jul 24, 2016

Commenting on closed issues will make no difference since there will be no visibility and therefore the maintainers will not dedicate any effort to fix your error!

This is not true. I read all comments, including ones on closed issues. In addition, @damieng provided assistance just a bit further up, despite the issue being closed.

FagnerMartinsBrack commented Jul 24, 2016

This is not true. I read all comments, including ones on closed issues. In addition, @damieng provided assistance just a bit further up, despite the issue being closed.

Good to know that this project has enough capacity to follow closed issues, but does it really helps if someone just posts that the problem is happening and no evidence that it is the same issue? Wouldn’t be better to encourage creating a new issue with log errors so that the maintainers can analyze objectively if the problem is the same or not?

I am saying this because it just seems common sense in OSS and the contributing guidelines shows a lot of suggestions on how to create a bug report that can drive action.

50Wliu commented Jul 24, 2016 •

Wouldn’t be better to encourage creating a new issue with log errors so that the maintainers can analyze objectively if the problem is the same or not?

Yeah, I didn’t include this in my comment, but that’s generally what I do on closed issues (see for example my comments in this issue).

Edit: In this case though there’s really only two ways that the Windows installer can fail: paths are too long or an AV is stopping the installation.

FagnerMartinsBrack commented Jul 24, 2016

In this case though there’s really only two ways that the Windows installer can fail: paths are too long or an AV is stopping the installation.

Are you sure there are only two ways? Most of the time, trying to create a simple model for complexity can make us reach to conclusions that contain too many assumptions.

50Wliu commented Jul 25, 2016

Ok, >95% of the issues we receive 😉 . If someone opens up a new issue (or comments on one) about the installer and the log provided doesn’t match any of the two symptoms listed above, then of course it’s triaged further. Though this is getting off-topic now; are you a member of the Atom Slack channel? If so, I’d be happy to continue this conversation with you there! I’m @wliu on Slack.