From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: yantar92@posteo.net, 60308@debbugs.gnu.org, bugs@gnu.support
Subject: bug#60308: 30.0.50; Can't read some PDF files any more
Date: Fri, 06 Jan 2023 08:40:13 +0200 [thread overview]
Message-ID: <83bkncw4he.fsf@gnu.org> (raw)
In-Reply-To: <8dea9f3e0ea1e2a45e3b@heytings.org> (message from Gregory Heytings on Thu, 05 Jan 2023 20:58:24 +0000)
> Date: Thu, 05 Jan 2023 20:58:24 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: Ihor Radchenko <yantar92@posteo.net>, 60308@debbugs.gnu.org,
> bugs@gnu.support
>
> >>> I can't read this file with emacs -Q:
> >>>
> >>> https://gnu.support/files/tmp/2023-01-05/FR%20205.pdf
> >>
> >> I can reproduce on Emacs 30 and Emacs 29, but not on Emacs 28
> >>
> >> Recipe: emacs -Q /path/to/the/linked/downloaded/pdf
> >>
> >> Observed: empty buffer
> >> Expected: PDF page is displayed
> >
> > Can someone bisect this, please?
> >
>
> FTR, that file opens fine here, with Emacs 29 at ec172d748f, at
> d2a9dae400, at a6bad4d60f, at c59b8dfefa... and with Emacs 28.
Thanks.
So maybe the problem is updates to libraries/executables we use for
viewing PDF? AFAIR, this is DocView, and it use Ghostscript and
libpng? Maybe both Jean and Ihor had their systems updated recently?
next prev parent reply other threads:[~2023-01-06 6:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 21:39 bug#60308: 30.0.50; Can't read some PDF files any more Jean Louis
2023-01-05 16:50 ` Jean Louis
2023-01-05 17:12 ` Ihor Radchenko
2023-01-05 18:31 ` Eli Zaretskii
2023-01-05 20:58 ` Gregory Heytings
2023-01-06 6:40 ` Eli Zaretskii [this message]
2023-01-06 9:58 ` Stephen Berman
2023-01-06 10:10 ` Gregory Heytings
2023-01-06 10:22 ` Gregory Heytings
2023-01-06 12:51 ` Jean Louis
2023-01-06 10:32 ` Stephen Berman
2023-01-06 11:12 ` Gregory Heytings
2023-01-06 11:44 ` Stephen Berman
2023-01-06 12:04 ` Eli Zaretskii
2023-01-06 12:22 ` Gregory Heytings
2023-01-06 12:55 ` Eli Zaretskii
2023-01-06 20:38 ` Stephen Berman
2023-01-07 15:48 ` Manuel Giraud
2023-01-07 18:25 ` Gregory Heytings
2023-01-07 18:35 ` Eli Zaretskii
2023-01-07 18:45 ` Gregory Heytings
2023-01-07 18:37 ` Manuel Giraud
2023-01-07 18:59 ` Gregory Heytings
2023-01-07 20:07 ` Eli Zaretskii
2023-01-07 20:58 ` Manuel Giraud
2023-01-07 22:19 ` Gregory Heytings
2023-01-08 12:57 ` Manuel Giraud
2023-01-10 10:59 ` Gregory Heytings
2023-01-11 10:35 ` Manuel Giraud
2023-01-11 16:26 ` Gregory Heytings
2023-01-11 17:03 ` Eli Zaretskii
2023-01-11 19:33 ` Gregory Heytings
2023-01-14 8:53 ` Eli Zaretskii
2023-01-07 20:53 ` Manuel Giraud
2023-01-06 12:48 ` Jean Louis
2023-01-05 23:54 ` Jean Louis
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=83bkncw4he.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60308@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=gregory@heytings.org \
--cc=yantar92@posteo.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.