unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: pquessev@gmail.com, alan@idiocy.org, larsi@gnus.org,
	56182@debbugs.gnu.org
Subject: bug#56182: 28.1; Display of SVG file with transparent background is incorrect
Date: Tue, 12 Sep 2023 17:22:21 +0300	[thread overview]
Message-ID: <8334zjpj36.fsf@gnu.org> (raw)
In-Reply-To: <CAJf-WoTrSi0VvEzfGaoH5pLBs2g+GXhuatsLWrunEBJ-xP9tJA@mail.gmail.com> (message from Corwin Brust on Tue, 12 Sep 2023 08:55:37 -0500)

> From: Corwin Brust <corwin@bru.st>
> Date: Tue, 12 Sep 2023 08:55:37 -0500
> 
> Compile: yes.  Fixes the problem: unsure.
> 
> I did not have difficulty building the emacs-29 branch with this patch
> applied. Unfortunately, I could not confirm (or disprove) the success
> of the patch because I received (under -Q) "Invalid Image
> Specification" trying to load etc/images/down.svg.  Here's a
> screenshot:
> 
> https://bru.st/i/emacs-29.1.50.1_i9DY4oaggq.png
> 
> I then confirmed I get this same from a recent (upatched:
> ca95e45f7e828aebdf2736c9c7b2d64f9621214e) build from the development
> branch.  Others I grabbed at random also give this error now, so I'm
> confident it's nothing to do with down.svg.  An unpatched emacs-28
> build could display SVGs, I remember that 29.1 can but didn't check.
> Is it possible there's a recent regression breaking SVG image display
> more generally (perhaps merged up, already)?

I see no problems with SVG images here, but my librsvg is quite old,
so maybe the regression happened in parts that are not compiled with
my librsvg.

> Should I open a seperate bug report?

Yes, please.

Thanks.





  reply	other threads:[~2023-09-12 14:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  6:30 bug#56182: 28.1; Display of SVG file with transparent background is incorrect Pascal Quesseveur
2022-06-24  9:23 ` Lars Ingebrigtsen
2022-06-24 12:18   ` Pascal Quesseveur
2022-06-25  9:25   ` Eli Zaretskii
2022-06-25 16:32     ` Alan Third
2022-06-27  6:49       ` Pascal Quesseveur
2022-06-27  8:12       ` Pascal Quesseveur
2022-06-28 18:38       ` Pascal Quesseveur
2022-06-28 19:45         ` Alan Third
2022-06-29  2:26           ` Eli Zaretskii
2023-09-09 12:09         ` Alan Third
2023-09-11 19:10           ` Alan Third
2023-09-12 13:55             ` Corwin Brust
2023-09-12 14:22               ` Eli Zaretskii [this message]
2023-09-12 17:01                 ` Corwin Brust
2023-09-12 14:19             ` Eli Zaretskii
2023-09-13 19:21               ` Alan Third

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8334zjpj36.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56182@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=corwin@bru.st \
    --cc=larsi@gnus.org \
    --cc=pquessev@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).