From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Regression: pdf.js-2.16.105_1 broken with qutebrowser-2.5.2_1
Date: Thu, 20 Oct 2022 20:44:50 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40061@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2713 bytes --]
New issue by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/40061
Description:
### Is this a new report?
Yes
### System Info
Void 5.15.63_1 x86_64 GenuineIntel notuptodate rFFFFFFFFFFFFFFFFFFF
### Package(s) Affected
pdf.js-2.16.105_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
None noted
### Expected behaviour
Visiting [a sample PDF](https://raw.githubusercontent.com/mozilla/pdf.js/master/examples/learning/helloworld.pdf) in qutebrowser should show an action dialog that presents `Ctrl+p` as an option to view the PDF with `pdf.js`. Choosing this option should open a new window with the `pdf.js` UI and a "Hello World" document displayed.
cc: @heittpr
### Actual behaviour
Although the `pdf.js` UI is displayed, the content array is completely empty. Only the dark gray background is visible. Opening the qutebrowser web console with key combination `wIh` shows the following stack trace:
```
pdf.js:4213
Uncaught TypeError: key.split(...).at is not a function
at new KeyboardManager (pdf.js:4213)
at Function.<static_fields_initializer> (pdf.js:4369)
at Array.Object.defineProperty.value (pdf.js:4342)
at __w_pdfjs_require__ (pdf.js:19477)
at Array.Object.defineProperty.value (pdf.js:3737)
at __w_pdfjs_require__ (pdf.js:19477)
at Array.Object.defineProperty.value (pdf.js:3562)
at __w_pdfjs_require__ (pdf.js:19477)
at Array.Object.defineProperty.value (pdf.js:1119)
at __w_pdfjs_require__ (pdf.js:19477)
viewer.js:4333
Uncaught ReferenceError: require is not defined
at Array.Object.defineProperty.value (viewer.js:4333)
at __webpack_require__ (viewer.js:16331)
at Array.pdfjsLib (viewer.js:1499)
at __webpack_require__ (viewer.js:16331)
at viewer.js:16367
at viewer.js:16546
at viewer.js:16548
viewer.html?filename=tmptkbvwf5m_helloworld.pdf&file=&source=https://raw.githubusercontent.com/mozilla/pdf.js/master/examples/learning/helloworld.pdf:466
Uncaught TypeError: Cannot read property 'set' of undefined
at HTMLDocument.<anonymous> (viewer.html?filename=tmptkbvwf5m_helloworld.pdf&file=&source=https://raw.githubusercontent.com/mozilla/pdf.js/master/examples/learning/helloworld.pdf:466)
```
Downgrading to `pdf.js-2.14.305_1` fixes the problem.
### Steps to reproduce
1. `xbps-install qutebrowser pdf.js`
2. `qutebrowser "https://raw.githubusercontent.com/mozilla/pdf.js/master/examples/learning/helloworld.pdf"`
3. Press `Ctrl+p` to show broken PDF viewer
4. Press `wIh` to open the browser debug view, then choose the `Console` from the tabs to see the stack trace.
next reply other threads:[~2022-10-20 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 18:44 ahesford [this message]
2022-10-20 22:02 ` heittpr
2022-10-20 22:19 ` heittpr
2022-10-20 22:19 ` heittpr
2022-10-20 22:25 ` ahesford
2022-10-20 22:43 ` ahesford
2022-10-20 22:48 ` heittpr
2022-10-21 2:29 ` ahesford
2022-10-24 1:09 ` [ISSUE] [CLOSED] " ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40061@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).