From: Thomas Huth <925405@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 925405] Re: VNC server does not work with Mac Screen Sharing
Date: Sun, 01 Jan 2017 10:23:48 -0000 [thread overview]
Message-ID: <20170101102348.2743.69955.malone@gac.canonical.com> (raw)
In-Reply-To: 20120202110843.18662.48430.malonedeb@wampee.canonical.com
QEMU 2.0 is not maintained by the QEMU project anymore. Can you please
try again with the latest release of QEMU (v2.8)? ... otherwise you
should report this to the bug tracker of your distro instead.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/925405
Title:
VNC server does not work with Mac Screen Sharing
Status in QEMU:
Incomplete
Status in Ubuntu:
Invalid
Bug description:
When connecting to a QEMU instance from a Mac using any VNC settings
on the QEMU CLI and any target arch (ARM, Intel, etc.), the connection
is attempted but the negotiation never finishes.
I've verified this when building QEMU from source (1.0 and HEAD) on
Ubuntu, Fedora and Debian or when using Ubuntu (Oneiric) and Debian
(Lenny) packages.
It does not matter whether I specify authentication (or anything else)
on QEMU's side, the behavior is always the same - I see the connection
being established using netstat and tcpdump, but QEMU does not seem to
send back any pixmap data after the connection setup.
Best guess as to why this happens is that the VNC negotiation on QEMU
does not like the protocol version and VNC encoding sent by the Mac's
built-in VNC client, or that its negotiation logic is subtly broken. I
appreciate that it's not meant to be a full VNC server, but it
prevents me from using it remotely until a stable Mac build is
feasible.
Background info:
Mac OS X includes a VNC client called Screen Sharing that you can
invoke in two different ways:
* At a terminal, by typing "open vnc://hostname:tcp_port"
* From any URI-enabled field (such as the Safari URI field), where you can just type the URI as vnc://hostname:tcp_port
Please do not confuse the enhanced VNC protocol Apple Remote Desktop
uses with Screen Sharing - they are not mutually exclusive, but they
are not incompatible either, since what Apple does is to negotiate
extra pixmap encoding and authentication options - I use Screen
Sharing to access many VNC servers such as vnc4server, tightvncserver,
vino, etc. without any issues whatsoever, so the issue I'm reporting
is not an issue with Apple's implementation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/925405/+subscriptions
next prev parent reply other threads:[~2017-01-01 10:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 11:08 [Qemu-devel] [Bug 925405] [NEW] VNC server does not work with Mac Screen Sharing Rui Carmo
2012-02-02 13:20 ` [Qemu-devel] [Bug 925405] " Rui Carmo
2012-02-16 10:52 ` Fabio Marconi
2014-09-01 21:04 ` Hendrik
2016-12-29 7:53 ` Dave Eckhardt
2017-01-01 10:23 ` Thomas Huth [this message]
2017-01-01 16:55 ` Rui Carmo
2017-01-02 18:57 ` François Revol
2017-01-02 19:14 ` Rui Carmo
2017-01-02 21:44 ` mmu_man
2017-01-03 8:50 ` Thomas Huth
2021-05-03 9:51 ` Thomas Huth
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=20170101102348.2743.69955.malone@gac.canonical.com \
--to=925405@bugs.launchpad.net \
--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).