New answers tagged linux
After checking the recently updated packages, I found ghostscript was updated from 9.14-1 to 9.15-1, which is very suspicious as I could find any problem exists in Texlive 2014 itself. After downgrading, this problem is solved. I am not sure what is wrong with this new ghostscript. Xelatex must called some postscript functionalities from ghostscript.
This is a more general UNIX sysadmin question, but you can use visudo to add Defaults secure_path="/usr/local/texlive/2014/bin/x86_64-linux:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" Edit that path for your environment! See https://wiki.debian.org/sudo or https://www.google.com/search?&q=sudo+secure_path on the web, and the manual ...
put the file in ~/texmf/tex/latex/bbm/ (you may have to create directories for that). however, the fonts are distributed separately as metafont source and you'll need to install them, too; it's a long time since i've done that, but try copying all of the font files on an archive mirror into ~/texmf/fonts/bbm after that, i reckon it’s worth running texhash ...
Top 50 recent answers are included