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

Spacemacs fails to start with error "Symbol's value as variable is void: \213" #19

Open
Zlopez opened this issue Jul 9, 2019 · 6 comments · Fixed by #26
Open

Spacemacs fails to start with error "Symbol's value as variable is void: \213" #19

Zlopez opened this issue Jul 9, 2019 · 6 comments · Fixed by #26

Comments

@Zlopez
Copy link

Zlopez commented Jul 9, 2019

Hi,

I tried to use spacemacs with flatpak emacs and if I switch to develop branch, which is recommended, I'm hitting this issue:

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

Symbol's value as variable is void: \213

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.

This could be related to syl20bnr/spacemacs#11585. According to discussion this issue is about missing gnutls. I looked at freedesktop.Sdk runtime and it looks like gnutls is not part of this runtime.

@Zlopez
Copy link
Author

Zlopez commented Aug 15, 2019

I was able to install spacemacs from develop branch using workaround from syl20bnr/spacemacs#12535, but I'm still hitting the issue.

Spacemacs is working in standard emacs 26.2 installed from rpm package on Fedora 30 Silverblue, so this looks like flatpak only issue.

philn added a commit to philn/org.gnu.emacs that referenced this issue May 24, 2020
This is a requirement for the spacemacs develop branch.
See also: syl20bnr/spacemacs#11585
Fixes flathub#19
@muep muep closed this as completed in #26 May 24, 2020
muep pushed a commit that referenced this issue May 24, 2020
This is a requirement for the spacemacs develop branch.
See also: syl20bnr/spacemacs#11585
Fixes #19
@philn
Copy link
Contributor

philn commented May 25, 2020

OK I apologize but I think this should be reopened. Today I installed the emacs flatpak update containing the commit from #26 and got the symbol value error again.
As this happens when emacs checks for updates on ELPA, the error isn't raised at every startup... I'd need to force Emacs to always look for updates so I can reliably reproduce the issue...

@muep muep reopened this May 25, 2020
@muep
Copy link
Collaborator

muep commented May 25, 2020

Thank you for investigating the issue.

I do not have time to look at this much right now, but what I'd expect to do if I had time, would be to try to do a connection from some bit of elisp, similarly to but separately from what the failing program does. Then if there is a wider problem e.g. with TLS support missing, it should be easy to experiment with different potential solutions.

@stradicat
Copy link

Can confirm, the issue is still present; the snap equivalent does not exhibit this behaviour.

When installed in Elementary OS 6, and given all filesystem access permissions to both system libraries and home folder, the message Symbol's value as variable is void: \213 still pops up, and initialization stops.

@stradicat
Copy link

More information on the issue here:
syl20bnr/spacemacs#11585

Could it be a Spacemacs-specific bug, or does it happen to everybody else using a vanilla or self-cobbled configuration?

@LeifAndersen
Copy link

I think this is beecause flatpak is on emacs 28, while spacemacs seems to only work on 27. If you revert to version 27.2 of emacs, it works fine:

flatpak update --commit=84827e2ccdedc3e31516319d91c6a12ff8f1a6dcc048e76dee9d123c8fb229f1 org.gnu.emacs

Note that:

  1. the aspell program still doesn't work, (can't find any dictionaries) so you won't get spell check unless you manually add some, and
  2. You will need root to run this command, as well as constantly making sure not to upgrade emacs to the latest version until spacemacs works with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants