qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lindsay Mathieson <lindsay.mathieson@optusnet.com.au>
To: qemu <qemu-devel@nongnu.org>
Subject: [Qemu-devel] VNC
Date: Tue, 27 Jul 2004 18:53:38 +1000	[thread overview]
Message-ID: <41061812.6060206@optusnet.com.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2763 bytes --]

Using the VNC (5) patch with qemu-0.6.0
I can configure, compile under Mandrake 10, and connect with a VNC 
client, but the first time I hit a key in the vnc client the qemu server 
generates a a seg fault.


qemu win98.img -vnc
Warning: could not read keymap - falling back native keycodes!
27/07/2004 16:26:35 Listening for VNC connections on TCP port 5900
QEMU 0.6.0 monitor - type 'help' for more information
(qemu) 27/07/2004 16:26:40 Got connection from client 192.168.5.69
27/07/2004 16:26:40   other clients:
27/07/2004 16:26:40 Protocol version 3.4
27/07/2004 16:26:40 Ignoring minor version mismatch
27/07/2004 16:26:40 Pixel format for client 192.168.5.69:
27/07/2004 16:26:40   8 bpp, depth 8
27/07/2004 16:26:40   true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
27/07/2004 16:26:40 Using ZRLE encoding for client 192.168.5.69
27/07/2004 16:26:40 rfbProcessClientNormalMessage: ignoring unknown 
encoding type 9
27/07/2004 16:26:40 rfbProcessClientNormalMessage: ignoring unknown 
encoding type 8
27/07/2004 16:26:40 Using compression level 6 for client 192.168.5.69
27/07/2004 16:26:40 Enabling X-style cursor updates for client 192.168.5.69
27/07/2004 16:26:40 Enabling full-color cursor updates for client 
192.168.5.69
27/07/2004 16:26:40 Using image quality level 0 for client 192.168.5.69
27/07/2004 16:26:40 rfbProcessClientNormalMessage: ignoring unknown 
encoding type -65530
27/07/2004 16:26:40 Enabling LastRect protocol extension for client 
192.168.5.69
27/07/2004 16:26:40 Enabling NewFBSize protocol extension for client 
192.168.5.69
27/07/2004 16:26:40 rfbProcessClientNormalMessage: ignoring unknown 
encoding type -65535
27/07/2004 16:26:40 Pixel format for client 192.168.5.69:
27/07/2004 16:26:40   16 bpp, depth 16, little endian
27/07/2004 16:26:40   true colour: max r 31 g 63 b 31, shift r 11 g 5 b 0
27/07/2004 16:26:40 no translation needed
27/07/2004 16:26:40 Using hextile encoding for client 192.168.5.69
27/07/2004 16:26:40 rfbProcessClientNormalMessage: ignoring unknown 
encoding type 9
27/07/2004 16:26:40 rfbProcessClientNormalMessage: ignoring unknown 
encoding type 8
27/07/2004 16:26:40 Using compression level 6 for client 192.168.5.69
27/07/2004 16:26:40 Enabling X-style cursor updates for client 192.168.5.69
27/07/2004 16:26:40 Enabling full-color cursor updates for client 
192.168.5.69
27/07/2004 16:26:40 Using image quality level 0 for client 192.168.5.69
27/07/2004 16:26:40 rfbProcessClientNormalMessage: ignoring unknown 
encoding type -65530
27/07/2004 16:26:40 Enabling LastRect protocol extension for client 
192.168.5.69
27/07/2004 16:26:40 Enabling NewFBSize protocol extension for client 
192.168.5.69
Segmentation fault



-- 
When life hands you lemons, ask for a bottle of gin and tonic.





[-- Attachment #2: Type: text/html, Size: 3445 bytes --]

                 reply	other threads:[~2004-07-27  9:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41061812.6060206@optusnet.com.au \
    --to=lindsay.mathieson@optusnet.com.au \
    --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).