When compiling the attached file with pdflatex, the error message points to ./dy-log2011.tex:4 instead of ./dy-log_tracking.tex:4 Changing the length of the path to this files (i.e. by creating a symlink with less 'a') solves the problem. The problem shows up for every warning or error after this \includegraphics statement while the correct file is shown if the error happens before this \includegraphics I have no clue what is going on. It's reasonably easy to work around but in large files (e.g. thesis) rather annoying to locate the excat line that triggers the problem... Reproducible: Always
Created attachment 83954 [details] minimal example
After being annoyed by this for too long, I took the time to try an fix this. The attached patch solves the problem and has not shown any negative side effects so far.
Created attachment 85573 [details] fixing this bug the bug was triggered by when the last char on a line was an opening parenthesis the patch pushes an dummy "file" onto the stack in these cases. (The dummy file gets popped when the parenthesis is closed on the next line)
What's the state of this? Anything I can do to help this fix to progress?
Unfortunately you have to wait until the maintainer of this code has time to review the patch.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Just checked again, the minimal example provided still works. Compiling dy-log2011.tex will trigger two errors: ./dy-log_tracking.tex:1:Unkown float option... ./dy-log2011.tex:4:Undefined control sequence \gt The first error is due to the missing \usepackage{float} and reported at the proper place. The second error is actually in ./dy-log_tracking.tex at line 4... So, yes this bug is still valid. (I did not recompile with my patc, so I can't say if that would still work.)
Thanks for the update!