I'm on opensuse tumbleweed, and today after updating my packages, I can't use emacs. Anyone have any ideas how to troubleshoot this?
❯ emacs -Q
Loading loadup.el (source)...
Dump mode: nil
Using load-path (/usr/share/emacs/29.1/lisp /usr/share/emacs/29.1/lisp/emacs-lisp /usr/share/emacs/29.1/lisp/progmodes /usr/share/emacs/29.1/lisp/language /usr/share/emacs/29.1/lisp/international /usr/share/emacs/29.1/lisp/textmodes /usr/share/emacs/29.1/lisp/vc)
Loading emacs-lisp/debug-early...
Symbol's function definition is void: file-name-sans-extension
I started by checking
emacs --version
and confirming that it reported 29.1. The file atwhich emacs
(/usr/bin/emacs
) is not a symlink, it's a bash script that was ultimately runningemacs-gtk
, which is a binary in the same directory.If I run emacs-gtk directly, things appear to work, but I get this warning:
This appears to be related to screen reader support. My repos do have packages for at-spi, but I don't reckon that hiding a warning I might see once per reboot is a strong enough reason to install it.
If I run
emacs-x11
directly, things seem to work, though if I turn on menu-bar-mode or check the menu with F10 it looks awful.If I set and export EMACS_TOOLKIT to x11 and run the bash script, it seems to take longer to load and spams hundreds of lines in the shell as it announces that it's loading things. I'm not that bothered by long loading times as I'm seldom restarting, but I don't know why it's so spammy when I start it through the script.
I'd like to better understand what's going on. For now, I think I have a working setup again if I just skip the script and run emacs-gtk directly, but I'm sure there's something wrong with my setup, and I hate not knowing things. I'll include the bash script in a reply to myself here.
According to the other thread and a Mastodon post the package is broken.
As a side note for me Emacs is just too important to leave to the distribution, I always build my own.
Yeah... I may have to do the same. I had plans this weekend that this slowed down. Thanks for your help. I hadn't seen the other thread or the mastodon post.