ENOENT error when publishing new repository
See original GitHub issueDescription
When attempting to publish a new repository, I receive this error:
ENOENT: no such file or directory, mkdtemp 'C:\Users\[name]\AppData\Local\Temp;C:\MinGW\bin\GitHubDesktop-lfs-progress-XXXXXX'
The problem with this is that both of those directories exist and GitHub is running in administrator mode so it should be able to access those. I uninstalled GitHub and deleted all correlated files and registry keys to no avail.
Version
GitHub Desktop version: 1.0.12
OS version: Windows 6.3.9600
Steps to Reproduce
-
I wrote the code and used GitHub Desktop to create a new repository in the folder containing all of my code files.
-
I clicked the ‘Publish’ button and received this error.
-
I tried “soft” reinstalling GitHub Desktop by using Programs and Features to remove it.
-
Once this didn’t work, I reinstalled it and used Revo Uninstaller to locate all related files and registry entries, deleting every one.
-
I tried again and it still didn’t work, so I deleted the content of C:/Users/[me]/AppData/Local/Temp and double-checked the permissions to make sure it could write to it.
-
I rebooted my PC (this really should’ve been an earlier step). Still nothing.
Expected behavior: Publishing my repository without errors.
Actual behavior: Did not publish, received ENOENT instead.
Reproduces how often: 100% of the time
Logs
It appears that the log is mostly full of information about being unable to fetch my account picture (that’s happening as well), but that’s a much less important issue to me. I don’t know which pieces exactly are relevant. It can be found here for the sake of making this issue concise.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top GitHub Comments
This is a duplicate of #3072 - your
TEMP
orTMP
environment variable contains multiple paths - you should update the environment variable so it only contains one path.@piotrrybinski88 ensure you don’t have a trailing
;
on the path for both environment variables, as that seems to have been the issue here.