From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cam Macdonell Subject: Re: vnc protocol broken Date: Wed, 29 Apr 2009 09:14:35 -0600 Message-ID: <49F86EDB.9000207@cs.ualberta.ca> References: <7B7881568CF40E4388B615CD06F87B98098DAC@clara.maurer-it.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Dietmar Maurer Return-path: Received: from fleet.cs.ualberta.ca ([129.128.22.22]:52253 "EHLO fleet.cs.ualberta.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752884AbZD2POp (ORCPT ); Wed, 29 Apr 2009 11:14:45 -0400 Received: from fleet.cs.ualberta.ca (localhost.localdomain [127.0.0.1]) by fleet-spampd (Postfix) with ESMTP id 64D7A28033 for ; Wed, 29 Apr 2009 09:14:36 -0600 (MDT) In-Reply-To: <7B7881568CF40E4388B615CD06F87B98098DAC@clara.maurer-it.com> Sender: kvm-owner@vger.kernel.org List-ID: 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