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.

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

fail to finish fresh installation #6648

Closed
phinicota opened this issue Jul 21, 2016 · 4 comments
Closed

fail to finish fresh installation #6648

phinicota opened this issue Jul 21, 2016 · 4 comments
Labels
- Bug tracker - stale marked as a stale issue/pr (usually by a bot)

Comments

@phinicota
Copy link

phinicota commented Jul 21, 2016

Description

I am not able to finish spacemacs installation (completely fresh).
Might be worth mentioning:

  • I'm behind a corporate proxy (got my http_proxy and https_proxy variabels in environment)
  • Already tried the --insecure fix and the ssh/dns fix.
  • It doesn't seem to be completely frozen: If I C-g whilte it's stuck, I'm in a working state missing keybindings and configurations.

Reproduction guide

1- Install Emacs from some source
2- Obtain spacemacs (tried cloning and zip file)
3- Run Emacs (tried ---insecure too)
4- Choose vim mode and any option (base or recommended install)

Observed behaviour:

FIRST LAUNCH
first_launch

AFTER FIRST LAUNCH
second_launch

--debug-init OUTPUT
second_launch_debug_init

System Info

I am running:
Debian Jessie
GNU Emacs 24.4.1 (although tried also 24.5.1 from debian testing)
spacemacs-base-0.105.21

Backtrace

Where it hangs on first launch:
installing package: ws-butler@spacemacs-base...

Successive launches (as seen in images):
Loading HOME/.emacs.d/layers/+lang/emacs-lisp/packages.el (source)... done
--debug-init output:
(Spacemacs) -> init (spacemacs-base)

@a13ph
Copy link

a13ph commented Jul 21, 2016

@phinicota I had this issue for around two days and I still don't know for sure how I've solved it or how to reproduce it.

My weak guesses:

  • Some bad config file/directory existence was overlooked
  • Environment variables were causing trouble (via exec-path-from-shell maybe), which is why when I had success it was running emacs from [funny enough, 3 layers of] ranger
  • Compiled elisp leftovers were messing me up between my tries of emacs 24 and 25 (though I doubt that's the case)

Since my success translated easily to my pretty heavy config, and between different versions of spacemacs, it's probably not a branch thing either.

@phinicota
Copy link
Author

I somehow doubt it could be environment variables, I'm running almost (as far as we can tell) the same installation as a collegue.

The only grand difference we can find is we have different proxy/dns assigned. This ssh/dns fix seemed like it could work... could it be missing something? Is there a way I could confirm dns is messing up?

@phinicota
Copy link
Author

To update on this, I haven't found a solution, but I've tried running it from terminal and emacs -nw seems to be working fine. Same with emacs --daemon and emacsclient -nc afterwards. Any clues?

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- Bug tracker - stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

3 participants