After my recent upgrade (per new install) to Ubuntu 18.04, I have started having quite some troubles with my tool chain (Emacs, Lualatex, Evince). I am using forward/backward search to approximate WYSIWYG LaTeX editing.
Evince has started to crash on recompiling/updating LuaLaTeX. Then I tried zathura (another PDF viewer) instead, and after a view tries, similar crashes happen with zathura as well. Zathura after a while cannot even be started anymore by the commands Emacs issues to control zathura.
I am using Ubuntu 18.04 and the corresponding emacs, evince, and zathura packages as well as some "standard" emacs extensions from the ubuntu package repository.
The relevant portion of my .emacs:
(package-initialize)
(add-to-list 'load-path "~/.emacs.d/lisp/")
(add-hook 'text-mode-hook 'electric-pair-mode)
(add-hook 'text-mode-hook 'show-paren-mode)
(add-hook 'text-mode-hook 'turn-on-auto-fill)
(add-hook 'TeX-mode-hook 'outline-minor-mode)
(setq TeX-auto-save t)
(setq TeX-parse-self t)
(setq-default TeX-master nil)
(add-hook 'LaTeX-mode-hook 'flyspell-mode)
(add-hook 'LaTeX-mode-hook 'LaTeX-math-mode)
(add-hook 'LaTeX-mode-hook 'turn-on-reftex)
(setq reftex-plug-into-AUCTeX t)
(add-hook 'LaTeX-mode-hook 'company-mode)
(add-hook 'LaTeX-mode-hook 'TeX-source-correlate-mode)
(setq TeX-source-correlate-method 'synctex)
(setq TeX-source-correlate-start-server t)
(add-hook 'LaTeX-mode-hook 'TeX-PDF-mode)
(setq TeX-view-program-selection '((output-pdf "Zathura")))
Emacs generates the following call:
zathura file.pdf --synctex-forward 200:0:sometexinclude.tex -x "emacsclient
+%{line} %{input}"
Called like this, zathura (I do not use a zathura config file) exhibits the following:
zsh: segmentation fault (core dumped) zathura file.pdf
--synctex-forward 200:0:sometexinclude.tex -x
Evince also crashes with SIGSEGV which leads me to believe that is a problem independent of the viewers.
The last thing I found out is that taking away the synctex.gz file makes it possible to start zathura and view the pdf output. But this is of course no desirable solution. However, I was not able to quickly find out how to find the core dump and make it human readable in this case. (That might exceed the scope of my problem.)
A description of that issue occurring with large documents in an OS X setting is described here: For me, it also happens more often the longer (60+ pages) the documents are, however, in my case under Linux.
Hope to get some help? (Should I transfer/share this question to/with the emacs community?)