The version of XeTeX (xdvipdfmx) lacks an appropriate configuration file which is required for support for including PDF files with a version > 1.4. Reproducible: Always Steps to Reproduce: 1. Use Inkscape or any other application to create a PDF file. 2. Check the first few letters of the file to make sure it is a PDF 1.4 file. 3. Create a new tex document which attempts to include the PDF fiel (\XeTeXpdffile) 4. Attempt to run the file through xelatex. Actual Results: The PDF file generated will not contain the image. Expected Results: The images included in .tex document will not be present in the PDF output. One can get the exact warning like so: xelatex -no-pdf test.tex; xdvipdfmx test.tex; This will generate a ** WARNING ** about the PDF file having too newer version. This is a problem which does *not* occur with the stock TeXLive distribution (tried on a different Linux install and a MacText (TextLive 2007) install). It can be resolved by using a custom dvipdfmx config file in: ~/.texmf-config/dvipdfm/dvipdfmx.cfg with the line: V 4.
What package is this? dev-texlive/texlive-xetex or app-text/xetex?
I am using dev-texlive/texlive-xetex.
does uncommenting the line in /etc/texmf/dvipdfm/dvipdfmx.cfg helps ?
This is a dup of Bug 222869 or vice versa. In Bug 222869 i already reported, that the file "dvipdfmx.cfg" is not installed by app-text/xdvipdfmx. To make the chaos complete, the file is part of app-text/dvipdfmx. So if app-text/xdvipdfmx would install the dvipdfmx.cfg, we's had a file collision between app-text/xdvipdfmx and app-text/dvipdfmx. Also notice, that the defaults of the file that ships with xdvipdfmx are different from the defaults provided by dvipdfmx. (The "V 4" is not commented - "V 4" is default).
Also notice: Before i installed dvipdfmx, i didn't have any dvipdfmx.cfg on my system. That's why i reported Bug 222866: i had only xetex and xdvipdfmx installed without dvipdfmx. And i didn't have any dvipdfmx.cfg on my system.
as we're now using texlive's xdvipdfmx, tl-core-2008-r3 now ships the .cfg file too and it should be fine