All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cam Macdonell <cam@cs.ualberta.ca>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: kvm@vger.kernel.org
Subject: Re: vnc protocol broken
Date: Wed, 29 Apr 2009 09:14:35 -0600	[thread overview]
Message-ID: <49F86EDB.9000207@cs.ualberta.ca> (raw)
In-Reply-To: <7B7881568CF40E4388B615CD06F87B98098DAC@clara.maurer-it.com>

Dietmar Maurer wrote:
> Hi all,
> 
> the new vnc code seems to be broken. At least all java based viewers
> have serious problems, also realvnc for X
> 
> For example:
> 
> # kvm -cdrom ubuntu-9.04-desktop-amd64.iso -vnc :0 & vncviewer :0
> 
> CConn:       Throughput 20000 kbit/s - changing to hextile encoding
>  CConn:       Throughput 20000 kbit/s - changing to full colour
>  CConn:       Using pixel format depth 16 (16bpp) little-endian rgb565
>  CConn:       Using hextile encoding
> Rect too big: 10794x10794 at 10794,42 exceeds 720x400
>  main:        Rect too big
> 
> The protocol stream seems to be clobbered somehow after the first
> resize.
> 
> VNC Viewer Free Edition 4.1.1 for X - built Jan 30 2009 23:06:3
> 
> similar issues with tightvnc java viewer.
> 
> Any idea howto debug that further?
> 

I think this is a known problem in qemu mentioned here on qemu-devel

http://article.gmane.org/gmane.comp.emulators.qemu/42321

The vinagre viewer seems to be a little more resilient.  It's not a 
permanent solution of course if you need a java-based viewer.

Cam

  reply	other threads:[~2009-04-29 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29  8:28 vnc protocol broken Dietmar Maurer
2009-04-29 15:14 ` Cam Macdonell [this message]
2009-05-04 15:00   ` Dietmar Maurer

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=49F86EDB.9000207@cs.ualberta.ca \
    --to=cam@cs.ualberta.ca \
    --cc=dietmar@proxmox.com \
    --cc=kvm@vger.kernel.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.