guix.el icon indicating copy to clipboard operation
guix.el copied to clipboard

guix-system-from-file fails

Open FrozenPigs opened this issue 5 years ago • 3 comments

When I use guix-system-from-file on my system config it fails, I used (setq debug-on-error t) to get the backtrace below:

Debugger entered--Lisp error: (wrong-type-argument markerp nil)
  marker-position(nil)
  geiser-repl--narrow-to-prompt()
  geiser-repl--wrap-unfontify-region-function(1 419)
  font-lock-unfontify-region(1 419)
  font-lock-default-unfontify-buffer()
  font-lock-unfontify-buffer()
  font-lock-mode-internal(nil)
  font-lock-default-function(nil)
  font-lock-mode(-1)
  font-lock-change-mode()
  kill-all-local-variables()
  comint-mode()
  geiser-repl-mode()
  guix-start-repl(#<buffer *Guix Internal REPL*> "/tmp/emacs-guix-WyITVu/repl-socket")
  guix-start-repl-maybe(internal)
  guix-start-process-maybe()
  guix-get-repl-buffer(internal)
  guix-eval-read("(system-sexps 'from-file '(\"/home/wednesday/.guix-packages/wed/system/pc.scm\") '(file number-of-packages number-of-services kernel bootloader firmware initrd-modules))")
  guix-system-get-entries(from-file ("/home/wednesday/.guix-packages/wed/system/pc.scm") (file number-of-packages number-of-services kernel bootloader firmware initrd-modules))
  guix-system-info-get-entries(from-file "/home/wednesday/.guix-packages/wed/system/pc.scm")
  apply(guix-system-info-get-entries (from-file "/home/wednesday/.guix-packages/wed/system/pc.scm"))
  bui-get-entries(guix-system info (from-file "/home/wednesday/.guix-packages/wed/system/pc.scm"))
  bui-get-display-entries(guix-system info (from-file "/home/wednesday/.guix-packages/wed/system/pc.scm"))
  guix-system-get-display(from-file "/home/wednesday/.guix-packages/wed/system/pc.scm")
  guix-system-from-file("/home/wednesday/.guix-packages/wed/system/pc.scm")
  funcall-interactively(guix-system-from-file "/home/wednesday/.guix-packages/wed/system/pc.scm")
  call-interactively(guix-system-from-file)
  magit-invoke-popup-action(121)
  funcall-interactively(magit-invoke-popup-action 121)
  call-interactively(magit-invoke-popup-action nil nil)
  command-execute(magit-invoke-popup-action)

By looking at it, this could end in a problem with guiser but since it stems from guix I brought the issue here.

FrozenPigs avatar Apr 09 '19 12:04 FrozenPigs

Hello and sorry for the long delay :blush:

What happens, if you simply run Geiser (M-x run-guile) or if you run some other Emacs-Guix command (for example, M-x guix-installed-packages)? I mean do you have any errors?

alezost avatar Apr 24 '19 07:04 alezost

I can use geiser fine, same with most all of the emacs.el commands, the only ones that I remember having problems are the 3 that use the system config.

FrozenPigs avatar Apr 24 '19 09:04 FrozenPigs

Hm, did you install emacs-guix with Guix? If so, maybe you didn't update it for some time, so it may not be in sync with the current Guix.

Recently another strange problem was reported on mailing list, and Ludovic rightly guessed that it happened because of the Guix ABI change: https://lists.gnu.org/archive/html/help-guix/2019-04/msg00075.html

So, could you please reinstall Emacs-Guix (with guix package -u emacs-guix) and check if the error stays.

Oh, also please make sure that guix system build builds your config successfully.

alezost avatar Apr 27 '19 19:04 alezost