File error: Cannot open load file, No such file or directory, bind-map

[achikin]

Description :octocat:

Freshly installed spacemacs does not work because of init.el error

Reproduction guide :beetle:

• git clone the repo
• Start Emacs

Observed behaviour: :eyes: :broken_heart:

Warning (initialization): An error occurred while loading ‘/Users/achikin/.emacs.d/init.el’:

File error: Cannot open load file, No such file or directory, bind-map

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the ‘--debug-init’ option to view a complete error backtrace.

Expected behaviour: :heart: :smile: Emacs starts without errors

Backtrace :paw_prints:

Warning (initialization): An error occurred while loading ‘/Users/achikin/.emacs.d/init.el’:

File error: Cannot open load file, No such file or directory, bind-map

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the ‘--debug-init’ option to view a complete error backtrace.

[rebcabin]

I have exactly the same issue. Brand-new Windows machine, fresh installation of Emacs 25 from gnu headquarters, fresh git clone of spacemacs, all this stuff always works on the mac, where I have been using spacemacs for more than a year. I went through the debugging step, Found that the init.el file is empty. No clear way to resolve the problem.

[achikin]

It looks like some melpa outage. I've retried half an hour later and everything worked as intended.

[rebcabin]

Still have the problem a day later. Run as Admin or not, Master branch or develop branch. Fresh .spacemacs file or custom .spacemacs file.

[dancar]

👆 Same here :-\

[fokoepxg]

Same here. Cant install spacemacs. Exact same error described above

Edit: Fixed it by increaseing the time out for elpa, as packages were not installed(including bind-map).

the relevant setting in .spacemacs :- dotspacemacs-elpa-timeout 30

[JAremko]

Sometimes Melpa can lag for days :disappointed:

I hope it's all ok now?

[grarl1]

For me it is solved after using:

emacs --insecure

[achikin]

No further issues.

[azer]

This issue is still happening for me, makes it impossible to open Emacs. How did others solve the problem ?

[rebcabin]

it just went away for me after a few days, so I assumed it was melpa lag, but didn't prove so.

[Bost]

@guillermoruizalv emacs --insecure helps indeed. @achikin The --insecure switch bothers me a lot. IMO we should be able to run emacs securely(!). I propose to reopen this issue.

Edit: I found out in my case the proxy is the culprit. So until I find the proper solution I keep on alternating between emacs --insecure and:

(setq
 url-proxy-services ;; TODO use (getenv "proxy")
 ;; must NOT contain "http://", "https://"
 '(("http"     . "<proxy-machine>:<port>")
   ("https"    . "<proxy-machine>:<port>")))

[sahilshekhawat]

Facing the same error, don't think using emacs --insecure is a fix. Please reopen the issue.

[rdjack21]

Just did a clean install today and have the same issue. while emacs --insecure did allow the install to finish I really don't like that we have to do that to get things to work.

[paldepind]

I was trying to install Spacemacs and I experience the same issue. Running Emacs with --insecure doesn't help.

[ShingoFukuyama]

Thanks to @fokoepxg, dotspacemacs-elpa-timeout 300 in .spacemacs works for me!

[gcperrin]

Still an issue as of 9/27 -- fresh install on Debian 9 (headless), Emacs 25. The standalone emacs build works fine.

[benbot]

Still happening today, maybe first run should be insecure by default?

[theamazingcase]

Fresh install, same issue on MacOS 10.12.6. Having never used emacs before, this is a rather daunting introduction, and I'm hesitant to use the --insecure flag...

[ashleylester]

Happening on Windows 10 with fresh install of Emacs emacs-25.3_1-x86_64. Adding dotspacemacs-elpa-timeout 300 doesn't work.

[simendsjo]

I get a similar error: File error: Cannot open load file, No such file or directory, up-core. I've tried increasing the timeout, using both develop and master, and running emacs --insecure on both combinations without any luck.

EDIT: Looks like #9951 might be the same as my issue.

[vitorbaptista]

Just in case others have this error, make sure you delete your .emacs.d folder and clone spacemacs again, as the issue with up-core was caused by a bug in a package that might still be in your local cache.

[duianto]

The up-core issue was caused by use-package, but it has been fixed. Here's the Spacemacs issue that related to it: File error: Cannot open load file, No such file or directory, up-core #9948

When it happened, then one solution was to use the melpa stable version (the instructions are in that issue).

Now it's enough to just delete the use-package-<timestamp> folder from .emacs.d/elpa/ (on the develop branch it's in: .emacs.d/elpa/<emacs version>/develop/). Then restart Emacs and it will download the latest version.

[loxs]

I had the same problem. Nothing of the aforementioned (both here and in the referenced bug) helped. I nuked my whole .emacs.d/ and that didn't help as well. Finally I ended up fixing it like this:

M-x install-package RET use-package

I waited for the package to install, then restarted emacs with --insecure and finally that helped spacemacs to pull in all required packages, compile them etc.

[vclvm]

CentOS, emacs 25.3.1 built from sources, same problem, solved by M-x install-package RET use-package (thanks @loxs!) --insecure option is not needed

[joaocenoura]

I was hitting the same issue (File error: Cannot open load file, No such file or directory, bind-map) when updated spacemacs to develop branch + emacs 25. After deleted my old ~/.spacemacs and restart emacs it fetched packages from melpa successfully.

[JosXa]

Same issue as OP on Windows 8 and Windows 10. --insecure option has no effect.

[tuliogrodrigues]

I had the same problem because the proxy server was not allowed to connect through https. To solve the problem, in my .spacemacs file I changed the bellow configuration

from dotspacemacs-elpa-https t to dotspacemacs-elpa-https nil

[ghost]

Because .spacemacs dones't exist, so just:

cp ~/.emacs.d/core/templates/.spacemacs.template ~/.spacemacs

Then mkdir layers in .spacemacs.d fold Everything will be fine

[kowodo]

for me solution was commenting out in my init.el following line: ;;(require 'diminish) ;; if you use :diminish

[jkrasnay]

For me, the problem was that Emacs was complaining about an insecure Lets Encrypt token from melpa. By setting dotspacemacs-elpa-timeout 300 I was able to see the error and tell it to proceed.

[gsunjka]

I had the same issue. Seems like Emacs for Windows doesn't support TLS out of the box. I downloaded emacs-25-x86_64-deps.zip from http://ftp.gnu.org/gnu/emacs/windows/ and extracted it over my existing emacs folders. Afterwards everything worked fine.

[pauljamesharper]

I am getting this same error on Debian Stretch. 0.200.13@27.0.50 (spacemacs) emacs-snapshot --version GNU Emacs 27.0.50

None of the fixes above work. Increased the timeout in .spacemacs :- dotspacemacs-elpa-timeout 300

[azer]

I'm also experiencing this error.

[tkodyl]

Hello, I had the same issue like @achikin. I have Fedora 27 and emacs from its repo (1:25.3-3.fc27), fresh spacemacs repo checkout. Increasing timeout didnt help, running emacs with option -insecure caused packages fetch. I am not sure whether it matters but I am behind proxy. So far it seems to work correct. We will see In next package update time. But emacs --insecure seems to be poor solution. Doesnt it need ticket reopen?

[thepulkitagarwal]

On a fresh install, I got this issue when I chose vim mode + helm. I did a complete reinstall with emacs mode + ivy, and this issue was not there.

[groundedsage]

I'm confused as to how this is still an issue and that I am spending hours trying to find a solution.

[groundedsage]

Following this seemed to do the trick. http://sourabhbajaj.com/mac-setup/Emacs/ Though it concerns me that you have to turn off security to get everything to run.

[eedahl]

Same problem

[saint-shark]

I have the same issue. OS: Manjaro 17.1.10 Emacs version: 26.1 Spacemacs version: 0.200.13

[1-riverfish]

I met the same question and solved it by changing the timeout from 30 to 300.

[damon98xp]

My Solution to this problem:

(setq package-user-dir "C:\My_ELPA_DIR")
(package-initialize)

After applying the code above, the error message "File mode specification error" disappears.

[tuliogrodrigues]

@damon98xp Thanks a lot. Now I can start my emacs again.

[dg01d]

same problem for me, on a mac. Nothing at all is loaded as a result, so I do not get a spacemacs.

This is nonsensical.

[csdrane]

I, also, am experiencing this problem.

[togakangaroo]

Happening for me when trying to trigger projectile on a brand new emacs/spacemacs install on a brand new instance of the windows 10 ubuntu subsystem

[Rizary]

windows 10 cloning fresh spacemacs all the above solution cannot work

[finomayato]

Deleting elpa folder my problem has been resolved - rm -rf .emacs.d/elpa/. emacs --insecure finished with success after that

[KraevRoot]

still have this problem

[isaaczhou]

Why is this issue closed? Still got this error

[ghost]

still have this problem on a fresh spacemacs installation. Why is this issue closed ?