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

Emacs gets stuck on "Indexing layers..." during boot. #14720

Closed
Martinsos opened this issue Apr 27, 2021 · 6 comments
Closed

Emacs gets stuck on "Indexing layers..." during boot. #14720

Martinsos opened this issue Apr 27, 2021 · 6 comments
Labels
stale marked as a stale issue/pr (usually by a bot) To be reproduced

Comments

@Martinsos
Copy link
Contributor

Description :octocat:

Forever stuck during boot, on "Indexing layers...".

Reproduction guide 🪲

  • Start Emacs, and ~ 1 out of 20 times this will happen.

Observed behaviour: 👀 💔
When it gets stuck, I quit re-enter emacs couple of times and then it is ok again.
I also reinstalled emacs completely and it didn't help.
I also installed it on fresh machine for the first time, and again the same problem.
This has been happening for some time now (months, maybe even a year, not sure).

Expected behaviour: ❤️ 😄
It should not get stuck.

System Info 💻

  • OS: gnu/linux (Archlinux)
  • Emacs: 27.2
  • Spacemacs: 0.300.0
  • Spacemacs branch: develop (rev. 4262e01)
  • Graphic display: t
  • Distribution: spacemacs
  • Editing style: vim
  • Completion: helm
  • Layers:
(python windows-scripts vimscript meson ruby docker terraform emoji
        auto-completion better-defaults emacs-lisp git
        (haskell :variables haskell-completion-backend 'dante dante-tap-type-time 1 haskell-indentation-layout-offset 4 haskell-indentation-starter-offset 4 haskell-indentation-left-offset 4 haskell-indentation-where-pre-offset 2 haskell-indentation-where-post-offset 2)
        helm html
        (javascript :variables js2-mode-show-strict-warnings nil js2-basic-offset 2 js-indent-level 2)
        lsp markdown multiple-cursors org
        (shell :variables shell-default-height 30 shell-default-position 'bottom)
        (syntax-checking :variables syntax-checking-enable-tooltips nil flycheck-display-errors-function #'flycheck-display-error-messages-unless-error-list)
        treemacs version-control yaml cmake)
  • System configuration features: XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB NOTIFY INOTIFY ACL GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD JSON PDUMPER LCMS2 GMP
@lebensterben
Copy link
Contributor

I haven't encounter this problem myself. Need more report from community.

In the meantime consider to run Emacs in a daemon.

@Martinsos
Copy link
Contributor Author

I found this one under closed issues #8941 , however it ends up with an ask for possibly re-opening the issue due to the proposed solution not being completely effective.

I had problems running emacs in a daemon so I am keen into investing some more time into trying to fixing this before giving that a go again.

Do you have any suggestion on how to possibly debug this, or what to look into? Why is this "indexing of layers" step and what could be the potential problem here?

@lebensterben
Copy link
Contributor

lebensterben commented Apr 28, 2021

If you mean you cannot run Emacs client as --fg-daemon, just run it as --daemon.

To start debugging, search "indexing of layers" in the source.

(spacemacs-buffer/set-mode-line "Indexing layers..." t)

Then randomly add some (kill-emacs) to figure out where it actually hangs. If it quit, the site of (kill-emacs) is before what cause it to hang. If it hang, the cause of hanging is after the last (kill-emacs) you inserted.

@ksjogo
Copy link
Contributor

ksjogo commented Jun 24, 2021

Also started running into this with layers apparently not being loaded, will have a look.

@alexriabtsev
Copy link

I'm getting the same error when fullscreen mode is enabled.

@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 Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale marked as a stale issue/pr (usually by a bot) To be reproduced
Projects
None yet
Development

No branches or pull requests

4 participants