Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corrupted PDF display under Crostini (ChromeOS Linux container) #11575

Closed
msiniscalchi opened this issue Feb 8, 2020 · 3 comments
Closed

Corrupted PDF display under Crostini (ChromeOS Linux container) #11575

msiniscalchi opened this issue Feb 8, 2020 · 3 comments

Comments

@msiniscalchi
Copy link

Attach (recommended) or Link to PDF file here:
Using the demo PDF on the pdf.js website

Configuration:

  • Chromium Version 79.0.3945.130 (Developer Build) built on Debian 10.2, running on Debian 10.2 (64-bit)
  • Operating system and its version: Debian Buster running in the ChromeOS Linux default container ("Crostini")
  • PDF.js version: whatever version the demo on the PDF.js web page uses
  • Is a browser extension: NO

Steps to reproduce the problem:

  1. Go to the PDF.js webpage
  2. Click "Demo"

What is the expected behavior? (add screenshot)

PDF is displayed correctly

What went wrong? (add screenshot)
Most characters are simply not displayed.

Screenshot 2020-02-07 at 6 17 22 PM

Comments: I originally found out about this problem using the VScode LaTeX Workshop extension, which uses pdf.js to display PDF files produced by LaTeX. I was having the same issue with my own files---most characters just were not displayed. However, as shown above, the exact same behavior occurs when running a browser under Crostini.

If I instead visit the pdf.js website using Chrome, NOT within the Crostini container but under "regular" ChromeOS, everything works perfectly.

@Snuffleupagus
Copy link
Collaborator

This does look more like a <canvas> and/or Font loading bug in the platform/browser itself, rather than a general PDF.js library issue (since otherwise you'd expect it to be broken everywhere).

@msiniscalchi
Copy link
Author

Hm. Interesting. Indeed things seem to work using Firefox-esr (68.4.1esr 64-bit). See attached screenshot. So this seems to be a Chromium-on-Crostini-specific issue. As I mentioned in the original message, the issue dues not arise with the standard Chrome browser in ChromeOS . It does however arise with Chromium 79, and with the Chromium engine built into VSCode.
Screenshot 2020-02-08 at 1 01 19 PM

@timvandermeij
Copy link
Contributor

This doesn't look like something that can be fixed on the PDF.js side. It's best to report the issue to the Chrostini developers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants