PDF Viewer not working in Google Chrome for Windows 11

[lmsoren]

PDF files aren't showing in Google Chrome, Win 11.

They show in Firefox and MS Edge, as well as Firefox for Fedora 37 Workstation.

I frankly can't remember if this is a new issue or if I also had it in older NC versions.

Steps to reproduce

1. Open NC 25 in Google Chrome
2. Click on a PDF file

Expected behaviour

The PDF should show.

Actual behaviour

Blank (black) screen with filename and UI elements present in the top bar

Server configuration

Operating system: Linux 5.15.0-56-generic x86_64 (Ubuntu Web Server 22.04)
Web server: Apache 2.
Database: MySQL

PHP version:
8.2

Nextcloud version: (see Nextcloud admin page)
25.0.2

Client configuration

Browser:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36

Operating system:
Windows 11 Pro, 22H2, build 22621.963

[skjnldsv]

Hello!
I will need your browser console log to investigate this issue.
Open your console, reload your page and/or do the action leading to this issue and copy/paste the log in this thread.

How to access your browser console (Click to expand)

Chrome

• Press either CTRL + SHIFT + J to open the “console” tab of the Developer Tools.
• Alternative method:
  1. Press either CTRL + SHIFT + I or F12 to open the Developer Tools.
  2. Click the “console” tab.

Safari

• Press CMD + ALT + I to open the Web Inspector.
• See Chrome’s step 2. (Chrome and Safari have pretty much identical dev tools.)

IE9

1. Press F12 to open the developer tools.
2. Click the “console” tab.

Firefox

• Press CTRL + SHIFT + K to open the Web console (COMMAND + SHIFT + K on Macs).
• or, if Firebug is installed (recommended):
  1. Press F12 to open Firebug.
  2. Click on the “console” tab.

Opera

1. Press CTRL + SHIFT + I to open Dragonfly.
2. Click on the “console” tab.

[lmsoren]

Hello! I will need your browser console log to investigate this issue. Open your console, reload your page and/or do the action leading to this issue and copy/paste the log in this thread.

How to access your browser console (Click to expand)

Thanks for taking your time and sorry it took a few days to get back!

The logfile exceeds the maximum characters allowed, please download the logfile from

https://www.dropbox.com/s/lo9kl0g7c0ounjo/logfile.txt?dl=0

(Yes, I understand the irony of using Dropbox for this, but my instance is for personal use and I'm not comfortable with exposing it on the interwebs ;-)

[skjnldsv]

Hey, sorry, this is too big for me to debug.
Please filter out warnings, so we only see the errors. Feel free to screenshot the error instead if you prefer.

[skjnldsv]

Yous seem to have a few extensions erroring though.

[szaimen]

Hi @imsoren there have been multiple updates to the pdfviewer in the meantime. Can you please update e.g. to Nextcloud 26.0.3 and check if one of it fixed the problem for you? Thank you!

[lmsoren]

Hi @imsoren there have been multiple updates to the pdfviewer in the meantime. Can you please update e.g. to Nextcloud 26.0.3 and check if one of it fixed the problem for you? Thank you!

@szaimen Thanks for your reply: I upgraded, but the issue is still there.
Note: I'm on a different installation, than I was on when I posted this back in January.

[szaimen]

@imsoren can you send me the pdf file so that I can try to reproduce with the file? You can send it to the mail address that is shown in my github profile :)

[lmsoren]

@szaimen Sending you a sample, but unfortunately the issue is with every PDF I try to view in NC :-/
I can add that they show up fine in Fedora Workstation 38.

[r-hmn]

@imsoren a while ago i also had a PDF viewing problem. it turned out that my browser was based on an outdated chromium version. Have you tried other/newer (chromium based) browsers ?

[joshtrichards]

Note: I'm on a different installation, than I was on when I posted this back in January.

Please re-test in Incognito mode and with all browser extensions disabled. Also, as previously requested, please provide an excerpt of the final few console log messages while reproducing the behavior.

That said, I feel fairly confident this is something about your environment somehow since we'd have many reports if this was a widespread issue with Chrome.