Error on fresh install: Wrong type argument: stringp, nil

[lucassmagal]

Hello,

I've just installed Prelude after installing Emacs and, whenever I try to install some package (say solarized-theme), I get the error on the title.

Running emacs --debug-init this is what I see:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
      file-name-nondirectory(nil)
      rainbow-turn-on()
      rainbow-mode(1)
      prelude-emacs-lisp-mode-defaults()
      run-hooks(prelude-emacs-lisp-mode-hook)
      (lambda nil (run-hooks (quote prelude-emacs-lisp-mode-hook)))()
      run-hooks(change-major-mode-after-body-hook prog-mode-hook emacs-lisp-mode-hook)
      apply(run-hooks (change-major-mode-after-body-hook prog-mode-hook emacs-lisp-mode-hook))
      run-mode-hooks(emacs-lisp-mode-hook)
      emacs-lisp-mode()
      autoload-find-file("ruby-end-pkg.el")
      byte-code("\306\211\211\211\307\306\310�!\306\311�!\306\211������0�1�2�3�4�5r \206(  ** THIS LINE IS PRETTY BIG **
      autoload-generate-file-autoloads("ruby-end-pkg.el" nil "/home/lsmagalhaes/.emacs.d/elpa/ruby-end-20130426.909/ruby-end-autoloads.el")
      update-directory-autoloads("/home/lsmagalhaes/.emacs.d/elpa/ruby-end-20130426.909")
      package-generate-autoloads("ruby-end" "/home/lsmagalhaes/.emacs.d/elpa/ruby-end-20130426.909")
      package--make-autoloads-and-compile("ruby-end" "/home/lsmagalhaes/.emacs.d/elpa/ruby-end-20130426.909")
      package-unpack(ruby-end "20130426.909")
      package-download-tar(ruby-end "20130426.909")
      package-download-transaction((ruby-end))
      package-install(ruby-end)
      mapc(package-install (ruby-end))
      prelude-ensure-module-deps((ruby-tools inf-ruby yari ruby-end))
      eval-buffer(#<buffer  *load*<3>> nil "/home/lsmagalhaes/.emacs.d/modules/prelude-ruby.el" nil t)  ; Reading at buffer position 1244
      load-with-code-conversion("/home/lsmagalhaes/.emacs.d/modules/prelude-ruby.el" "/home/lsmagalhaes/.emacs.d/modules/prelude-ruby.el" nil t)
      require(prelude-ruby)
      eval-buffer(#<buffer  *load*<2>> nil "/home/lsmagalhaes/.emacs.d/prelude-modules.el" nil t)  ; Reading at buffer position 553
      load-with-code-conversion("/home/lsmagalhaes/.emacs.d/prelude-modules.el" "/home/lsmagalhaes/.emacs.d/prelude-modules.el" nil nil)
      load("/home/lsmagalhaes/.emacs.d/prelude-modules.el")
      (progn (load prelude-modules-file))
      (if (file-exists-p prelude-modules-file) (progn (load prelude-modules-file)))
      (when (file-exists-p prelude-modules-file) (load prelude-modules-file))
      eval-buffer(#<buffer  *load*> nil "/home/lsmagalhaes/.emacs.d/init.el" nil t)  ; Reading at buffer position 3807
      load-with-code-conversion("/home/lsmagalhaes/.emacs.d/init.el" "/home/lsmagalhaes/.emacs.d/init.el" t t)
      load("/home/lsmagalhaes/.emacs.d/init" t t)
      #[0 "�\205\262  ** BIG LINE AGAIN **
      command-line()
      normal-top-level()

These are my configfiles: https://gist.github.com/lucassmagal/5588943

This is the second computer I see this bug - the same bug. I'm running a Ubuntu 13.04, and before was fedora 16.

[daenney]

Same error but for me debug says:

Debugger entered--Lisp error: (file-error "Cannot open load file" "package")
  require(package)
  eval-buffer(#<buffer  *load*<2>> nil "/Users/daenney/.emacs.d/core/prelude-packages.el" nil t)  ; Reading at buffer position 1204
  load-with-code-conversion("/Users/daenney/.emacs.d/core/prelude-packages.el" "/Users/daenney/.emacs.d/core/prelude-packages.el" nil t)
  require(prelude-packages)
  eval-buffer(#<buffer  *load*> nil "/Users/daenney/.emacs.d/init.el" nil t)  ; Reading at buffer position 3397
  load-with-code-conversion("/Users/daenney/.emacs.d/init.el" "/Users/daenney/.emacs.d/init.el" t t)
  load("/Users/daenney/.emacs.d/init" t t)
  #[nil "^H\205\276^@   \306=\203^Q^@\307^H\310Q\202A^@ \311=\2033^@\312\307\313\314#\203#^@\315\202A^@\312\307\313\316#\203/^@\317\202A^@\$
  command-line()
  normal-top-level()

I haven't configured anything yet, it's a completely fresh install.

[bbatsov]

@lucassmagal Looks like this is an upstream bug in the Zenburn theme.

[daenney]

@bbatsov Any idea where mine is coming from? Or is that the same issue?

[bbatsov]

Update in half an hour the zenburn package and the problem should go away.

[daenney]

It works for me now.

[lucassmagal]

It works, thank you!