PDF content not rendered when specifying a PDF on command line

[jmozd]

Using Quba-Viewer-1.4.0 on Linux, opening the application including a PDF file name will not render the PDF content, but produce a content warning instead.

If the PDF contains structured content, the PDF display on the left reports the error, while the structured content pane is displayed with proper content from the PDF's structured data.

Opening the same PDFs via d&d or Ctrl-O works properly

The detailed error message reveals that Quba-Viewer is trying to render the PDF using a container-based path, instead of the host file system:

user@host:~> bin/Quba-1.4.0.AppImage somedir/somefile.pdf

PDF.js Version 2.9.359 (build: e667c8cbc) Nachricht: Missing PDF "file:///tmp/.mount_Quba-1zAq2sf/resources/app.asar/dist/lib/pdfjs/web/somedir/somefile.pdf".