From: Paul Eggert <eggert@cs.ucla.edu>
To: 22442@debbugs.gnu.org
Subject: bug#22442: 25.0.50; --with-cairo does not display PNG on GNU/Linux
Date: Sat, 23 Jan 2016 00:27:08 -0800 [thread overview]
Message-ID: <56A3395C.4040208@cs.ucla.edu> (raw)
To reproduce the problem, configure Emacs --with-cairo, and then run these shell
commands:
wget https://upload.wikimedia.org/wikipedia/commons/f/f5/All_palaeotemps.png
emacs -Q All_palaeotemps.png
Emacs shows a blank (or sometimes garbled) screen instead of the image.
I think the problem is that lookup_rgb_color is returning garbage.
Here are more details about the configuration, built on Fedora 23 x86-64:
In GNU Emacs 25.0.50.55 (x86_64-unknown-linux-gnu, GTK+ Version 3.18.6, cairo
version 1.14.2)
of 2016-01-22 built on penguin.cs.ucla.edu
Repository revision: 27a0919cde7a6dce93aeba63b5ce7d0834f48531
Configured using:
'configure --enable-gcc-warnings --with-cairo'
Configured features:
XPM JPEG TIFF GIF PNG RSVG CAIRO IMAGEMAGICK SOUND GPM DBUS GCONF
GSETTINGS NOTIFY ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF
XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11
Important settings:
value of $LC_ALL: en_US.utf8
value of $LC_COLLATE: en_US.UTF-8
value of $LC_CTYPE: en_US.UTF-8
value of $LC_MESSAGES: en_US.UTF-8
value of $LANG: C
locale-coding-system: utf-8-unix
next reply other threads:[~2016-01-23 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 8:27 Paul Eggert [this message]
2016-01-23 9:24 ` bug#22442: 25.0.50; --with-cairo does not display PNG on GNU/Linux Eli Zaretskii
2016-01-23 9:44 ` Paul Eggert
2016-01-24 0:31 ` Paul Eggert
2016-01-24 6:38 ` Mark Oteiza
2018-12-11 2:29 ` Dmitry Gutov
-- strict thread matches above, loose matches on Subject: below --
2016-01-22 10:54 [PATCH] Fix compilation erorr when --enable-gcc-warnings passed Alexander Kuleshov
2016-01-23 0:06 ` Paul Eggert
2016-01-23 6:28 ` Alexander Kuleshov
2016-01-23 9:12 ` bug#22442: 25.0.50; --with-cairo does not display PNG on GNU/Linux Paul Eggert
2016-01-23 9:25 ` Eli Zaretskii
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=56A3395C.4040208@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=22442@debbugs.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.