From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: jpeg image does not show in background
Date: Sun, 03 Oct 2010 00:17:30 +0200 [thread overview]
Message-ID: <4CA7AF7A.50507@gmail.com> (raw)
In-Reply-To: <AANLkTinrq1GSG4rzkqdgidhr9dXQ=ORnmyjqubc+jDdn@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2604 bytes --]
On 10/02/2010 11:17 AM, Piscium wrote:
> 2010/10/1 Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>:
>
>
>> On 10/01/2010 08:55 PM, Piscium wrote:
>>
>
>>> The conclusion appears to be that the jpeg module in grub2 is very
>>> fussy about the files that it displays. Note there was nothing special
>>> about the files I wanted to display. The "green_mountains" was taken
>>> from a blog, and the two 1280x1024 images were taken from the Gnome
>>> Art website.
>>>
>>>
>
>> It's not really "nothing particular". With pictures taken by my camera
>> it works fine.
>>
> The site I mentioned, Gnome Art is this:
> http://art.gnome.org/backgrounds
>
> It is where some people come to get nice background images, and not
> just Gnome users. For example, in my Windows PC at work I have a
> background from this site.
This isn't a place for advertisement.
> So it would be good if pictures from this
> site could be displayed with grub2. They are just normal pictures.
>
> In fact I think the site could be used as a test resource for the
> grub2 background image feature, as it has images created by various
> people in various sizes and with various cameras and software
> packages.
>
>
>
>>> There is a file grub-core/video/readers/jpeg.c. It has plenty of debug
>>> statements like:
>>> "grub_error (GRUB_ERR_BAD_FILE_TYPE, "jpeg: huffman decode fails");
>>>
>>> Is there some easy way to read the text of these messages? (I have no
>>> JTAG and my hardware does not support virtualization).
>>>
>>>
>>>
>> They aren't debug messages but error messages which are shown if you
>> call background_image manually.
>>
> By loading the image files manually on the command line I got this
> error message for both problem files:
> "jpeg: invalid 0xFF in data stream"
>
>
This is very insightful. The issue is because of optional (and useless)
padding in jpeg. I know how to fix it but is too tired right now
(admiring beauties of my country takes sometimes effort)
> This comes from jpeg.c, line 124.
>
> I have created a bug report as you requested, unfortunately I could
> not attach the said files as they exceed the site limit. If you want I
> can email the files to you or upload to some temporary place of your
> choice. (The file sizes are 2.1 Mb and 577 Kb).
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2010-10-02 22:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 12:10 jpeg image does not show in background Piscium
2010-10-01 12:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-10-01 13:03 ` Piscium
2010-10-01 14:00 ` Piscium
2010-10-01 14:34 ` Piscium
2010-10-01 16:11 ` Piscium
2010-10-01 16:44 ` BandiPat
2010-10-01 18:55 ` Piscium
2010-10-01 20:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-10-02 9:17 ` Piscium
2010-10-02 9:31 ` Piscium
2010-10-02 22:17 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-10-01 18:12 ` Colin D Bennett
2010-10-01 18:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
-- strict thread matches above, loose matches on Subject: below --
2010-10-01 14:15 Tom Davies
2010-10-01 15:40 ` Piscium
2010-10-01 18:10 ` Colin D Bennett
2010-10-01 18:39 ` Piscium
2010-10-02 19:48 Tom Davies
2010-10-02 22:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4CA7AF7A.50507@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@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.
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.