getting error about headless

[tony-an-phd]

Description

I have been getting the following errors when I tried to render a qmd. I updated the quarto and Chrome to the latest version, and I followed the instruction setting environment variable QUARTO_CHROMIUM_HEADLESS_MODE=new etc, but no luck, the same error persist. Any idea how to fix this? I have no idea what the two links below about chrome is about or how to use it.

Stack trace:
Chrome process error: Old Headless mode has been removed from the Chrome binary. Please use the new Headless mode (https://developer.chrome.com/docs/chromium/new-headless) or the chrome-headless-shell which is a standalone implementation of the old Headless mode (https://developer.chrome.com/blog/chrome-headless-shell).

at criClient (file:///C:/Program Files/Quarto/bin/quarto.js:38718:15)
at eventLoopTick (ext:core/01_core.js:175:7)
at async file:///C:/Program Files/Quarto/bin/quarto.js:38676:22
at async Semaphore.runExclusive (file:///C:/Program Files/Quarto/bin/quarto.js:38350:29)
at async Object.createPngsFromHtml (file:///C:/Program Files/Quarto/bin/quarto.js:38947:42)
at async makePng (file:///C:/Program Files/Quarto/bin/quarto.js:82312:70)
at async makeDefault (file:///C:/Program Files/Quarto/bin/quarto.js:82372:24)
at async Object.cell (file:///C:/Program Files/Quarto/bin/quarto.js:82395:20)
at async Promise.all (index 0)
at async Object.document (file:///C:/Program Files/Quarto/bin/quarto.js:39242:25)

Error occurred during cleanup: NotFound: entity not found

[mcanouil]

What version of Quarto are you using?

• How do I render and publish via Github actions using Chrome headless? #11966
• Transition to Chrome new headless mode #10532
• Chrome Headless improvements #11877

[tony-an-phd]

I am using 1.6.40

[mcanouil]

Could you go through the threads I shared?
Some changes were made but only for 1.7.13

Accessibility: Why did you put a link to the get started page of the documentation for the Quarto version? The page does not target a specific version.

[tony-an-phd]

To show you where the latest version I found, so I put a link to it.

[mcanouil]

FYI, no assistive reader can possibly understand that. The text used for link should always describe the link to allow users (with or without assistive technologies) to know what the link is about. (Source: WCAG: writing meaningful link text)

[tony-an-phd]

Update to 1.7.13 resolved the issue.