Recursive load buffers.el

[deril]

What did you expect to happen?

Emacs loaded without any errors

What actually happened?

When emacs opens, Warnings buffer appears with the following errors after the update

Error (doom-init-ui-hook): Error running hook "+doom-dashboard-init-h" because: (error Recursive load /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el) Disable showing Disable logging
Error (doom-first-input-hook): Error running hook "ivy-mode" because: (error Recursive load /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Applications/MacPorts/Emacs.app/Contents/Resources/lisp/dired-loaddefs.el /Applications/MacPorts/Emacs.app/Contents/Frameworks/native-lisp/28_0_50-cff1cd86/dired-6a3ae2bc-061ce01a.eln /Users/deril/.emacs.d/.local/cache/eln/28_0_50-cff1cd86/counsel-eb5de957-be4e8ab1.eln) Disable showing Disable logging
Error (focus-in-hook): Error running hook "doom-auto-revert-buffers-h" because: (error Recursive load /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el /Users/deril/.emacs.d/core/autoload/buffers.el) Disable showing Disable logging
Warning (with-editor): Cannot determine a suitable Emacsclient

And emacs is not usable anymore.

Describe your attempts to resolve the issue

I tried to reinstall doom, upgrade it from the latest develop.

Steps to reproduce

1. Open Emacs
2. Observe errors

System Information

https://pastebin.com/x11tNZUn

[hlissner]

⚠️ This issue was closed and marked for deletion for the checked reasons below:

• Issue cannot be acted on or investigated further because:
  • Could not be reproduced in vanilla Doom on any of our test environments.
  • Not enough information to act on.
  • Vital information was omitted or inaccessible.
  • Explanations are too vague or issue is too open ended.
  • It's unclear what you are trying to say.
• The following possibilities are more likely explanations and haven't been ruled out:
  • A pilot error.
  • Private configuration.
  • A third-party package is behaving correctly, but in a manner you're not expecting.
  • A corrupt or broken Emacs installation.
  • Your system environment (hardware issues, the OS, shell environment, missing system dependencies, etc).

This ruling is not absolute and can be reversed if you follow up with enough information to further investigate this issue. Our How to Debug Issues guide can help you find out more about it (note: our discourse currently requires an account).

If you still feel lost after reading our debugging guide, raise your issue on our Discord or Discourse -- there may be others who have experienced it. Otherwise, this issue will be automatically deleted after 14 days.

---

I apologize if this is inconvenient or you feel lost, but it takes a lot of time to review issues by myself. The complexity and extensibility of Emacs tends to produce a lot of false positive or open ended bug reports, so I've restricted our issue tracker to issues that are actionable, immediately reproducible in vanilla Doom, or can be investigated in a reasonable amount of time.

[deril]

Dear @hlissner
I have tried different approaches:
Reinstalled emacs, use vanilla doom config.

As I debugged, git bisect says, that everything get broken in commit e431dbc13860afb5b700c5f409716b28d3c2b4c0

Might be that the issue only with emacs 28. It was installed from macports:
port install emacs-app-devel +nativecomp

[hlissner]

Two of my macOS (Catalina) test systems run 28.0.50 and 28.0.60, one with and one without native-comp -- both installed from Homebrew. I also use 28+native-comp myself (but on Linux) and can't reproduce the issue there either. I can only suspect there is an issue with the macports source of Emacs. Try installing it from homebrew instead.

[telotortium]

Hi @deril, I encountered the same issues with Macports emacs-app-devel @20210928_0+imagemagick+nativecomp+rsvg. I had to switch back to the previous build:

port activate emacs-app-devel @20210727_0+imagemagick+nativecomp+rsvg

and then Emacs started working again. Perhaps MacPorts pulled a bad version of Emacs 28.0.60 this time.

[telotortium]

Also filed this on the MacPorts side: https://trac.macports.org/ticket/63651

[catap]

@hlissner both of this complains was related to some snapshot of master branch of emacs in macports (see -devel ports).

It is quite possible that it is another side effect of #5469 which leads to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50534 — since upstream fixed it, I had a few crashes which was reported as https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50641

In few days (or a bit longer) I will take a deep look to this issue. Maybe today evening.

Anyway, I'd love to ask confirmation of @telotortium and @deril that they tired to run doom purge or similar command to remove all native compiled files.

I had a few very wired bugs, when used native compiled files from another version.

The second question: have you recompiled all native compiled files after downgrade to old emacs? I'm asking because if you haven't cleaned up it, it probably reused it from doom version which was used before upgrade, and some mix which leads to missed commit that pointed @telotortium can easy occur.

[catap]

Well, I've upgraded used version of doom emacs from 4549b27 to faceb8c via doom up and can confirm appears of an issue.

doom build doesn't help, you may ignore this step.

Anyway, emacs crashed one more time which I've reported to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50641

[catap]

Upgrade to emac's commit 5f5189e9be6c70c4db99e8057287d16955b9c620 fixed an issue on my side. I've opened pull request macports/macports-ports#12629

[telotortium]

macports/macports-ports#12629 merged