all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Ponce <da_vid@orange.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64908@debbugs.gnu.org
Subject: bug#64908: 29.1; svg parse failure
Date: Fri, 4 Aug 2023 09:55:03 +0200	[thread overview]
Message-ID: <ac9501a3-001e-b429-9b6d-d0407d27c555@orange.fr> (raw)
In-Reply-To: <83o7jnwfd3.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

On 04/08/2023 07:23, Eli Zaretskii wrote:
>> Date: Thu, 3 Aug 2023 21:16:35 +0200
>> From: David Ponce <da_vid@orange.fr>
>>
>> In case it could help, using emacs from master (see details at end
>> below), with librsvg2-2.56.0-1.fc38.x86_64 I can insert-image
>> dir-src-open.svg and dir-public-open.svg in the *scratch-buffer*
>> without issue (see Screenshot1).
>>
>> However, the same failed using librsvg2-2.56.3-1.fc38.x86_64 (see
>> Screenshot2).
>>
>> I did test also with some KDE breeze icons.
>>
>> No issue with librsvg2-2.56.0-1.fc38.x86_64.
>>
>> With librsvg2-2.56.3-1.fc38.x86_64 some icons works, some not (see an
>> example in Screenshot3):
>>
>> /usr/share/icons/breeze/actions/22/go-next.svg doesn't work:
>>
[...]
>>
>> /usr/share/icons/breeze/actions/22/go-next.svg works:
>>
[...]
>>
>> As far as I can see, other applications (Gwenview, Geeqie, Firefox) don't have
>> problem to display the same images with librsvg2-2.56.3-1.fc38.x86_64 installed.
> 
> Thanks, this helps.
> 
> When an image fails to display, do you see any error messages from
> librsvg?  Those are usually emitted to stderr, so perhaps you need to
> run Emacs in a way that stderr is not discarded, but either shown on
> the terminal or written to a file.

Hello ELi,

I don't see any message on stderr, but a bunch of messages:
"Invalid image size (see ‘max-image-size’)" in the *Messages* buffer,
probably related to the display of an invalid image (empty square)
in the *scratch* buffer. Also, the result of image-size is not the
expected image size (22x22 px in example). I attached a screenshot.

Thanks

[-- Attachment #2: Screenshot.png --]
[-- Type: image/png, Size: 148177 bytes --]

  reply	other threads:[~2023-08-04  7:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  1:10 bug#64908: 29.1; svg parse failure Daniel Vianna
2023-07-28  6:05 ` Eli Zaretskii
     [not found]   ` <CAMLJ+NHO38NYGPctAj9MmMwy4tz8aSqHgLDWQhQaDm7FUP7Yqw@mail.gmail.com>
2023-07-28 11:00     ` Eli Zaretskii
2023-07-28 12:48       ` Visuwesh
2023-08-03  8:11         ` Eli Zaretskii
2023-08-03 19:16 ` David Ponce
2023-08-04  5:23   ` Eli Zaretskii
2023-08-04  7:55     ` David Ponce [this message]
2023-08-04 10:26       ` Eli Zaretskii
2023-08-04 16:23         ` David Ponce
2023-08-04 18:32         ` Alan Third
2023-08-04 19:08           ` Eli Zaretskii
2023-08-04 21:08             ` David Ponce
2023-08-05  8:30               ` David Ponce
2023-08-05  9:58                 ` Alan Third
2023-08-05 10:07                   ` Eli Zaretskii
2023-08-05 10:24                     ` Alan Third
2023-08-05 10:41                       ` Eli Zaretskii
2023-08-05 12:32                   ` David Ponce
2023-08-05 15:14                     ` Alan Third
2023-08-05 15:53                       ` David Ponce
2023-08-05 16:02                         ` Alan Third
2023-08-05 16:24                           ` David Ponce
2023-08-05 16:31                             ` Alan Third
2023-08-05 17:37                               ` David Ponce
2023-08-05 17:39                                 ` Alan Third
2023-08-05 18:00                                   ` David Ponce
2023-08-05 18:31                                     ` Alan Third
2023-08-05 20:04                                       ` David Ponce
2023-08-08 13:58                                         ` David Ponce
2023-08-08 21:18                                           ` Alan Third
2023-08-08 22:22                                             ` David Ponce

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=ac9501a3-001e-b429-9b6d-d0407d27c555@orange.fr \
    --to=da_vid@orange.fr \
    --cc=64908@debbugs.gnu.org \
    --cc=eliz@gnu.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.
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.