Clara Anton Fernandez <cantonfe <at> mtu.edu> writes:
>
> The error shown in the LaTex Errors windows is:"Package pdftex.def
> Error: File `0_media_H_Projects_Cancun_Docs_Presentati"
> I don't know how to get a more complete error message.
The first thing to try would be Document > LaTeX log, and see if the full error
message was written in the log file.
> I've tried entering the path with an absolute and a relative path, none
> of them worked. The preview of the pdf looks fine, in case it makes a
> difference.
>
> The code in lyx looks like:
> \begin{figure}
> \caption{TheTitle}
> \includegraphics{/media/H/Projects/Cancun/Docs/Presentation/Figures/harvbau1}
> \end{figure}
>
> I've also tried inserting it as External Material, the preview looks
> fine, but Lyx crashes immediately after pressing the pdf button.
You're saying that in the LyX GUI you see the figure correctly drawn? I think
that's done from the original source document, not the copy, which means LyX can
see the file on the Samba share (but I expected that).
I can say with certainty (having just checked here) that having an image source
file on /share/whatever... and specifying it with the full path works fine,
including PDF output. The file is copied to the temporary buffer, with a
suitably mangled name. (I'm using LyX 1.6.7 on Linux Mint Helena, by the way.)
I don't have a Samba share on which to test, so I suppose it's possible (but
unlikely) that something specific to Samba is at fault.
Here are a couple of experiments to try:
1. In the home directory for the document, add a symlink to the file on the
Samba share, and use the symlink in the image file path in LyX.
2. Put another copy of the image on the Samba share, but with a short name and
somewhere not too far down from the root of the share, and try using that.
I ran into a situation (years ago, I think) where files that were buried too
deeply on the local hard drive either were not copied correctly to the temp
directory or were copied but then not found by LaTeX, because their path strings
were too long (and something was truncating the paths). The two experiments
above will help determine if path length might be the culprit. I don't really
think that's it, because I just tried a file buried ridiculously deep on a thumb
drive (mounted of course under /media) and had no problem, but we should at
least eliminate the possibility.
/Paul
