All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Hupp <jdhupp@prpcompany.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, dri-devel@lists.freedesktop.org
Subject: Re: Moving a bug upstream per downstream request, emailing the maintainers
Date: Fri, 16 Aug 2013 17:34:32 -0400	[thread overview]
Message-ID: <520E9AE8.8000207@prpcompany.com> (raw)
In-Reply-To: <20130816074325.GC2819@nuc-i3427.alporthouse.com>

On 8/16/2013 3:43 AM, Chris Wilson wrote:
> On Thu, Aug 15, 2013 at 03:28:53PM -0400, John Hupp wrote:
>> [1.] One line summary of the problem:
>> Flash 11.2 content displays in shades of green and purple only, and
>> in a horizontally compressed space
>>
>> [2.] Full description of the problem/report:
>> The full downstream bug report is at
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212455 , but
>> my description from there:
>>
>> In my testing with the Intel driver using its default acceleration:
>> - Flash 11.2 works on Quantal with the 3.5 kernel
>> - Flash 11.2 works on Raring with the 3.5.0-17 kernel (though it
>> boots to a low-res desktop with a frozen pointer)
>> - Flash 11.2 works on Raring also with the 3.6.11-030611 or
>> 3.7.10-030710 mainline kernels
>> - Flash 11.8 works on Raring with the 3.8 kernel (in Chrome)
>> - Flash 11.2 fails on Raring with the 3.8 kernel
>> - Flash 11.2 fails on Raring with the latest mainline kernel,
>> 3.11.0-031100rc5
>> - Flash 11.2 fails on Saucy alpha 2 with its default kernel
> It's a flash bug. They ignore the format of the Window that they
> PutImage to. (Worse, they create an image of the right depth or else X
> would reject the PutImage with a BadMatch and then render incorrect
> pixel data into it.)
> -Chris
>

OK, thanks for identifying the problem.

  reply	other threads:[~2013-08-16 21:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 19:28 Moving a bug upstream per downstream request, emailing the maintainers John Hupp
2013-08-16  7:43 ` Chris Wilson
2013-08-16 21:34   ` John Hupp [this message]
2013-09-13 19:35 ` John Hupp

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=520E9AE8.8000207@prpcompany.com \
    --to=jdhupp@prpcompany.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.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.