qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1087974 <1087974@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [Bug 1087974] Re: [regression] vnc tight png produces garbled output
Date: Tue, 11 Dec 2012 09:57:11 +0100	[thread overview]
Message-ID: <20121211085711.GC23720@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <20121210155458.27947.19873.malone@gac.canonical.com>

On Mon, Dec 10, 2012 at 03:54:58PM -0000, Tim Hardeck wrote:
> 47683d669f993308c2b84bed4ce64aafb5d7ced4 is the first bad commit
> commit 47683d669f993308c2b84bed4ce64aafb5d7ced4
> Author: Gerd Hoffmann <kraxel@redhat.com>
> Date:   Thu Oct 11 12:04:33 2012 +0200
> 
>     pixman/vnc: remove rgb_prepare_row* functions
> 
>     Let pixman do it instead.
> 
>     Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> 
> :040000 040000 653d58e66bf3a2d8240b2f9176979c44ccd720e1
> 6b6e367a8522cb58b42ad8f204387a354d3b3d00 M  ui
> 
> 
> Just reverting this particular commit isn't enough thou but it is connected.

This suggests the conversion to pixman has introduced the bug.

Tim: can you provide steps to reproduce the bug?

Stefan

  reply	other threads:[~2012-12-11  8:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-08 11:46 [Qemu-devel] [Bug 1087974] [NEW] [regression] vnc tight png produces garbled output Tim Hardeck
2012-12-10 14:23 ` Stefan Hajnoczi
2012-12-10 15:54 ` [Qemu-devel] [Bug 1087974] " Tim Hardeck
2012-12-11  8:57   ` Stefan Hajnoczi [this message]
2012-12-11  9:15     ` Gerd Hoffmann
2012-12-11 10:09 ` Tim Hardeck
2012-12-11 14:50   ` Gerd Hoffmann
2012-12-11 11:11 ` Tim Hardeck
2012-12-11 15:50 ` Tim Hardeck
2012-12-14 12:29 ` Tim Hardeck
2016-11-21 15:45 ` Thomas Huth

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=20121211085711.GC23720@stefanha-thinkpad.muc.redhat.com \
    --to=stefanha@gmail.com \
    --cc=1087974@bugs.launchpad.net \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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 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 NNTP newsgroup(s).