All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thorsten Glaser <t.glaser@tarent.de>
Cc: qemu-devel@nongnu.org
Subject: Re: qemu-system-x86_64: warning: Unknown X11 keycode mapping '<null>'.
Date: Tue, 3 Mar 2020 13:14:07 +0000	[thread overview]
Message-ID: <20200303131407.GF1773352@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2003031410520.18659@tglase.lan.tarent.de>

On Tue, Mar 03, 2020 at 02:12:04PM +0100, Thorsten Glaser wrote:
> On Tue, 3 Mar 2020, Daniel P. Berrangé wrote:
> 
> > AFAICT, this is not the case. On both my Fedora & Debian installs,
> > x11vnc is just a binary that attaches to an existing X11 server
> 
> Huh, weird. Perhaps this changed over the years and distro releases.
> 
> >   $ ls -al /usr/bin/vncserver
> 
> $ realpath $(which vncserver)
> /usr/bin/tightvncserver
> 
> This does surprise me, because I also have x11vnc installed and
> vaguely remember using it in standalone server mode for a while.
> 
> But, yes, tightvncserver 1:1.3.9-9.1 is also installed, so I’m
> apparently using that.

Thanks, that gives me something to try to reproduce the problem now.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2020-03-03 13:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-01 23:04 qemu-system-x86_64: warning: Unknown X11 keycode mapping '<null>' Thorsten Glaser
2020-03-02 10:28 ` Daniel P. Berrangé
2020-03-02 12:43   ` Thorsten Glaser
2020-03-02 13:03     ` Daniel P. Berrangé
2020-03-02 18:19       ` Thorsten Glaser
2020-03-03 10:46         ` Daniel P. Berrangé
2020-03-03 10:44     ` Daniel P. Berrangé
2020-03-03 13:12       ` Thorsten Glaser
2020-03-03 13:14         ` Daniel P. Berrangé [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-26 23:31 Oliver Bailey

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=20200303131407.GF1773352@redhat.com \
    --to=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=t.glaser@tarent.de \
    /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.