vncviewer crashes when connecting to qemu-kvm vnc server

[Ralf Spenneberg]

Ubuntu Precise
Versions:
qemu-kvm 1.0+noroms-0ubuntu2
xvnc4viewer 4.1.1+xorg4.3.0-37ubuntu3

Connecting to a virtual guest via the qemu built in vnc-server crashes xvnc4viewer. The image is drawn and then the client crashes.

# xvnc4viewer 192.168.0.202:5900
VNC Viewer Free Edition 4.1.1 for X - built Sep 7 2011 11:16:25
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Fri Dec 30 12:00:37 2011
 CConn: connected to host 192.168.0.202 port 5900
 CConnection: Server supports RFB protocol version 3.8
 CConnection: Using RFB protocol version 3.8
 TXImage: Using default colormap and visual, TrueColor, depth 16.
 CConn: Using pixel format depth 6 (8bpp) rgb222
 CConn: Using ZRLE encoding

Fri Dec 30 12:00:38 2011
 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
 main: ZlibInStream: inflate failed

Using a different Encoding the vncviewer crashes after 1 second with unknown message type.

# xvnc4viewer -PreferredEncoding raw -Autoselect=0 192.168.0.202:5900

VNC Viewer Free Edition 4.1.1 for X - built Sep 7 2011 11:16:25
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Fri Dec 30 12:01:52 2011
 CConn: connected to host 192.168.0.202 port 5900
 CConnection: Server supports RFB protocol version 3.8
 CConnection: Using RFB protocol version 3.8
 TXImage: Using default colormap and visual, TrueColor, depth 16.
 CConn: Using pixel format depth 6 (8bpp) rgb222
 CConn: Using raw encoding
unknown message type 63

Fri Dec 30 12:01:55 2011
 main: unknown message type

[Alexander Nekrasov (lxndr-nkrsv)]

avoided this with -FullColor option.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Ralf Spenneberg, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please feel free to subscribe me to this new report.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs