cfr once asked and answered the following question:   In short: every run of xindy/texindy on an actual file (not the help menu) does end with something like  /usr/local/texlive/2017/bin/x86_64-linux/xindy.run: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory   The problem is that the given solution does not work anymore nowadays. Running an up-to-date TeX Live 2017 (vanilla) and Arch Linux x64 with access to AUR I tried to use the packages given in the answer. Unfortunately both cannot be validated and even skipping the signature check does not help.  Probably it could work compiling xindy manually against another library, but where are the official sources with version 2.5.1 (or newer)?  Or is there maybe another way of getting xindy to work on a "modern" OS?  Update: I've tried to compile the ancient sources from 2010 from  (CVS) where any essential binaries and code files are from 1996 (no luck). And the xindy home page talks about xindy 2.2 being a release candidate, although TeX Live 2017 ships with xindy 2.5.1.  Update 2: As @DavidCarlisle showed in the chat the usual behavior would be  $ xindy --version xindy release: 2.5.1 xindy script version: 1.18 xindy kernel version: 3.0 CLISP version 2.49.50 (2017-03-19) (built on desktop-new [192.168.1.4])     architecture: X86_64   Because of the missing library the kernel version and the clisp version do not even show up.
121204
My GNU/Linux system (Arch) now has libncurses.so.6 rather than libncurses.so.5. But I have upstream's vanilla TeX Live (fully updated) and xindy wants libncurses.so.5:    xindy --version   produces the following error  xindy release: 2.5.1 xindy script version: 1.18 /usr/local/texlive/bin/xindy.run: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory   And ldd can confirm the problem:  ldd /usr/local/texlive/bin/xindy.run    gives      linux-vdso.so.1 (0x00007ffc07997000)     libm.so.6 =&gt; /usr/lib/libm.so.6 (0x00007fab4d1b1000)     libcrypt.so.1 =&gt; /usr/lib/libcrypt.so.1 (0x00007fab4cf79000)     libncurses.so.5 =&gt; not found     libdl.so.2 =&gt; /usr/lib/libdl.so.2 (0x00007fab4cd75000)     libc.so.6 =&gt; /usr/lib/libc.so.6 (0x00007fab4c9d1000)     /lib64/ld-linux-x86-64.so.2 (0x00007fab4d4af000)   How can I use xindy without changing my operating system, while using vanilla TeX Live?  2 strategies have occurred to me:   compile xindy from sources against libncurses.so.6; compile and install libncurses.so.5 alongside libncurses.so.6.   Option (2) can be dodgy or can be fine, depending on the details. My suspicion is it may be dodgy for this library, simply because no packages are available for the old version of the library, which might mean there are problems having both installed. Moreover, since everything else is compiled against the new version, I'm not sure whether this would be enough for xindy anyway.  Option (1) I have no idea about. I don't know if this is even vaguely doable or, in fact, where the sources are or what might be required to compile them. (I don't suppose there's any chance a pre-compiled binary is available somewhere? But that is probably hoping for too much ;).)  What is the most practicable approach?
13458
Texstudio doesn't work for me anymore after updating to Mac OS X 10.11 El Capitan. I have the latest version of TexStudio installed (2.10.2). As pointed out by , this is due to a change in the places OS X allows files to be saved. When I started TexStudio, I received a message "PDFLatex could not be launched". In the settings, I had to change the folder of the compiler from user/texbin/ to /Library/Tex/texbin, as shown in the screenshot below:    Can anybody tell me if I have to make further changes in order to make TexStudio fully working (bibliography and the like), and if yes, which?   I hope TexStudio are very soon going to release an update (there is an issue for this on their issue queue.  Thank you for your help. This is my first post here, so please apologize any imprecisions.
114516
This question led to a new package:      How can I display the full path of the tex file that I compile? It is a simple file, no include or input present.  Edit: I use MiKTeX 2.9 on a Windows 7 64-bit.  Less demanding: If not possible, then I will be satisfied with a partial path (at least one or two folders up + the filename).
102977
I'd like to know which are the essential differences between makeindex and xindy (or texindy) in this sense:   What things can we do with xindy that we can not do with makeindex? or vice versa. What is the primary use of each one of them? Syntactic differences between their style files. (.ist vs .xdy)
112131
When typing either of the commands nautilus . or xdg-open . into terminal, they execute correctly, but with a warning:  Nautilus-Share-Message: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory)   As I say, it opens the file manager correctly and I can detect no further problems. There are several instances of users experiencing this message in other questions , but each of the questions either addresses a side-issue I'm not experiencing, or simply goes unanswered.    What does this message mean, and can I do anything to prevent it?
103148
A couple weeks ago I didn't have any issue when using Bibtex on a document where the different parts were included with \include commands, but today I updated Miktex, and now it seems not to work anymore. Now when I compile the main document I get an error message that says  I couldn't open auxiliary file section.aux ---line 3 of file test.aux : @input{section.aux : } I'm skipping whatever remains of this command  Here's a minimal (non)working example : my main file &quot;test.tex&quot; is just \documentclass{article} \usepackage[utf8]{inputenc} \usepackage[T1]{fontenc} \usepackage[english]{babel} \begin{document} \include{section} \bibliography{reference} \bibliographystyle{plain} \end{document}  where the file &quot;section.tex&quot; is just \section{My section} I need to test the citations, so see \cite{A}.  and the file &quot;reference.bib&quot; just contains one reference. It works like a charm if I add the section directly or if I \input it, but with \include it just gives the error message as above. I tried with different editors (Texniccenter, Texmaker, Texstudio and Texworks) and it seemed to have the same issue each time. What is causing this problem ? P.S. I've looked at an old version of my document that used to work, and I've noticed a difference in the .aux files : the old version has, near the beginning, a line \bbl@cs{beforestart}  whereas in the newer versions it seems that this line has become \@nameuse{bbl@beforestart}  I'm not sure it's related or if it makes any sense, but I thought I'd add it in case it made a difference.
66199
I am trying to make a glossary list using xindy in TexStudio. I have already installed Perl but it does not work. Here is my MWE  \documentclass[a4paper,openright,12pt]{book} \usepackage{vmargin} \usepackage{fancyhdr} \usepackage{emptypage} \usepackage{xpatch} \usepackage{float} \fancypagestyle{plain}{\renewcommand{\headrulewidth}{0.5pt} \renewcommand{\footrulewidth}{0.5pt}} \pagestyle{fancy}  \usepackage{afterpage} \usepackage{blindtext} \fancypagestyle{chapterfirstpage}{% \renewcommand{\headrulewidth}{0pt}% \renewcommand{\footrulewidth}{0.5pt}% \fancyhf{}% \rfoot{\thepage}% } \xpatchcmd{\chapter}{\thispagestyle{plain}}{\thispagestyle{chapterfirstpage}}{\typeout{Success}}{\typeout{Failed}}   \usepackage{epigraph}  \newcommand\blankpage{% \null \thispagestyle{empty}% \addtocounter{page}{-1}% \newpage} \usepackage[utf8]{inputenc} \setcounter{secnumdepth}{3}  \setcounter{tocdepth}{3}  \usepackage[spanish, es-tabla]{babel}  \usepackage{graphicx}  \graphicspath{{./figuras/}} \usepackage{setspace} \usepackage[backend=bibtex,bibencoding=ascii,style=chem-angew,citestyle=numeric-comp,sorting=none,]{biblatex}  \addbibresource{biblio}   \usepackage{csquotes}  \usepackage{titlesec}  \usepackage{tocloft}  \usepackage{tabu}  \usepackage{color}  \usepackage{epsfig}\usepackage{multirow}  \usepackage{colortbl}  \usepackage[table]{xcolor}  \titleformat{\chapter}{\normalfont\huge\sffamily}{\thechapter.}{0.1em}{\Huge}  \renewcommand\cftchapaftersnum{.}  \makeindex  \usepackage[labelfont=bf]{caption}  \usepackage{bm}  \usepackage{textcomp}  \usepackage{upgreek}  \usepackage[xindy]{glossaries}  \GlsSetXdyCodePage{duden-utf8}  \usepackage{translator}  \setacronymstyle{long-sc-short} \makeglossaries  \newacronym{DRX}{DRX}{Difracción de Rayos X}  \raggedbottom  \definecolor{lightgray}{gray}{0.9}  \begin{document}  \printglossary[letter]  \end{document}   I get the following error:  Warning: File 'acronyms prueba.glo' is empty. Have you used any entries defined in glossary 'main'? Remember to use package option 'nomain' if you don't want to use the main glossary.   Thanks!
36877
Ubuntu Software instantly crashes as I try to open it. Tried to access from terminal and gives the following error:  (ubuntu-software:5523): Gs-WARNING **: failed to open plugin /usr/lib/gs-plugins-9/libgs_plugin_xdg_app_reviews.so: /usr/lib/gs-plugins-9/libgs_plugin_xdg_app_reviews.so: cannot open shared object file: No such file or directory
87384
After having updated to Mac OS X El Capitan (10.11), I'm no more able to compile using either TexMaker or TexShop. This is the message I get from TexShop  "/usr/texbin/pdflatex does not exist. TeXShop is  a front end for TeX, but you also need a TeX distribution. Perhaps such a distribution was not installed or was removed during a system upgrade. If so, go to  and follow the instructions to (re)install MacTeX. A less likely possibility is that a tool path is incorrectly configured in TeXShop preferences. This can happen if you are using the macports or fink distributions."  I tried to change the path in Preferences-Engine, as many suggested. Yet, it doesn't work either. Any help?
75193
After upgrading to Ubuntu 14.04 LTS, I find the Unity destkop in vnc4server never works as it did under Ubuntu 12.04 LTS.  Here is my ~/.vnc/xstartup for vnc4server:  #!/bin/sh  xrdb $HOME/.Xresources xsetroot -solid grey  /usr/bin/gnome-session &amp;   That works fine starting Unity desktop on Ubuntu 12.04 LTS, but unfortunately on 14.04 LTS only a gray screen is seen in vncviewer.  I searched a little and find  shows the way to start legacy gnome desktop (gnome-fallback) in vnc on 14.04, but what I want is the solution for a normal Unity desktop in vnc.  Has anyone successfully run Unity desktop in a vnc session (vnc4server, or any other vnc server) on Ubuntu 14.04 LTS?
115596
This code:  \documentclass[11pt,openright]{book} \usepackage[T1]{fontenc} \usepackage[latin9]{inputenc} \usepackage[british]{babel}  \usepackage{tikz} \usetikzlibrary{external} \tikzexternalize[prefix={"C:/Users/MyName MySurname/Documents/LaTeX/Figures/"}]  %\tikzexternalize[prefix={Figures/}]   \begin{document} \begin{tikzpicture}     \draw (0,0) circle (1cm); \end{tikzpicture} \end{document}   gives me the error:     ! I can't write on file `"C:/Users/MyName   MySurname/Documents/LaTeX/Figures/MyMWE-figure0.md5"'.   I'm working with Windows 10, MiKTeX 2.9 distibution.  Following the advice Tarass gave me on a comment of this question:  and as indicated here:  I've registered a user-managed TEXMF directory but I still get the same error.  With \tikzexternalize[prefix={Figures/}] all works perfectly but, since I'm using LyX, the files are stored in a LyX temp dir, hence I loose them when I close the program (making externalization useless), so I need to use an absolute path.
98542
When attempting to run various pieces of software (notably Steam and Yenka), I have come across an error similar to this: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory  I'm running a 64 bit system, with an NVidia Optimus card (I dual boot for certain windows only software that requires a dedicated graphics card). I have bumblebee installed, and I am using the nvidia-current driver, rather that one downloaded from NVidia, as recommended.  The library (libGL.so.1) is not present in the top directory of /usr/lib, however it is present in /usr/lib32/nvidia-current, as a softlink to /usr/lib32/nvidia-current/libGL.so.304.64.  A section of the output from ldconfig -p:  libGL.so.1 (libc6,x86-64, OS ABI: Linux 2.4.20) =&gt; /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 libGL.so (libc6,x86-64, OS ABI: Linux 2.4.20) =&gt; /usr/lib/x86_64-linux-gnu/libGL.so libGL.so (libc6,x86-64, OS ABI: Linux 2.4.20) =&gt; /usr/lib/x86_64-linux-gnu/mesa/libGL.so   Obviously a library with that name is being loaded, but they are located in /usr/lib/x86_64-linux-gnu, however installed software doesn't seem to able to 'see' it. For Steam, running it with optirun causes it to work, but this is not the case for Yenka. I assume that optirun causes the library stored in /usr/lib32/nvidia-current to be  used, which allows Steam to run, so I can't understant why Yenka won't run.  Can anyone explain why software can't see the normal mesa library, and why Yenka refuses to run with the nvidia-current library?
62657
Background  There is a .cls file that pdflatex should use. I have read the following         Using TeX Live 2012, installed into /usr/local/texlive/.  I would like to install the .cls file into $HOME/.texmf (or some other non-standard directory), rather than $HOME/texmf. I thought this would be:  mkdir $HOME/.texmf initexmf --register-root=$HOME/.texmf sudo /usr/local/texlive/2012/bin/x86_64-linux/tlmgr conf texmf TEXMFHOME $HOME/.texmf mv amazingbook.cls $HOME/.texmf latex amazing-stories-1.tex   Problem  The initexmf program does not exist (in TeX Live 2012). I have read that the mktexlsr command is equivalent to initexmf.  Update  Ran:  mktexlsr $HOME/.texmf mv amazingbook.cls $HOME/.texmf mktexlsr $HOME/.texmf   The .cls file cannot be found when running:  pdflatex amazing-stories-1.tex   Question  What are the exact steps necessary to install a custom .cls file into a given directory and configure the environment so that the .cls file is visible from LaTeX using TeX Live 2012?
32097
I am trying to run a rather simple code using tikz and a pgf library. My simple code is  \documentclass{book} \usepackage[explicit]{titlesec} \usepackage{fourier} \usepackage{tikz} \usepackage{epigraph} \usepgflibrary{qrr.shapes.openrectangle}  \begin{document}      This is a test document  \end{document}   This code was copied from Gonzalo Medina's answer in . When I run this code I get the error     '!Package pgf Error: I did not find the pgf library qrr.shapes.openrectangle'.   I am using TeXLive-2014 (actually I installed it yesterday) but nonetheless I updated all packages just in case, but that didn't seem to help.  Any idea how to use this specific library and why it cannot be found in the texmf trees?
65641
I have a fresh install of TeX Live 2013 and am attempting to compile a file using the python package. Here is the relevant portion of the file  \begin{python} print 'hi' \end{python}   I've compiled successfully on my linux machine with TeX Live 2013, but cannot get my windows 7 machine to compile successfully. When I run latex --shell-escape pytest.tex I get an error which begins with   pytest.py: Forbidden to open for writing ! I can't write on file `pytest.py'. \@python ...mediate \openout \@out =\@outname .py                                                    \newlinechar ='15 \begingr...   Can anyone help me fix this so I can compile latex documents using python.sty on my windows machine?  Update  So I'm pretty certain the issue has to do with permissions. If that is the case it would be really great if there were a few easy tests I could run to determine why \write18 cannot open files for writing / what it is trying to do. I've seen some problems from searching that were related to the TEXMFOUTPUT environment variable, but I don't know (1) what to set as the value of TEXMFOUTPUT in order to make sure that these temporary python files are created in the current working directory and (2) if setting TEXMFOUTPUT would have anything to do with these \write18 permission problems.  Ok, one new piece of information: So, I've created a minimal example:  \documentclass[letterpaper,10pt]{article} \usepackage{python} \begin{document}  \begin{python} print 'hi' \end{python}  \end{document}    When compiled after the `! I can't write on file pytest1.py' It says (Press Enter to retry, or Control-Z to exit; default file extension is '.tex' Is this error because write18 can only write to a .tex file?  At the beginning of the compile on the second line it just says ` \write18 enabled'. So it is not running with restricted \write18. I feel like I am really close to fixing this.  Solved  The comment  was exactly right. I had .py listed in my PATHEXT environment variable. Removing it allowed the file to compile without error.  Just read meta.tex.SE and will credit JosephWright once answer is up.
13080
Since arXiv is still using outdated libraries, it doesn't have an up to date TikZ version, which is very inconvenient for me since I'm using TikZ 3.0. Consequently, I get lots of error messages when I submit my article like missing tikzlibraryquotes.code.tex or tikz-cd isn't working properly or doesn't accept certain arguments.  What do I do?
30225
Last night, I migrated my MacBook's operating system from 10.10 "Yosemite" to 10.11 "El Capitan". Everything seemed to go smoothly. Happily, regarding my TeX-related work, I am able to use the GUI front ends "TeXworks" and "TeXshop" just fine since completing the OS upgrade. I use MacTeX2015, with all the latest updates installed.  Oddly, though, since completing the upgrade I can no longer run any MacTeX command-line utilities such as texdoc and kpsewhich. (Actually, as I just discovered, I can no longer run pdflatex either from a command line. However, I never do run pdflatex from a command line prompt, so that's not an urgent problem for me -- at least not for now.)  The suggestions given in the posting  do not seem to be applicable to this case, as they all seem to revolve around setting up /usr/texbin correctly -- /usr/texbin is no longer allowed under MacOSX 10.11. The document  by Herb Schulz deals in depth with adjusting settings in the GUI front ends, but it appears not to touch on what to do about /usr/texbin, which appears to be the now-missing link to TeX's command line utilities.   Pointers and solutions most welcome!