### Discussed in https://github.com/quarto-dev/quarto-cli/discussions/3359

<div type='discussions-op-text'>

<sup>Originally posted by **fuhrmanator** November 16, 2022</sup>
I spent several hours trying to track down why my CI for the Quarto book project I have (running on ubuntu) wasn't building a valid PDF (there was no error in the build). I had made some big changes to my book project and hadn't verified the PDF on the web, and thought it was I who "broke" things with ubuntu (I actually didn't realize the CI was running the release candidate builds). The PDF was coming out corrupt. I tried to remove all the changes I'd made in the past week, but couldn't get a MWE; the simplest book (hello world preface) was still a corrupt PDF.

On my Windows station everything is OK. I'm using Quarto 1.2.233, and the PDFs are fine. So, when I realized the CI builds were moving ahead of my windows version, I set them to 1.2.233 also, and now everything is OK.

I suspect it has something to do with `pdf-engine: latexmk`, since on a separate laptop I can get a Quarto project to render good PDFs if I don't use `latexmk` with the latest (1.2.269). It looks like some kind of regression (not sure when this started, sorry).</div>
dragonstyle
2022-11-17T14:05:50Z
dragonstyle
v1.2
closed
Debugging corrupted PDFs turns out to be a problem with Quarto after 1.2.233 with latexmk
https://github.com/quarto-dev/quarto-cli/issues/3364