# XeLaTeX can find font, but xdvipdfmx can't

I had hoped to use the Minion and Myriad fonts from my new copy of Adobe CS 5 in XeLaTeX; but \setmainfont{Minion Pro} produces the following error: (output of xdvipdfmx -vvv shown)

DVI File Info
Unit: 25400000 / 473628672
Magnification: 1000
Media Height: 41484288
Media Width: 26673152
Stack Depth: 3
Page count: 1
DVI Comment: XeTeX output 2010.08.20:1057
DVI file font info
TeX Font: MinionPro-Regular loaded at ID= 16, size= 9.96pt (scaled 100.0%)
tufte.xdv -> tufte.pdf
D:/TEMP/dvipdfmx.a0056400001 [1 ** ERROR ** Cannot proceed without the "native" font: MinionPro-Regular (Minion Pro Regular)...
Output file removed.

Variations of the argument, such as MinionPro, MinionPro-Regular, Minion Pro Regular, etc., also produce the error. Refreshing the font cache, with fc-cache -fv, doesn't change anything either.

I have determined that it is the output driver, xdvipdfmx, that is causing this error, since invoking xelatex with --no-pdf works without any problems. Apparently XeLaTeX can find the font, but the output driver can't.

To make things even more bizarre, if I select the font like this:

\setmainfont[ExternalLocation,%
BoldFont=MinionPro-Bold.otf,%
ItalicFont=MinionPro-It.otf,%
BoldItalicFont=MinionPro-BoldIt.otf]{MinionPro-Regular.otf}


everything works as expected. Can somebody advise me as to what is going on here?

UPDATE: I changed above to show the output of xdvipdfmx -vvv.

-
I’ve got the same problem with TeX Gyre Pagella. A bit of googling reveals that quite a few people seem to be having this problem. Incidentally, using the (deprecated, I understand?) xdv2pdf instead of xdvipdfmx works so this is may point to a bug in the latter driver. –  Konrad Rudolph Sep 12 '10 at 13:38
FWIW: I had the same problem on Mac OS X, and the fix was to move the fonts from my local directory (~/Library/Fonts) to the system directory (/Library/Fonts). Thanks to Khaled's comment on his answer. –  ShreevatsaR Sep 25 '11 at 11:54

Yes, it's installed on the system, and not in the TEXMF tree. It seems that XeTeX can find the font just fine (since it complains when I replace Minion Pro with a nonsense font name), it's xdvipdfmx that can't find it. –  ptomato Aug 23 '10 at 9:26