From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Simon Rowe <simon.rowe@nutanix.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"freddy77@gmail.com" <freddy77@gmail.com>
Subject: Re: Corrupt VNC display for 1366x768
Date: Wed, 2 Oct 2024 13:01:20 +0100 [thread overview]
Message-ID: <Zv02EDIKgmq2L0fg@redhat.com> (raw)
In-Reply-To: <DM8PR02MB81217D61C42562572F8AFFB093702@DM8PR02MB8121.namprd02.prod.outlook.com>
On Wed, Oct 02, 2024 at 11:09:13AM +0000, Simon Rowe wrote:
> I've been trying to track down the cause of a glitch that affects guest VNC consoles when the resolution is set to 1366x768. This results in a "stair case" effect where each successive row is offset to the right by a handful of pixels. I believe this is related to the fact that the horizontal resolution only divisible by 2, not 16 which most others are.
>
> There was a similar report many years ago, with a proposed patch
>
> https://lists.gnu.org/archive/html/qemu-devel/2013-03/msg02732.html
>
> but this was never committed and the code has been significantly reworked in the meantime.
>
> Could anyone give me any pointers as to where the problem may lie?
There's a newer bug report here, but not real progress:
https://gitlab.com/qemu-project/qemu/-/issues/90
1366 is particularly problematic as it apparently can't be represented
exactly in EDID which needs a x8 multiple.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-10-02 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 11:09 Corrupt VNC display for 1366x768 Simon Rowe
2024-10-02 12:01 ` Daniel P. Berrangé [this message]
2024-10-02 12:59 ` Simon Rowe
2024-10-03 13:01 ` Simon Rowe
2024-10-03 13:05 ` Daniel P. Berrangé
2024-10-03 13:34 ` Simon Rowe
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=Zv02EDIKgmq2L0fg@redhat.com \
--to=berrange@redhat.com \
--cc=freddy77@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=simon.rowe@nutanix.com \
/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.